Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 296 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Superusers no longer able to see users in DB Info
Edward_Bloomfield
Member Posts: 155
Hi!
I have an especially strange issue with a client.
The client runs a NAV V4 database on V4.03 executables with a SQL2000 database back end.
They found that if they made their super users DBOwners on SQL, then the super users were no longer able to see other users on the database by going to the sessions in Database Information - Only their own session. This would happen to all users they configured this way and on different PCs.
When they took away the DBOwner permissions, things returned to normal and they could see other users listed.
Has anyone encountered this issue before?
Thank you!
I have an especially strange issue with a client.
The client runs a NAV V4 database on V4.03 executables with a SQL2000 database back end.
They found that if they made their super users DBOwners on SQL, then the super users were no longer able to see other users on the database by going to the sessions in Database Information - Only their own session. This would happen to all users they configured this way and on different PCs.
When they took away the DBOwner permissions, things returned to normal and they could see other users listed.
Has anyone encountered this issue before?
Thank you!
Edward Bloomfield
Lead Consultant
Theta
Lead Consultant
Theta
0
Answers
The client was using SQL2005, rather than SQL2000.
In 2005, the users need to be given the SecurityAdmin server role to do this, as DB_owners in one database no longer have permission to view the server state without this role.
Lead Consultant
Theta