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.
| Author |
Topic |
|
johntrmns
Starting Member
1 Post |
 Posted - 2006-09-01 : 11:10:30
|
| I noticed that when I upgraded from SQL Server 2000 to SQL Server 2005 I could now only see my processes in an sp_who/sp_who2. It turns out you need to be a sysadmin in 2005 to see all user procedures running. I work next to a few other developers and we're all querying the database so oftentimes we have to check and see what conflicting processes are running. Is there GRANT permission that will enable me to restore this functionality? I can't seem to find one in books online that's solely for this purpose.Thanks. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-09-01 : 11:43:25
|
| from bol - sysprocessesIf a user has VIEW SERVER STATE permission on the server, the user will see all executing sessions in the instance of SQL Server; otherwise, the user will see only the current session.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
sp_who2 2005 permissions question