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
I doubt that this comes up often, but I find myself in a bit of an argument about what isolation level will be used for transactions in our ...
Microsoft Technet has published an article that includes some rules of thumb for sizing a SQL Server system. NOTE: These are for sharepoin...
The Soft and Melting Duck Egg Meditation: (Moving the yang qi from the head) When Master Hakuin was just starting out upon his Zen c...