Select to view content in your preferred language

How can DBO test other users in OS Auth SQL Server?

1118
2
Jump to solution
03-22-2013 08:09 AM
847396730
Frequent Contributor
Hello!  We're using SQL Server OS Auth, and I am DBO.  How can I mimic/test another users' experience?  When we were on DB Auth in Oracle, it was simple--just access the tables using the user's logon and password.  But OS Auth disallows this.  I can't test as a regular user, because I am always DBO.  What is the workaround?
Thank you!
0 Kudos
1 Solution

Accepted Solutions
MarcoBoeringa
MVP Alum
Your IT network administrators may not like it, but the only logical thing to do is to create a second OS account with "normal" user priviliges, instead of DBO, used for testing purposes. This account should not be coupled with a physical person, so that you can use it using the credentials of the account.

The whole purpose of being DBO is to be able to manage your (geo-)database. Changing the DBO account properties is therefore not a real option.

If your network administrators really don't allow it, or if you have a host of different specific permissions set for multiple users, than I guess one generic account won't do, and I guess being good friends with your non-DBO colleagues, is a must... or a switch over to "mixed mode authentication" with your SQL Server instance.

View solution in original post

0 Kudos
2 Replies
MarcoBoeringa
MVP Alum
Your IT network administrators may not like it, but the only logical thing to do is to create a second OS account with "normal" user priviliges, instead of DBO, used for testing purposes. This account should not be coupled with a physical person, so that you can use it using the credentials of the account.

The whole purpose of being DBO is to be able to manage your (geo-)database. Changing the DBO account properties is therefore not a real option.

If your network administrators really don't allow it, or if you have a host of different specific permissions set for multiple users, than I guess one generic account won't do, and I guess being good friends with your non-DBO colleagues, is a must... or a switch over to "mixed mode authentication" with your SQL Server instance.
0 Kudos
847396730
Frequent Contributor
Thank you for the reply; we did end up pursuing that exact outcome, and, believe it or not: the IT group happily complied!  Thanks again.
0 Kudos