I've been tasked with trolling for references to tables on a particular server/database. We're in the process of moving most of the data to a new machine, but the migration isn't well documented (or executed).
It's my suspicion that a lot of the jobs and processes still running on the old box are in vain.
I'd like to capture all table references in that database over the span of say, 45 days, but PLENTY of code is executed using sp_executesql().
Further, I've found that when stores procs are called, the code shown in SQL Profiler stops well before the entire definition of the sproc, potentially leaving out some references.
Can someone please help me work around these shortfalls with the Profiler? Is there a better approach without incurring too much overhead?
Thanks in advance SSC!