Hello,
My question may be dumb, but desperation causes me to ask it anyway:
I have created an instance of SQL SERVER 2000 on my PC(which is not ideal, but the server wont be here for a couple of more weeks so my pc is all the hardware I have to work with).
I have a problem, the machine was in the middle of a job when it got turned off:
Now the Instance of SQL Server on my machine is in the process of recovering the Database that was in use when it was turned off :
Here's the message that appears in the error log:
Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
and recovering the entire database which is approximately 15 gigs -- its is veeeeery slow:
(started recovery at 09:21:17.03
2003-05-28 11:27:59.54 spid11 Recovery of database (7) is 17% complete (approximately 35392 more seconds) (Phase 3 of 3).
Is there a way around this? Is there a way to expedite?
Any help is greatly appreciated...
My question may be dumb, but desperation causes me to ask it anyway:
I have created an instance of SQL SERVER 2000 on my PC(which is not ideal, but the server wont be here for a couple of more weeks so my pc is all the hardware I have to work with).
I have a problem, the machine was in the middle of a job when it got turned off:
Now the Instance of SQL Server on my machine is in the process of recovering the Database that was in use when it was turned off :
Here's the message that appears in the error log:
Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
and recovering the entire database which is approximately 15 gigs -- its is veeeeery slow:
(started recovery at 09:21:17.03
2003-05-28 11:27:59.54 spid11 Recovery of database (7) is 17% complete (approximately 35392 more seconds) (Phase 3 of 3).
Is there a way around this? Is there a way to expedite?
Any help is greatly appreciated...
