I am upsizing an access DB to SQL Server. I'v had trouble running the
upsizing wizard, so I imported both the data and schema via DTS. ALl the
data and schema imported just fine. The field types were on target for the
most part. My biggest concern is the relationships which din't make it as
well as primary keys, and so forth. I was able to fix this without much
effort. Here is my question:

The access DB is running on a production site. I needed to first do the
upsize and work out all the SLQ issues and make sure the system will work
once the switch is ultimately made. So in an effort to get all the data in
(and tell me if I'm wrong here) into SQL Server, I couldnt have any identity
fields or relationships in place inthe new SQL server DB inorder to preserve
all the referential data. Once the data is in I then changed all the
autonumber columns to identity columns. Everything is great. Now, once I can
be sure everything is running well, I'll need to get all the data from the
production access DB.

My plan is to export the SQL server schema and then import the access data
into the new DB. Do I need to get rid of all the identity columns (just set
to INT) in order to get the data in properly. ALso, do I need to wait until
all the data is in the new SQL Server production DB before establishing all
the relationships?

Any thoughts, or ideas are greatly appreciated!

Have a look at this article and let us know if it answers your concerns

Problems With IDENTITY() and the DataPump task.
(http://www.sqldts.com/default.aspx?293)

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"bidllc" <bidllc (AT) discussions (DOT) microsoft.com> wrote

Thanks, I'll check it out and let you know.

"Allan Mitchell" wrote: