Bringing It All Together with SQL Nexus - SQL Server 2012 Internals and Troubleshooting - page 329

NOTE Please refer to Chapter 11 for details about what data you need to capture
for analyzing a bottleneck or troubleshooting a performance issue on your SQL
Server instance.
Once you have provided the output directory location of the data collected by SQLdiag or
manually collected diagnostic data, click the Import button. This initiates the import, and the
relevant importers will be called to extract, parse, and import the relevant data into the appropriate
tables. A summary of each of the i les processed and the importers activated is displayed in the same
dialog after the import is initiated.
NOTE For security reasons, the *.trc i les are created with the same Windows
security permissions as the database data i les. In most environments this means
that you don't have read permission to the i les, which will cause the import to
fail. Check the permissions on all the *.trc i les in the SQLDiag Output folder
and assign the account running the import into the SQL Nexus database
Read & Execute permissions where appropriate.
If you run into any errors or exceptions while importing the data, you can view the SQL Nexus log
i le, which is located at %temp%/sqlnexus.000.log on the machine on which you are running
SQL Nexus. This log i le can be attached to the Discussion/Issue Tracker pages available on the SQL
Nexus CodePlex site in case you are not able to resolve the issue. You can also browse through the
existing discussions and issues listed on the site, which contains answers to the most commonly
asked questions about the tool.
The BLG Blaster and the Rowset Importer are relatively straightforward in their tasks, but the
ReadTrace importer warrants a special mention here. Figure 12-4 shows the different options
available for the ReadTrace importer.
FIGURE 12-4