7 0 1900-01-01 00:00:00.000 background DB STARTUP NULL NULL NULL NULL 1 1 NULL 0 SLEEP_DBSTARTUP 88 SLEEP_DBSTARTUP 0 1 0 NULL 0 0
46 81051588 1 0x0000000006012988 558 124 2935 4096 us_english mdy 7 0 0 0 0 0 0 0 0 2 -1 0 0 0
1 0 0 1 NULL NULL
14 0 1900-01-01 00:00:00.000 background DB STARTUP NULL NULL NULL NULL 0 1 NULL -3 LCK_M_S 81045798 LCK_M_S KEY: 5:196608 (2d188ef96974) 0 1 0 NULL 8 932043145 452 81048034 0 0x0000000006008BC8 21914
1933 586856 4096 us_english mdy 7 0 0 0 0 0 0 0 0 2 -1 0 0 0 1 0 0 1 NULL
NULL
It appears like a lock, and I'm thinking that killing session 14 perhaps would help me.
I'm looking for options that help me to bring ONLINE again my database, I'm thinking in restart my Instance, drop the database, and attach again, but as a last resort option,
What do you think ??
Thanks for your answers
Those two system processes are normal when starting up a database - sleep_dbstartup just checks the status intermittently. I wouldn't kill them at this point. Try the following for queries to check the status of the recovery:
Tracking database recovery progress using information from DMV
Sue