November 14, 2008 at 7:37 am
I'm trying to restore a large DB temporarily to retrieve a table, in a less than ideal situation, but it's my only option right now. The database is 700 Gig. I only have enough room on one old server that's not being used for much. The backup was taken with Redgate ver 4.6, and the backup .SQB file resides on a Buffalo terrastation external drive. I scripted out the command from the Redgate GUI, put it into a SQL job and started the job. It says executing, the MDF, NDF and LDF all appeared in the correct location, sp_who2 shows RESTORING, but DiskIO shows 0, CPUTime is only 2343 and it's been running more than 24 hours. The database does not show up in SSMS, as "restoring" or anything else.
How can I determine if it's running very very slowly, or is just dead ?
November 14, 2008 at 7:55 am
homebrew01 (11/14/2008)
I'm trying to restore a large DB temporarily to retrieve a table, in a less than ideal situation, but it's my only option right now. The database is 700 Gig. I only have enough room on one old server that's not being used for much. The backup was taken with Redgate ver 4.6, and the backup .SQB file resides on a Buffalo terrastation external drive. I scripted out the command from the Redgate GUI, put it into a SQL job and started the job. It says executing, the MDF, NDF and LDF all appeared in the correct location, sp_who2 shows RESTORING, but DiskIO shows 0, CPUTime is only 2343 and it's been running more than 24 hours. The database does not show up in SSMS, as "restoring" or anything else.How can I determine if it's running very very slowly, or is just dead ?
Hard to say, but with the db being 700 GB, it may just be slow.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply