How to set up a simple SQL trace for trouble shooting database related issues with LANDESK
To reduce the size of the trace and the amount of data in the trace to filter through,please stop all LANDESK Services prior to running the SQL trace. To make stopping the LANDESK services fast and easy, go to this link and get the batch file. How to Stop/Start all LANDESK Services at Once?
NOTE: Check with your LANDESK Support Technician regarding any services that may need to remain running, depending on the component you are trouble shooting.
-Simple Trace:
1. Open up the 'SQL Server Management Studio'
2. Go to 'Tools' and open 'SQL Server Profiler'
3. Select the tab that says 'Events Selection'
4. Uncheck All for 'Audit Login', 'Audit Logout', 'Existing Connections'
5. Check the 'Show All Events' box in the bottom right corner
6. Find and expand 'Errors and Warnings' and put a check in each box under the column 'TextData' and select the leftmost check box (to select entire row) by 'User Error Messages'
7. Find and expand 'OLEDB' and put a check in the left most box next to 'OLEDB Errors'
8. Find and expand 'Stored Procedures' and put a check in the left most box for 'RPC Output Parameter', 'RPC:Completed', RPC:Starting', 'SP:StmtCompleted', and 'SP:StmtStarting'.
9. If you have multiple databases on the SQL server, you will need to select both 'Show All Events' and 'Show All Columns', then open 'Column Filters' and select 'DatabaseName' > 'Like', and enter the name of the LANDESK database.
10. Start trace
11. Then try to recreate the issue.
12. Once you see the issue, Stop the trace and save the trace file.
-Advanced Trace:
1. Open up the 'SQL Server Management Studio'
2. Go to 'Tools' and open 'SQL Server Profiler'
3. Select the tab that says 'Events Selection'
4. Uncheck All for 'Audit Login', 'Audit Logout', 'Existing Connections'
5. Check the 'Show All Events' box in the bottom right corner
6. Find and expand 'Errors and Warnings' and put a check in each box under the column 'TextData' and select the leftmost check box (to select entire row) by 'User Error Messages'
7. Find and expand'Locks' and put a check in the left most box next to 'Lock:Deadlock'
8. Find and expand 'OLEDB' and put a check in the left most box next to 'OLEDB Errors'
9. Find and expand 'Performance' and put a check in the leftmost checkbox by 'SQL:FullTextQuery' and 'Showplan All'
10. Find and expand 'Stored Procedures' and put a check in the left most box for 'RPC Output Parameter', 'RPC:Completed', RPC:Starting', 'SP:StmtCompleted', and 'SP:StmtStarting'.
11. If you have multiple databases on the SQL server, you will need to select both 'Show All Events' and 'Show All Columns', then open 'Column Filters' and select 'DatabaseName' > 'Like', and enter the name of the LANDESK database.
12. Start trace
13. Then try to recreate the issue.
14. Once you see the issue, Stop the trace and save the trace file.
Once you have finished, you can use the same batch file to restart all the LANDESK services, or you can reboot the core.