November 17, 2013 at 1:25 pm
I am trying to use Copy database wizard to copy databases from 2005 to 2012 sql server, but I'm getting error "An entry with same key already exists". What does this mean?
November 17, 2013 at 1:33 pm
Any idea on what kind of object it fails?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 17, 2013 at 2:42 pm
It failed on master stored proc objects. I skipped that and its working now. But its been alreay an hour and the process to copy is still runnng. DB size is 160GB. Is it usually slow? I am copying it to VM from physical serverl.
November 17, 2013 at 2:44 pm
Wouldn't a compressed full backup/restore have been faster?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 17, 2013 at 3:03 pm
can't take compressed backup on 2005...what are other options? because other dbs are pretty similar in size.
November 17, 2013 at 3:14 pm
You could do an uncompressed back-up/restore.
Or do the data migration in SSIS itself so you can exploit parallellism to the max. (not sure how the copy database task uses parallellism).
ps: since this is a sql 2012 forum, you would expect questions about 2012, nt 2005 😉
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 17, 2013 at 5:18 pm
Thanks. Any idea how to copy the list of linked server from 2005 to 2012? I didn't see the option in SDT.
November 18, 2013 at 12:37 am
SQL_Surfer (11/17/2013)
Thanks. Any idea how to copy the list of linked server from 2005 to 2012? I didn't see the option in SDT.
You can script them out. You can either right-click on each one and script them seperately, or you can retrieve the info from sys.servers.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 18, 2013 at 12:44 am
Koen Verbeeck (11/17/2013)
Wouldn't a compressed full backup/restore have been faster?
A normal uncompressed backup/restore would likely have been faster and less prone to random failures.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2013 at 2:50 am
SQL_Surfer (11/17/2013)
can't take compressed backup on 2005...what are other options? because other dbs are pretty similar in size.
install the trial version of Litespeed and use that to compress and move the backups.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply