SQL Nexus Tool

New Post: Invaid object name 'sys.databases'

jackli — Fri, 03 Oct 2008 21:04:23 GMT

do select @@version to verify if you are truly on 2005
sys.databases is required but only exist in 2005 and beyond. 2000 doesn't have this object.

New Post: Error importing data

jackli — Fri, 03 Oct 2008 21:02:30 GMT

based on the conversation among ourselves, we have answered your question.
for the purpose of other people, here is the detail
If you use profiler (instead of sqldiag and our canned batch file to capture), a event can be lost. it will result in such behavior.
future version will stop importing to avoid confusion if readtrace detects a event is lost.
so best pratice is to use our canned batch file with trace defintion together with sqldiag (home page of this tool has link ) to collect server side tracing.

New Post: Invaid object name 'sys.databases'

lenin_tvr — Tue, 30 Sep 2008 14:10:00 GMT

Hi all,

i have SQL 2005 in my DB server.
when i try to conect databbase from SQL NExus, i am the following error.

"Invalid object name 'sys.databases' Error.208
thrown from .net Sql client data provider"

Kindly reply to resolve this issue.

-Lenin

New Post: Error importing data

rdoggart — Sun, 28 Sep 2008 13:33:03 GMT

I have a problem inporting data using readtrace. The import fails when it tries to create a unique clustered index on the seq key for table tbluniquestatements, it fails with a duplicate key error. When I check the table it does have multiple duplicate seq keys.

Any help welcome.

Ronnie

Created Issue: Can not Export to pdf format

maxfiep — Wed, 24 Sep 2008 13:50:59 GMT

This one has been frustrating me for the past two weeks. I want to save my reports to pdf for later review but every time I try I get the message “Only excel file format is supported” at first I though this may be because I didn’t have any pdf authoring tools installed but after downloading a trial vision of Adobe’s I still can not use this function. Also I have found nothing else on the web relating to the issue I’m having. Please can you tell me what I need to do to enable us to save these reports as pdf files?

New Post: SQL 2008 and SQLNexus

adrianc — Mon, 15 Sep 2008 21:39:31 GMT

Is there any ETA/estimated date for the new version ?
Thank you,
Adrian C.

New Post: SQL 2008 and SQLNexus

jackli — Fri, 05 Sep 2008 15:07:39 GMT

current version of readtrace won't read 10 trace. we will release a new version that will work on 2008 soon.

New Post: SQL 2008 and SQLNexus

adrianc — Thu, 04 Sep 2008 02:14:00 GMT

Greetings,

I want to use SQLNexus in investigating perf related issues for SQL 2008 on X64.
After unzipping the 2.5.0.5 version, I downloaded and setup the RML related utilities (for ReadTrace.exe) from here:
   http://www.microsoft.com/downloads/details.aspx?FamilyId=B60CDFA3-732E-4347-9C06-2D1F1F84C342&displaylang=en – RML utilities for SQL Server (x64)

Then, after generating a trace (via SQL profiler), I tried to download it using this command:
       sqlNexus.exe /ic:\SQLTraces\myTrace.trc

It failed w/ error message claiming that only SQL 2000/2005 traces are supported (version 10 is not).

Are there any known workarrounds?

Any related pointers/references are appreciated.

Thank you,
    AdrianC.

New Post: Support for SQL Server authentication

jackli — Wed, 03 Sep 2008 19:20:52 GMT

I will considier adding this feature back in future release given your situation

New Post: Some or all identity references could not be translated. (mscorlib)

jackli — Wed, 03 Sep 2008 19:12:32 GMT

there was a bug which relied on hardcoded builtin administrator's name.
this was fixed in latest build.
try it on latest build

New Post: Command-line use of SQL Nexus

jackli — Wed, 03 Sep 2008 19:11:18 GMT

Initial design had this in mind and it worked initially. But due to time constratins, later enhancement and bug fixes didn't consdier this as a fator. so it's possible it may not work.
But since there is a demand, I have logged a work item to check on this.

New Post: Importing trace files

jackli — Wed, 03 Sep 2008 19:06:08 GMT

go to %temp%\rml and find a file called readtrace.log to see what is happening.
future release will give options in UI to open log files

New Post: Error while importing data in SQL Nexus

jackli — Wed, 03 Sep 2008 19:03:30 GMT

spid 60,000 seems to be really high.
are you using latest version of SQL nexus?
"About" will tell you which version. latest is 2.5.0.5
The reason I ask about this is that older version of SQL Nexus turn on a trace flag to handle MARS by default. that will pad one zero to every spid. for example, spid 100 will become 1000.
reply to this message if you are using version 2.5.0.5 and continue to have this issue

Closed Issue: Can't import trace files into SQL Nexus

jackli — Wed, 03 Sep 2008 18:57:47 GMT

I get no error message just 0 rows created. I see a cmd window open but can not get any information off the window since it closes to quick.

I have installed the RML Utilites on the system already.

Commented Issue: Can't import trace files into SQL Nexus

jackli — Wed, 03 Sep 2008 18:57:38 GMT

I get no error message just 0 rows created. I see a cmd window open but can not get any information off the window since it closes to quick.

I have installed the RML Utilites on the system already.
Comments: ** Comment from web user: jackli **

examine a file called ReadTrace.log at %temp%\rml to see if there are any errors.
Additionally, do you have any file named *.trc in the directory

Closed Issue: Error when importing *.trc: The system cannot find the file specified

jackli — Wed, 03 Sep 2008 18:55:16 GMT

When I attempt to import files, and error is generated "The system cannot find the file specified" at the *.trc step. I have SQL Server Express along with a default SQL Server 2005 Developer addition running on the system I'm testing this on. I do see a file named: LSHUCK01__sp_trace.trc in the SQLDiagOutput directory.

A screen shot is attached.

Thanks,

Lee

Closed Issue: How can you work with only one instance?

jackli — Wed, 03 Sep 2008 18:54:27 GMT

If I have a clustered server with more than one instance, SQLDiag appears to grab information from ALL the instances, yet, when I import the trace files, and want to look at ReadTrace_Main, it says I have no events, which I know I do, it justs resides on a different instnace, not the default one. How can I chaange this?

Commented Issue: How can you work with only one instance?

jackli — Wed, 03 Sep 2008 18:54:17 GMT

Current approach is that it detects if pssdiag has collected multiple instances. then it presents a diaglog box to let you chose which instance to load data. so it should work.
if this doesn't work. you can do the following
1) rename ##pssdiag.log file to something else
2) separate files to different directories by instance. The files all have *_<InstanceName>_*. so it's easy to spot them

Closed Issue: >1gb trace-files per min.

bartduncan — Tue, 02 Sep 2008 23:04:01 GMT

a heavy loaded system generates >1 GB of tracedata per min.
Is there any parameters in the default SQLDiagPerfStats_Trace.XML file I can disable?
Comments: See above comment

Commented Issue: >1gb trace-files per min.

bartduncan — Tue, 02 Sep 2008 23:03:50 GMT

a heavy loaded system generates >1 GB of tracedata per min.
Is there any parameters in the default SQLDiagPerfStats_Trace.XML file I can disable?
Comments: ** Comment from web user: bartduncan **

Unfortunately, this is a limitation of SQL Serve profiler tracing... any trace that provides per-batch execution statistics will generate a lot of trace output on a server with a high batch execution rate. The SQLDiagPerfStats_Trace.XML file already excludes events (such as statement-level events) that would allow for better analysis but are not necessary for a high-level analysis. There's not much else you could exclude that would reduce the trace size without making the trace worthless for perf analysis. You could exclude a lot of low-volume events, but there are only a couple of events that contribute to trc file size significantly, so eliminating all the low-volume events is kind of pointless.

Long-term (very long term, as in "future releases of SQL Server"), there is interest in providing an effective way to get statement- and batch-level execution statistics without requiring a profiler trace, but for SQL 2005 and prior versions, profiler trace analysis is generally as good as it gets. There is a new feature ("plan fingerprints") in SQL 2008 that takes some initial steps toward providing trace-less query perf analysis.