November 26, 2012 at 2:10 pm
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.......
November 26, 2012 at 11:38 pm
How many users are there?
How did you configure the lookup?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 27, 2012 at 6:34 am
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.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply