User Database Automatic Recovery

Hi

Yesterday a user has run a storedprocedure which
updates a very transaction table having million of
records , as usual the user killed the process in the
middle of the execution.(which has resulted in rollback
action).

this rollback process blocked other scheduled jobs and
its was running for more than 8 hours without completing

as usual decided to shutdown and restart the sqlserver
while restarting the sql server went into automatic recovery

the following are the log recording

2001-04-17 12:00:01.86 spid9 Recovery progress on database 'ISH' (7): 48 percent.
2001-04-17 12:00:37.89 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'.
2001-04-17 12:02:36.60 spid9 Recovery progress on database 'ISH' (7): 49 percent.
2001-04-17 12:08:12.79 spid9 Recovery progress on database 'ISH' (7): 49 percent.
2001-04-17 12:11:49.90 spid9 Recovery progress on database 'ISH' (7): 50 percent.
2001-04-17 12:11:50.32 spid9 Recovery progress on database 'ISH' (7): 92 percent.

if you see the log reading from 50% jumps to 92 % and the automatic recovery
process is running from another 5 hours (now not able to open the database)

in order to avoid the sql server going into automatic recovery mode (usually the dba use to update the master.sysdatabase table the status column with some
magic number to set the database into emergency mode) but i followed my own style (deleting the reocord for the user database from sysdatabases)
and restarted the sql server , and used my monday tape backup (complete bkup) to recover the database. In the recovery option i used force restore over existing database (hoping that this will reduce the database recovery time ,bcaus the data file (mdf and ldf ) need not to be created.

but the result :- after running six hours of loading data from tape ( i am getting the following reading in the log file)

2001-04-17 16:15:58.40 spid7 Starting up database 'ISH'.
2001-04-17 16:15:58.40 spid7 Opening file F:DATABASEISH.mdf.
2001-04-17 16:15:58.46 spid7 Opening file F:DatabaseISH_1.mdf.
2001-04-17 16:15:58.48 spid7 Opening file G:Databaseish_5_data_Data.NDF.
2001-04-17 16:15:58.49 spid7 Opening file G:Databasesrv_fg_data1.NDF.
2001-04-17 16:15:58.49 spid7 Opening file G:Databasesrv_fg_data3.NDF.
2001-04-17 16:15:58.53 spid7 Opening file G:Databasesrvindex_fg_data1.NDF.
2001-04-17 16:15:58.54 spid7 Opening file F:DATABASEISH_3.mdf.
2001-04-17 16:15:58.57 spid7 Opening file F:databaseISH_4.mdf.
2001-04-17 16:15:58.59 spid7 Opening file F:databaseISH_2.mdf.
2001-04-17 16:15:58.60 spid7 Opening file G:Databasesrv_fg_data2.NDF.
2001-04-17 16:15:58.62 spid7 Opening file G:DATABASEISH_log.ldf.
2001-04-17 16:15:58.64 spid7 Opening file G:databaseISH_log_1.ldf.
2001-04-17 16:15:58.65 spid7 Bypassing recovery for database 'ISH' because it is marked IN LOAD.

realy do not what is happening in the background.(if its oracle the dba has
the control over the database . In sql server has the control over the dba)

any one who has any idea on sql server recovery (the size of the database is
22 gb which is recovered and tape device is hp sure store DAT 40 E (DSS-4,4MM TAPE). Thanks in advance

Have a good day (not for me laaa)

Sethu