I'm performaing a restore of a database and am encountering some odd behavior.

The resore has been running since 10:00 this morning...! It should not have
taken more than an hour to complete.

The database continually shows a status of LOADING. I've even stopped and
restarted SQL Server and STILL get the LOADING status.

I've seen this before but for the life of me ccan't recall how I fixed it...

Perhaps SQL Server is trying to roll back a large transaction log. Normally,
the rollback would resume
when the service is started again, but you can re-start the service using a
special command line parameter that indicates not to resume rollbacks.
However, the database will probably be left marked as suspect. At that
point, you may choose to restore the database from a recent backup that took
place before the transaction started. I think the parameter is -T4022, but
you will need to research this further
on MSDN.COM

Show quoteHide quote

Actually found the issue:

The RESTORE script did a restore of the database with a NORECOVERY. This left the database in a LOADING status.

I just ran a RESTORE DATABASE WITH RECOVERY which essentially just reset the LOADING status...

Thanks for the input
  Perhaps SQL Server is trying to roll back a large transaction log. Normally,
  the rollback would resume
  when the service is started again, but you can re-start the service using a
  special command line parameter that indicates not to resume rollbacks.
  However, the database will probably be left marked as suspect. At that
  point, you may choose to restore the database from a recent backup that took
  place before the transaction started. I think the parameter is -T4022, but
  you will need to research this further
  on MSDN.COM

Show quoteHide quote

Consecutive values
Random number generation with seed value
Compute sum of count(*) with group by
Copying records from one table to another
Automate Importing File