December 25, 2003 at 1:42 am
Hi!
Development guys claim that they need SA role to run Profiler on production servers.
Just need arguments why running Profiler on production servers is a bad practice.
Thanks.
December 26, 2003 at 6:05 am
I don't think running profiler is a bad practice. There always a need to run profiler and maybe the development guys need to know what the app is executing to resolve a bug.
And yes you need sa rights to run profiler. Maybe you can run it so you don't give them sa rights.
December 26, 2003 at 6:06 am
I don't think running profiler is a bad practice. There always a need to run profiler and maybe the development guys need to know what the app is executing to resolve a bug.
And yes you need sa rights to run profiler. Maybe you can run it so you don't give them sa rights.
December 28, 2003 at 1:40 am
I agree with racosta.... profiler is sometimes (no, make that often) a necessity on a production server.
But, handing the profiling duty to the dev guys is something I would recommend against. If however your management gives it the nod, then maybe I would give them sysadmin privilege either through Windows authentication or the creation of a new sysadmin sql login. Unless complete trust exists, I would also schedule a continual profiler trace to ensure that login only uses "SQL Profiler" and to capture anything done.
Cheers,
- Mark
Cheers,
- Mark
December 29, 2003 at 2:35 pm
Do agree that Profiler is most necessary! But it can be a performance hit. We run profiler on our DEV server - connected to the Production server - so the DEV server takes the performance hit while it captures Production info.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply