January 16, 2014 at 4:45 am
I'm trying to use SQL 2012's Copy Database Wizard to take copy a SQL 2005 database from another server and load it into SQL 2012. At the moment I'm testing things, so the source database is SQL 2005 Standard Edition, and the destination is only SQL 2012 Developer Edition, but I don't see that this should be a problem?
When it comes time to do it for the production DB, we can't have downtime, hence me testing this method and not just doing a detach/attach.
Errors are being written to the event log and it keeps failing on the final step when I hit 'Finish'. The event log shows an error with EventID 12291 then a warning with EventID 208, but when I look online everyone seems to have a different take on what causes this, so I'll list what I'm doing and maybe someone could tell me where I'm going wrong please?
Click Finish to perform the following actions:
Source: 192.168.114.22, 30127 SQL Server 2005, Microsoft SQL Server Standard Edition (64-bit) , Build 5000, Microsoft Windows NT 5.2 (3790) NT AMD64
Destination: SQL2012Dev1 Other SQL Server Version, Microsoft SQL Server Developer Edition (64-bit) , Build 3128, Microsoft Windows NT 6.2 (9200) NT x64
Using SMO online transfer
The following databases will be moved or copied:
Copy:AffiliateSystem_Temp
Destination file will be created: F:\DATA\AffiliateSystem_Temp.mdf
Destination file will be created: G:\LOG\AffiliateSystem_Temp_log.ldf
Stop transfer if duplicate database name exists at destination
Package scheduled to run immediately
After clicking the Finish button, it runs through the first 4 actions successfully then fails on the final one, 'Execute SQL Server Agent job'
The Event Log shows an error on EventID 12291 with the description:
Package "Test_Copy_Package_1" failed.
... and EventID 208 with the description:
SQL Server Scheduled Job 'Test_Copy_Package_1' (0xEE07A7B432F2FF46BE4E33A4BA92FBFD) - Status: Failed - Invoked on: 2014-01-16 05:06:20 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 1 (Test_Copy_Package_1_Step).
I've checked the Configuration Manager and 'Integration Services' and 'Agent' are running on both the source and destination servers.
Thanks in advance for any help with this, it's probably some tiny little thing I'm missing or haven't considered, which is usually the way!! Any help is much appreciated 🙂
January 16, 2014 at 5:49 am
why not just use backup\restore or detach\attach
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 16, 2014 at 6:00 am
Perry Whittle (1/16/2014)
why not just use backup\restore or detach\attach
Hi Perry, thanks for the reply ...
Detach / Attach would require downtime which we don't want, the production version is a large database being moved across a network, it would be offline for far too long.
Backup / Restore is an option, but it still involves downtime.
This method, using the Copy Database Wizard, lets me choose the 'Use the SQL Management Object Method' option to keep the database online.
To be honest I hadn't even considered this as an option until recently, I've used the detach/attach method a number of times for other smaller databases that don't matter as much with regards to downtime, so I was planning on using the backup / restore method here, until I realised this wizard may let me keep the database online the whole time, then the only downtime involved is to change files directing the webpages/apps to the new database, which would be very fast.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply