By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,426 Members | 3,368 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,426 IT Pros & Developers. It's quick & easy.

Need tools to Convert Access to SQL environment

P: n/a
Guy
I got a big Access file (1 400 tables) to convert to SQL and I would
like to be provided with some automated tools, except upsizing wizard
and DTS, to convert it on my own.

I got a lot of forms and query to convert too.

Can someday provide me with at least one tool name ?

Thanks,

Guy
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Someone else already answered your question earlier.

If you are not conformable using the DTS tools, then you need to hire some
one who experienced in this area.

Further, the fact of 1400 tables sounds like a VERY SERIOUS design program
exists. I would bet that a HUGE portion of those tables are some kind of
monthly, or yearly data. Simply adding one new column as for the date would
probably eliminate thousands of tables. (that many tables does not even come
close to making ANY kind of sense). A bit code to merge those many tables
into one would make the whole process a much better design, and the that
would also solve the whole export problem too! In other words, you should
look at the design of the data and the tables. It is quite easy to write a
bit code in ms-access to merge those tables together. From that point, you
then use the DTS tools.

It would be truly sad to simply move a horrible data mess from ms-access to
sql server. Moving such a mess accomplishes nothing for you. You are simply
shoving a huge mess into sql server now, and not improving your data
management by any amount. In fact, it would be waste of developer/people
time to move such a mess. A bit work on the data BEFORE you transfer sounds
like the ticket here. It is not use to build a new garage only to fill it
with all the old junk that made the old one so bad ;-)

If the dts tools and perhaps 1 or 2 hours of writing some code in ms-access
is beyond your abilities, then it is time to hire some professional help.
The tools plus a bit of code should be more then enough here.
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
No************@msn.com
http://www.attcanada.net/~kallal.msn
Nov 12 '05 #2

P: n/a
Guy
"Albert D. Kallal" <pl********************@msn.com> wrote in message news:<BSyyb.531898$6C4.452895@pd7tw1no>...
Someone else already answered your question earlier.

If you are not conformable using the DTS tools, then you need to hire some
one who experienced in this area.

Further, the fact of 1400 tables sounds like a VERY SERIOUS design program
exists. I would bet that a HUGE portion of those tables are some kind of
monthly, or yearly data. Simply adding one new column as for the date would
probably eliminate thousands of tables. (that many tables does not even come
close to making ANY kind of sense). A bit code to merge those many tables
into one would make the whole process a much better design, and the that
would also solve the whole export problem too! In other words, you should
look at the design of the data and the tables. It is quite easy to write a
bit code in ms-access to merge those tables together. From that point, you
then use the DTS tools.

It would be truly sad to simply move a horrible data mess from ms-access to
sql server. Moving such a mess accomplishes nothing for you. You are simply
shoving a huge mess into sql server now, and not improving your data
management by any amount. In fact, it would be waste of developer/people
time to move such a mess. A bit work on the data BEFORE you transfer sounds
like the ticket here. It is not use to build a new garage only to fill it
with all the old junk that made the old one so bad ;-)

If the dts tools and perhaps 1 or 2 hours of writing some code in ms-access
is beyond your abilities, then it is time to hire some professional help.
The tools plus a bit of code should be more then enough here.


Thanks Albert for your advice. I agree the structure problem must be
fix up before converting.

Guy
Nov 12 '05 #3

P: n/a
Let me see -- you want to convert, but you eliminate the two tools most
likely to help you? And you want to convert _Forms_ to SQL Server? Strange,
I never understood SQL Server to have Forms... that's why so many people
create Access front-ends to SQL Server back ends.

In the absence of useful tools, which I think is what the result of your
question will be, given the limitations you apply -- you can use SQL Server
Enterprise Manage to create comparable SQL Server tables, link them, and
fill them with manually-created (or self-automated) Append Queries.

But, anyone who'd do that, in preference to the Wizards, seems to me to be a
"glutton for punishment".

Larry

"Guy" <gu*@graphic-designer.com> wrote in message
news:e0**************************@posting.google.c om...
I got a big Access file (1 400 tables) to convert to SQL and I would
like to be provided with some automated tools, except upsizing wizard
and DTS, to convert it on my own.

I got a lot of forms and query to convert too.

Can someday provide me with at least one tool name ?

Thanks,

Guy

Nov 12 '05 #4

P: n/a
"Larry Linson" <bo*****@localhost.not> wrote in message
news:e8*****************@nwrddc01.gnilink.net...
Let me see -- you want to convert, but you eliminate the two tools most
likely to help you? And you want to convert _Forms_ to SQL Server? Strange, I never understood SQL Server to have Forms... that's why so many people
create Access front-ends to SQL Server back ends.

In the absence of useful tools, which I think is what the result of your
question will be, given the limitations you apply -- you can use SQL Server Enterprise Manage to create comparable SQL Server tables, link them, and
fill them with manually-created (or self-automated) Append Queries.

But, anyone who'd do that, in preference to the Wizards, seems to me to be a "glutton for punishment".


Well unless they've really improved I would have to disagree. The wizard
for Access 97 was dreadful. It choked on anything larger than a few
thousand rows. Worse yet, it made horrible implementations of the tables
created. It created Triggers to enforce required fields, separate objects
for default values, and often used different DataType translations than I
would have made had I done it manually. I ended up deleting almost all of
these and starting over in Enterprise Manager.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.