Anyway to trace the origin of a SPID once server is rebooted?

Received a db error when I was in a conference
Process 49 unlocking unowned resource: DB: 1
and SQL server stopped and tried to recover.
In a panic my team rebooted the server (which resolved the issue)
Since the reboot occurred I couldn't see what was SPID 49.
After the reboot is there a way in the sys tables to see what SPID49 was at
a given time?
Jeff
Message posted via http://www.droptable.comNo
Andrew J. Kelly SQL MVP
"Jeffrey Sheldon via droptable.com" <forum@.droptable.com> wrote in message
news:d871d8b5bf1642a6bfca78c03646a764@.SQ
droptable.com...
> Received a db error when I was in a conference
> Process 49 unlocking unowned resource: DB: 1
> and SQL server stopped and tried to recover.
> In a panic my team rebooted the server (which resolved the issue)
> Since the reboot occurred I couldn't see what was SPID 49.
> After the reboot is there a way in the sys tables to see what SPID49 was
> at
> a given time?
> Jeff
> --
> Message posted via http://www.droptable.com

Anyway to trace the origin of a SPID once server is rebooted?

Received a db error when I was in a conference
Process 49 unlocking unowned resource: DB: 1
and SQL server stopped and tried to recover.
In a panic my team rebooted the server (which resolved the issue)
Since the reboot occurred I couldn't see what was SPID 49.
After the reboot is there a way in the sys tables to see what SPID49 was at
a given time?
Jeff
Message posted via http://www.sqlmonster.com
No
Andrew J. Kelly SQL MVP
"Jeffrey Sheldon via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d871d8b5bf1642a6bfca78c03646a764@.SQLMonster.c om...
> Received a db error when I was in a conference
> Process 49 unlocking unowned resource: DB: 1
> and SQL server stopped and tried to recover.
> In a panic my team rebooted the server (which resolved the issue)
> Since the reboot occurred I couldn't see what was SPID 49.
> After the reboot is there a way in the sys tables to see what SPID49 was
> at
> a given time?
> Jeff
> --
> Message posted via http://www.sqlmonster.com

Anyway to trace the origin of a SPID once server is rebooted?

Received a db error when I was in a conference
Process 49 unlocking unowned resource: DB: 1
and SQL server stopped and tried to recover.
In a panic my team rebooted the server (which resolved the issue)
Since the reboot occurred I couldn't see what was SPID 49.
After the reboot is there a way in the sys tables to see what SPID49 was at
a given time?
Jeff
--
Message posted via http://www.sqlmonster.comNo
--
Andrew J. Kelly SQL MVP
"Jeffrey Sheldon via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d871d8b5bf1642a6bfca78c03646a764@.SQLMonster.com...
> Received a db error when I was in a conference
> Process 49 unlocking unowned resource: DB: 1
> and SQL server stopped and tried to recover.
> In a panic my team rebooted the server (which resolved the issue)
> Since the reboot occurred I couldn't see what was SPID 49.
> After the reboot is there a way in the sys tables to see what SPID49 was
> at
> a given time?
> Jeff
> --
> Message posted via http://www.sqlmonster.com

Anyway to recover delete stored proc?

Folks.

I screwed up big time, I deleted a very long and smart stored proc (pls
don't ask how).

Is there anyway I can recover it?

Any advice appreciated.

Tada.KoliPoki (rayone@.gmail.com) writes:
> I screwed up big time, I deleted a very long and smart stored proc (pls
> don't ask how).
> Is there anyway I can recover it?

Do you have a backup of the database? Or do you run the database with
full or bulk-logged recovery? In that case you might be able to.

If you don't have any backup and run with simple recovery, the procedure
has left for outer space.

Generally, all source code should be under version control. See the
database as the place where you have the binary representation of
the source.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp