RE: SQL Profiler won't allow a developer to login

Charles,

Thanks for your response...However, I am very confused. as a test I removed
my name from any Active Directory group and any local group that gives me
access to use the SQL Server. Sure enough when I tried to connect to the SQL
server using Management Studio I got the expected "Invalid Login". I then
added myself to the developer domain group. Now I can logon to the SQL
Server. Interestingly though I could also start the Profiler app... So I now
have the same permissions as the other developers, I can use profiler but
they cannot.. Does that make sense?? I'm using the Active directory group and
I have access so I don't believe there could be a policy issue here...

I looked at the monitor tool you suggested but I'm a little confused as the
profiler tool does not run on the server, it's running on my client..There is
no process on the server I can filter..or is there??

Anyway, just wanted to let you know what I'd found...Hopefully you will have
an idea why identical permissions (seemingly identical) give two different
people different experiences??

Thanks
Jason

"Charles Wang[MSFT]" wrote:

Hi Jason,
Thanks for your post.

From your description, I understand that:
Your developers could not load SQL Profiler although you had assigned ALTER
TRACE permission to the logins. When you added them to local administrators
group, they can run it successfully.
If I have misunderstood, please let me know.

In your description, you mentioned:
"The group has SysAdmin access on the server and each of the developers can
do anything on the server except 2 things. They can't login with SQL
Profiler and they can't import SSIS packages. These two things may be
related or not but I'm wondering if giving access through Active directory
groups is causing the problem??"

Did you mean that you assign ALTER TRACE permission to the Active Directory
user groups in SQL Server, but not each developer's domain account?
I performed a test at my side and everything worked fine. Since
establishing a domain environment may require a long time via our Lab, I
just performed a simple test on my local computer. My test steps are as
follows:
1. On my local computer, created a group named TestGroup;
2. Created a user named test and assigned it to the TestGroup;
3. Logged on SQL Server 2005, and added the group MyComputer\TestGroup as a
login to the Security->Logins folder;
4. Granted the ALTER TRACE permission to the group login account:
Use Master
Go
GRANT ALTER TRACE TO [MyComputer\TestGroup]
Go
5. In Start menu, right click SQL Profiler, select "Run as...", and input
[MyComputer\test] as the user to run SQL Profiler;
6. After SQL Profiler opened, select Windows Authentication (the login
account was [MyComputer\test]) and click Connect.

Then I found that it worked fine. SQL Profiler could monitor SQL Server
2005 activities correctly. I also tried adding another windows user account
to the TestGroup and then run SQL Profiler as the new user and it also
worked. I also checked the permissions requirement for Profiler in SQL
Server 2005 Books Online and it said that to run SQL Server Profiler, users
must be granted the ALTER TRACE permission. Combined with my test, I
believe that it is not necessary to assign them to your local
administrators group to run SQL Profiler.

Is it possible that there are some Domain group policies to prevent that
you run SQL Profiler from non-administrator account? You may contact your
domain network administrator for further investigation. Also you may
manually run Process Monitor to monitor your SQL Profiler process (Filter:
Process Name = PROFILER90.EXE) to see if there are file or registry
permission issues. If you would like, you could mail it to me
(changliw_at_microsoft_dot_com) for further research. You can download
Process Monitor from:
Process Monitor v1.25
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

If you have any other questions or concerns, please feel free to let me
know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



.

Relevant Pages

  • Re: Performance questions
    ... >> What I normally do when a query is running slowly against SQL Server ... The SQL Profiler will only work with SQL Server. ...
    (microsoft.public.access.queries)
  • Re: SQL through Front Page
    ... Run SQL Profiler and see what statement is being sent to the ... >database through Database Results Wizard and an asp page and the error comes ... >your server administrator. ...
    (microsoft.public.sqlserver.clients)
  • Re: Performance questions
    ... > tables is to use the SQL Profiler to find out exactly what SQL is arriving ... These aren't SQL Server tables though. ...
    (microsoft.public.access.queries)
  • Re: Timeout after "a while" problem
    ... > The service using the CPU is SQL Server (IIS is not running on the ... > database server). ... > Oh, when I run SQL Profiler while it's happening, I do not see any of ... > the SQL commands from the machines that are timing out. ...
    (microsoft.public.sqlserver.programming)
  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)