November 19, 2008 at 5:11 am
SQLDiag runs fine on the servers i work with. The problem is the files generated (.OUT) are larger and growing larger on each run. The problem is that it cannot be opened in a normal text editor (Notepad) or Internet Explorer. Is there a way to edit the SQLDiag xml documents to reduce the size of the output file ?
November 19, 2008 at 5:34 pm
What are you running sqlsdiag for? It gathers information from the run, and if you run it multiple times without rebooting/restarting, I suppose they could be larger files, but I wouldn't expect that.
What is larger? Sizewise?
November 19, 2008 at 10:27 pm
For now, I'm just testing for future use. So i run it once from the command line when i need to. The issue is really the size of the .out file. On my pc its fine for now because its around 5mb, that can be opened, but on our servers the file is 9 Gigs and higher, this makes it impossible to open in Notepad and Internet Explorer. Now i know that the SQLDiag.xml file does the requests for info so if i could get a clear direction on the what to edit or set to false, i can get the file down to a manageable and usable size where i can request less information from SQLDiag. Any ideas?
November 19, 2008 at 11:47 pm
Try this link:
http://support.microsoft.com/default.aspx/kb/215340
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
November 20, 2008 at 8:05 am
I wonder if SQL Nexus to load 9GB trace file
http://www.codeplex.com/sqlnexus
What is SQL Nexus?
SQL Nexus is a tool that helps you identify the root cause of SQL Server performance issues. It loads and analyzes performance data collected by SQLDiag and PSSDiag. It can dramatically reduce the amount of time you spend manually analyzing data.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply