Database In Recovery

Hello all,

Is there a way to check the status of a database in recovery. Like how far along it may be. If not is there a way to stop a database in recovery and just drop it.

Thanks in advance,

Mike

There should be progress messages in the errorlog indicating percent complete and how long it is expected to continue?

What version of SQL are you running?

|||

Sorry im running SQL SERVER 2005 Standard Edition.

And you were correct it is in there. It looks like im looking at 9 hours to recover. Is there a way to stop the recovery? I can drop the database and reload the tables faster than that.

Thanks again,

Mike

|||

The only way to prevent recovery is to stop the server and delete or rename one of the database files. Then you can drop it after it comes up recovery pending on the server restart.

What phase of recovery is the database in? Is there just an enormous transaction to rollback?

|||

The recovery is in phase 2. The trans logs are about 58GB. I think i will do what you said that way I can just drop and create.

Thank You,

Mike

|||

Having same problem with database being in recovery. Has been running for a number of hours.

Below is message that repeats frequently in log file. However, I don't really know how to interpret it.

Process 16:0:0 (0xb78) Worker 0x03D880E8 appears to be non-yielding on Scheduler 1. Thread creation time: 12831081295625. Approx Thread CPU Used: kernel 265 ms, user 76778796 ms. Process Utilization 49%. System Idle 49%. Interval: 76832057 ms.

Any advise would be appreciated.

Database Grow Problems

I am having problems when I try to grow my database. It seems to be taken a
long time (1 hour and still going) and is also making the system
unresponsive. The CPU is at 0 but the computer is so slow nothing can be
done. This is a dual processor system with 2ghz processors. I am using the
express version and am trying to grow a database from 45 mb to the maximum
of 4096 mb.
Is this normall or is there something wrong with the hard drive, system or
database? I ran the dbcc tool and it did not report any problem with the
tables or index.
The reason I decided to grow it to the max is because my incremental grows
were slowing down my application. I figured if I set it to the maximum it
would speed things up. I didn't know growing it would take this long.
Bob
That seems excessive for just 4GB of growth but by default it will have to
zero initialize every bit in the file. This normally takes a while and
depends heavily on the hardware as to how long. If you are running on
Windows XP or Windows 2003 then you may be able to take advantage of Instant
file initialization. From BOL:
Instant file initialization is only available if the SQL Server
(MSSQLSERVER) service account has been granted SE_MANAGE_VOLUME_NAME.
Members of the Windows Administrator group have this right and can grant it
to other users by adding them to the Perform Volume Maintenance Tasks
security policy. For more information about assigning user rights, see the
Windows documentation.
Andrew J. Kelly SQL MVP
"Bob" <msgdev@.hotmail.com> wrote in message
news:%23RvjnVQVGHA.5288@.TK2MSFTNGP14.phx.gbl...
>I am having problems when I try to grow my database. It seems to be taken
>a long time (1 hour and still going) and is also making the system
>unresponsive. The CPU is at 0 but the computer is so slow nothing can be
>done. This is a dual processor system with 2ghz processors. I am using
>the express version and am trying to grow a database from 45 mb to the
>maximum of 4096 mb.
> Is this normall or is there something wrong with the hard drive, system or
> database? I ran the dbcc tool and it did not report any problem with the
> tables or index.
> The reason I decided to grow it to the max is because my incremental grows
> were slowing down my application. I figured if I set it to the maximum it
> would speed things up. I didn't know growing it would take this long.
>
> Bob
>

Database Grow Problems

I am having problems when I try to grow my database. It seems to be taken a
long time (1 hour and still going) and is also making the system
unresponsive. The CPU is at 0 but the computer is so slow nothing can be
done. This is a dual processor system with 2ghz processors. I am using the
express version and am trying to grow a database from 45 mb to the maximum
of 4096 mb.
Is this normall or is there something wrong with the hard drive, system or
database? I ran the dbcc tool and it did not report any problem with the
tables or index.
The reason I decided to grow it to the max is because my incremental grows
were slowing down my application. I figured if I set it to the maximum it
would speed things up. I didn't know growing it would take this long.
BobThat seems excessive for just 4GB of growth but by default it will have to
zero initialize every bit in the file. This normally takes a while and
depends heavily on the hardware as to how long. If you are running on
Windows XP or Windows 2003 then you may be able to take advantage of Instant
file initialization. From BOL:
Instant file initialization is only available if the SQL Server
(MSSQLSERVER) service account has been granted SE_MANAGE_VOLUME_NAME.
Members of the Windows Administrator group have this right and can grant it
to other users by adding them to the Perform Volume Maintenance Tasks
security policy. For more information about assigning user rights, see the
Windows documentation.
Andrew J. Kelly SQL MVP
"Bob" <msgdev@.hotmail.com> wrote in message
news:%23RvjnVQVGHA.5288@.TK2MSFTNGP14.phx.gbl...
>I am having problems when I try to grow my database. It seems to be taken
>a long time (1 hour and still going) and is also making the system
>unresponsive. The CPU is at 0 but the computer is so slow nothing can be
>done. This is a dual processor system with 2ghz processors. I am using
>the express version and am trying to grow a database from 45 mb to the
>maximum of 4096 mb.
> Is this normall or is there something wrong with the hard drive, system or
> database? I ran the dbcc tool and it did not report any problem with the
> tables or index.
> The reason I decided to grow it to the max is because my incremental grows
> were slowing down my application. I figured if I set it to the maximum it
> would speed things up. I didn't know growing it would take this long.
>
> Bob
>