Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Profiler question (resource issue) Expand / Collapse
Author
Message
Posted Tuesday, January 7, 2014 3:02 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, January 8, 2014 6:10 AM
Points: 31, Visits: 117
I keep having a long running profile shut down because the C Drive is full. I am saving the output to a table so is there a method to stop the direction to the screen?

We are saving transactions from a software package to the database and some of the transactions aren't saved nor do they error so I am trying to find out if the programmer has inadvertently rolled back a transaction.

The issue is when I try to recreate it by submitting the transaction it processes so I am thinking this condition is created by how it is submitting previous transactions and maybe the program has a variable that triggers a rollback. I have seen this before but my transaction volume was much lower and this was not an issue so I was able to show them where they were calling the roll back and we could infer from the previous transactions what caused it.

thoughts?


always get a backup before you try that.
Post #1528691
Posted Tuesday, January 7, 2014 5:36 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Saturday, August 30, 2014 7:18 PM
Points: 6,250, Visits: 7,409
Mountain Steve (1/7/2014)
I keep having a long running profile shut down because the C Drive is full. I am saving the output to a table so is there a method to stop the direction to the screen?

Use a serverside trace. You initiate it via T-SQL instead of via the profiler.

Offhand, not sure about the rest.



- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Post #1528721
Posted Monday, February 3, 2014 1:20 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 14, 2014 1:43 AM
Points: 215, Visits: 79
Serverside tracing is recommended over the SQL Profiler GUI.

In the profiler you can go to "Export" -> "trace definition". With that script, and a few minor adjustments, you can start the serverside trace.

If you want to use the SQL Profiler GUI, you can adjust a Windows setting (TEMP), as per
http://msdn.microsoft.com/en-us/library/ms174203(v=SQL.100).aspx
Post #1537486
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse