Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
alex_808
Starting Member
16 Posts |
 Posted - 2010-07-12 : 14:33:03
|
| Hi we have an SQL database with some what medium traffic and was wondering if it was reasonable to create a trace with sql profiler that logs every select,update,delete query 24/7 in a table.. is this common practice? or would this create too much overhead.I know this is extremely vague..just wondering if its a common practice.Thanks! |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-07-12 : 14:39:23
|
| Too much overhead. Just trace for specific items of interest when needed.If you really need to fully audit your database, look at auditing products like Lumigent AuditDB or such |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-07-12 : 15:03:48
|
| In addition, The profiler GUI should not be used to trace busy production servers, there's too much overhead. Tracing via the profiler GUI directly to a SQL table is the most intensive way of tracing and the one that will have the most impact on the traced server. (and by impact, I mean up to and including crashing it)--Gail ShawSQL Server MVP |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
SQL Usage Log