SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Best Way to Migrate Data from Different DB SQL Servers


Best Way to Migrate Data from Different DB SQL Servers

Author
Message
Paul Muller
Paul Muller
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 171
have data like the following:
:

PK Desc InsertedByUserID UpdatedByUserID

1 Johnny 13 90

2 Frankie 34 75

3 Brenda 75 90

4 Scott 25 14

The data is being moved into a new app. The userid will be changed in the new app. The initial migration of data is converting the old users to a new id. So I have no issues with the loading the new User table. The old id is being retained. Every row of data in the database has an InsertedByUserID and a UpdatedByUserID column. I have been trying to do the migration of data using a lookup of the old user id to the new user id. I am getting memory errors . I did also try a merge join of old to new on the insert id and another merge join for UpdatedBy id. Seems a bit complicated. Is there a better way? I cannot use staging tables for the migration. I cannot use linked servers either. Sometimes there could be a few more ids in the data columns.

So what is the best way? Please offer suggestions.......
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27601 Visits: 13268
How many users are there?
How did you configure the lookup?


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Tee Time
Tee Time
Say Hey Kid
Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)Say Hey Kid (673 reputation)

Group: General Forum Members
Points: 673 Visits: 465
Just a thought. Try pulling over the old data, as it is, into the new db. From there, use the old data in the new location as the source for your package. See if that helps to alleviate your issue.

Lookups can be very memory intensive, as my limited experience has shown me.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search