October 6, 2010 at 4:06 am
Morning,
450GB DB
300GB bak file
On 2005 i ran a full db backup.
Zipped
Transferred
Unzipped
2008 managment studio attempted a restore , received timeout message within 10 secs
Scripted a restore using:
---------------------------
RESTORE DATABASE DB2
FROM DISK = 'e:\DB2.bak'
WITH MOVE 'DB2' TO 'g:\SQLDATA\DB2.MDF' ,
MOVE 'DB2_Log' TO 'g:\SQLDATA\DB2_Log.LDF'
---------------------------
Ran for 2 days then stopped it manually.
Tested script with small database
Small database restored ok, within 2 mins
Ran:
-----------------------------
RESTORE FILELISTONLY
FROM DISK = 'e:\DB2.bak'
-----------------------------
To check file names were correct on larger db.
Ran:
---------------------------
RESTORE DATABASE DB2
FROM DISK = 'e:\DB2.bak'
WITH MOVE 'DB2' TO 'g:\SQLDATA\DB2.MDF' ,
MOVE 'DB2_Log' TO 'g:\SQLDATA\DB2_Log.LDF'
---------------------------
Been running for 6 days now...
Management Studio says: "debugging query...."
This text was exactly the same as the small db restore i.e appears to be working , not frozen.
The hardware the restore is running on is up to the task, new box , reasonable spec for testing. Having said that looking at task manager , the restore is not utilising much which is an oddity.
Two questions really:
1) hard to say im sure but would you guestimate the restore has failed somehow ?
2) part of this project is to move this large database to from 2005 to a new 2008 platform on the same network. I will not get away with anymore than a few hours downtime so it would seem backup/restore is not a good migration method.
What other methods are suggested ?
Half thought about collecting data on 2005 while migration is underway and using SSIS to transfer collected prior going live. Would all need tested obviously.
Also found this tool:
http://www.instavia.com/instant-upgrade-from-sql-2005-to-sql-2008
Which sounds too good to be true.
Any advice gratefully received.
Thanks
Scott
October 6, 2010 at 5:16 am
My guess is that you hit the 'debug' button rather than the execute button in management studio. It won't say debugging if you just ran the query.
Stop it, then hit F5 to run.
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
October 6, 2010 at 6:01 am
GilaMonster (10/6/2010)
My guess is that you hit the 'debug' button rather than the execute button in management studio. It won't say debugging if you just ran the query.Stop it, then hit F5 to run.
thanks for the reply .... first use of MGT studio 2008 , had not spotted that.
October 6, 2010 at 6:07 am
scott_lotus (10/6/2010)
GilaMonster (10/6/2010)
My guess is that you hit the 'debug' button rather than the execute button in management studio. It won't say debugging if you just ran the query.Stop it, then hit F5 to run.
thanks for the reply .... first use of MGT studio 2008 , had not spotted that.
The button change in SSMS 2208 annoyed me so much that the frist thing I do with a newly installed SSMS is remove the debug button from the toolbar entirely.
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
October 6, 2010 at 6:23 am
GilaMonster (10/6/2010)
scott_lotus (10/6/2010)
GilaMonster (10/6/2010)
My guess is that you hit the 'debug' button rather than the execute button in management studio. It won't say debugging if you just ran the query.Stop it, then hit F5 to run.
thanks for the reply .... first use of MGT studio 2008 , had not spotted that.
The button change in SSMS 2208 annoyed me so much that the frist thing I do with a newly installed SSMS is remove the debug button from the toolbar entirely.
🙂 thanks very much Gail, cannot believe it was something so simple .... wish i had posted sooner 🙂 i could hug you right now !
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply