I have installed SQL 2000 tools, (Profiler is version 8.0.194) and now when
I try to connect to either a 7.0 or 2000 SQL Server using Profiler, the
following message comes up:
"In order to run a trace against SQL Server you have to be a member of
sysadmin fixed server role."
I KNOW this isn't true with 7.0 (I can run traces using the same login with
the 7.0 version of Profiler), and I seriously hope it's not true in 2000.
The books online say you need access to the xp_trace* procedures, which
makes sense, but even granting execute rights to these procedures in master
doesn't let me run Profiler. The only way I seem to be able to run traces
is by actually making the login in question a member of the sysadmin server
Say it ain't so! I have users who rely on using Profiler as a diagnostic
tool, but making everyone a member of the syadmin role is asking a bit much
just for this functionality?
Is this a new rule in 2000? Is there any way to get the 2000 version of
profiler to run traces against a 7.0 server that does in fact have
Management Reports, Int.