First off, I'm new to SQL so please be kind. I've had one class (admin)
with another coming soon (programming), and too little time to properly
digest what I'm learning. That said, here's my situation:

My company was testing a software package. As such we had a test database
into which we imported data for our test group of users to review. When the
final test was over, this group was given explicit directions not to use the
test database. A month later "oops - I've been using the wrong database!"

So, now we have data in a couple tables in one database that needs to be
moved into another one. That part I get and can handle. The problem is the
Primary Keys. If I simply export-import, I get errors. Is there a way to
script new keys into the process, a way to instruct SQL to generate new keys
as part of the import process? If so, I think I can get the rest to work (I
know the tables, the user, the date range, etc.).

Any suggestions greatly appreciated.

What do you mean you get errors?

What errors?

Are you seeing this?

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.konesans.com - Consultancy from the people who know


"Neal Makely" <nmakely (AT) ahcinc (DOT) com> wrote