January 2, 2010 at 11:53 pm
I have a question and I hope you will help
Is there a way to prevent any user other than sa access to SQL server 2005
Because, as is well known to all when you download the SQL there are two options
Windows Authentication mode
SQL Server and Windows Authentication mode
January 3, 2010 at 3:08 am
why would you only allow sa to connect ?
Is it for sql server (software) maintenance ?
You could start sqlserver using the maintenance parameter. (check books onlin for startup parameters and the consequences)
Keep in mind, it is a BAD practise to use sa for applications.
It is a best practise to host sqlserver using a windows service account.
Please rephraze your question.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 6, 2010 at 6:15 am
You can do it simply by dropping/deactivating all logins and all of their associated users. Why you would want to do it, however, I'm not sure.
January 6, 2010 at 6:23 am
Or by activating a login trigger (needs sp2) which only alows 'sa' or members of sysadmins sqlgroup.
Could be usefull if you intend to acivate it for a maintenance window, but think of the consequences !!
Have a look at http://www.sqlservercentral.com/articles/Administration/64974/
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data and code to get the best help
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 8, 2010 at 9:09 am
Just out of curiosity, if your SQL Server is in a Domain, could you not do this by creating a login to deny connect permission to Domain Users? That would include the DBAs too, though . . . 😉
January 10, 2010 at 11:24 pm
I could, I suppose. The problem is that, aside from malevolent external intervention, the only people who have such write-access are the DBAs and the Sysadmins and none admit to doing it.
External malevolent intervention falls into the sphere of the sysadmins and I'll leave that to them. The lesson has taught me that we need a much more detailed logging system. At this point in time, the trace method suggested looks very appealing but I have to examine it in more detail.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply