There is a very good article on creating server side traces in SQL Server here:
SQL Server Pedia - Server Side Traces
The essence of the whole thing is this:
Monitoring using the SQL Server Profiler creates considerable overhead, whether you run it on the server that hosts the database itself, or on a client machine.
Monitoring using a script of the sort generated in the linked article, on the other hand, creates nearly zero performance degradation (per Linchi Shea's fine article, found here: trace-profiler-test). I have linked to Linchi's test results as well as the article. Test Results
Subscribe to:
Posts (Atom)
DBT-50000 when using DBCA.bat on Windows (Oracle 19.11)
I’ve been having some trouble getting DBCA to run in order to create databases. Thought I’d share it with you, and thus document it for la...
-
Most of what we're going to want to look at when you're having production issues are available through DMV's. If granti...
-
I’ve been having some trouble getting DBCA to run in order to create databases. Thought I’d share it with you, and thus document it for la...
-
On one of our internal WebSphere application server network deployment v7 environments, I hit the following error. The error was: com.ibm....