What's the overhead like for running a long SQL Server Profiler trace? Any considerations to running a 24 hour trace on production server? I'd like to get a good sample of what's going on when actual users are using the system instead of running mock-up sessions that try to mimic full spectrum of user activity.
Asked
Active
Viewed 58 times
0
-
I think the sql profiler is not a appropiate tool for a session for more than 24 hours. The main goal to use it is for debugging – Reporter Jul 20 '12 at 08:00
-
Thanks for the answer. What would you see is a reasonable length? 5 hours? 30 minutes? – hhuttunen Jul 20 '12 at 08:24
-
I'm not an expert for this. I think not longer than sixty minutes. – Reporter Jul 20 '12 at 08:30