Developers should have Dev boxes to play on, and they should be given SA
access to them if required. If the problem lies on a production box, then
it's the DBA's job to diagnose it, and to pass back the info back to the
developer. That's if the Dumb Bloody Admin ;) understands what's going on!

Chris
(The Nightmare Duhveloper)

-----Original Message-----
From: Farnsworth, Dave [mailto:[Email Address Removed] 20 June 2003 10:35
To: LazyDBA.com Discussion
Subject: RE: Profiler Question SQL Server 2K


DON'T DO IT!! If a duhveloper needs something traced in Profiler they
should go through the DBA. If you give them sysadmin they can have total
access to the system which means you lost control. If you give one
duhveloper Profiler then all will want it. Profiler takes up system
resource so you don't want multiple sessions of Profiler running at the same
time.

Dave(The Duhvelopers Nightmare)

-----Original Message-----
From: Chip Smith [mailto:[Email Address Removed] Thursday, June 19, 2003 1:58 PM
To: LazyDBA.com Discussion
Subject: Profiler Question SQL Server 2K


Developer wants to use profiler. Profiler wants sysadmin privvies. Any way
around this?

-- "Chip"
<<...OLE_Obj...>>
"It never Rains Under My Umbrella!"


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page