• DVSQL (3/26/2013)


    Never ran those before, but it's worth a try I guess. Would tracing a single table be that much of a load onto the server? This table barely gets used, and is very small in size.

    The thing with Trace, and where the other technologies I mentioned outshine it, is that you cannot key onto a specific table. You key onto Events, and then you filter from there. In your case you would likely need to Trace the SQL:StatementCompleted and SP:StatementCompleted Events and then add a filter to essentially say WHERE Database = 'YourDatabase' AND SQLText LIKE '%YourTableName%'. Finding accesses to your table this way would be horribly inefficient and could add significant load to your system. The reason it would add load is because each Event has to be evaluated and then the filter is applied. With the two Events I mentioned, that means every single SQL statement entering your system has to be evaluated to see if it was destined for your database, and then whether the SQL text contained your table name.

    With Audit and Change Data Capture (CDC) you actually do key onto a specific table so these methods are cleaner and have much less impact on your system

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato