Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have database and specifically one table that is used for batch data transfer from another organization. With each run the table is truncated and rows are re-inserted. I want to handle that process in a more robust way, but I need to find out if the other system is doing its work in a single transaction with INSERT/VALUES or smaller individual statements. There is a substantial amount of data, so I don't want to capture the whole payload. The instance is SQL Server 2005 Standard.

What's the most lightweight way to capture details of this transfer?

share|improve this question
Run a server-side trace for a couple of minutes during an operation? This should be enough data to give you a sense of what they are doing. – Aaron Bertrand Mar 27 '14 at 22:27
The timing is extremely variable. I may have to leave it running overnight; that's why I want minimize the impact. – Jeff Sacksteder Mar 27 '14 at 23:34
well, I'm not sure what to tell you - either you want to capture enough information to see what the code is doing, or you don't. :-) A server-side trace to a file, preferably on a different server, shouldn't be too bad (just don't use Profiler) as long as you filter it to, say, the host name or app name in question... – Aaron Bertrand Mar 27 '14 at 23:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.