sprocs executed but rolled back? is there any log?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » sprocs executed but rolled back? is there any...

sprocs executed but rolled back? is there any log?

Rate Topic

Display Mode

Topic Options

Author

Message

curious_sqldba

Posted Wednesday, December 26, 2012 4:14 PM

Ten Centuries

Group: General Forum Members
Last Login: Today @ 2:46 PM
Points: 1,171, Visits: 2,684

if a sproc started executing and then the transaction was killed, is there a way to check which sproc it was? I know if a sproc started and completed, i can try looking at sys.dm_exec_query_stats to see when was the last time it executed. Any thoughts?

Post #1400410

Bhuvnesh

Posted Friday, December 28, 2012 1:09 AM

SSCrazy

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562, Visits: 3,451

For future, you can set trace and capture that SP.

-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post

Post #1400819

Steve Jones - SSC Editor

Posted Friday, December 28, 2012 10:24 AM

SSC-Dedicated

Group: Administrators
Last Login: 2 days ago @ 1:47 PM
Points: 31,406, Visits: 13,722

I assume you'd be able to read the log and see the start and rollback, if there were changes, but this wouldn't be simple or easy.

SQL Server doesn't log every activity that occurs.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help

Post #1400970

curious_sqldba

Posted Friday, December 28, 2012 10:55 AM

Ten Centuries

Group: General Forum Members
Last Login: Today @ 2:46 PM
Points: 1,171, Visits: 2,684

Bhuvnesh (12/28/2012)

For future, you can set trace and capture that SP.

I don't want to trace to run 24 X7 as i don't know when the issue would occur. I wanted to know if someone killed a sproc, if i come in later is there a way to find which sproc was killed?

Post #1400981

Bhuvnesh

Posted Sunday, December 30, 2012 11:58 PM

SSCrazy

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562, Visits: 3,451

sqldba_newbie (12/28/2012)

I don't want to trace to run 24 X7 as i don't know when the issue would occur.

thats why i asked you to use trace when you are blank in any particular case use it but with PROPER AND REQUIRED filter. as we know that it s a resource intensive operation(that is what you would be thinking here and reluctant to use it ) , but when we have proper filer plus only fetching event which are relevant and required then you can minimize the resoure usage.

-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post

Post #1401296

« Prev Topic | Next Topic »

Permissions