Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Running SQL Profiler & Security

Author  Topic 

alunjg
Starting Member

15 Posts

Posted - 2006-03-23 : 16:34:08
Hi

I have had a request here to allow developers to run SQL Profiler against our SQL Server 2000 Production databases.

If I remember correctly, a user (NT or SQL) has to be a member of the SysAdmin group in SQL to do this; which is obviously not acceptable as only DBA's should have this right on a production sql server.

Does anyone have another solution for this?

Kind regards

Alun

SQLServerDBA_Dan
Aged Yak Warrior

752 Posts

Posted - 2006-03-24 : 13:19:18
quote:
Originally posted by alunjg

Hi

I have had a request here to allow developers to run SQL Profiler against our SQL Server 2000 Production databases.

If I remember correctly, a user (NT or SQL) has to be a member of the SysAdmin group in SQL to do this; which is obviously not acceptable as only DBA's should have this right on a production sql server.

Does anyone have another solution for this?

Kind regards

Alun




The fix for this is a simple one set solution: Upgrade to SQL Server 2005.

I don't even like giving the dev's a sysadmin role in dev. If they need it you'll need to upgrade or they can ask you to run the profile.

Daniel, MCP, A+
SQL Server DBA
www.dallasteam.com
Go to Top of Page

alunjg
Starting Member

15 Posts

Posted - 2006-03-24 : 16:52:12
Many thanks Daniel,

I just have 1 problem with that though - SQL2005 is not recognised as 'approved technology' by the company I work for, even if they have their own dedicated Microsoft Support Desk. Go figure on that one!!

Thanks again.
Go to Top of Page

graz
Chief SQLTeam Crack Dealer

4149 Posts

Posted - 2006-03-24 : 17:20:46
In SQL Server 2000 you do need to be a system administrator in order to run trace or profiler. There isn't an easy way around it that I know. The simplest thing would be to create a trace job that starts a trace and runs it for 15 minutes or so. Give them the ability to start the job and download the trace file.

===============================================
Creating tomorrow's legacy systems today.
One crisis at a time.
Go to Top of Page
   

- Advertisement -