I created a database in MS SQL Server 2000. Everything was working great until I found that a user can login to the server more than once at the same time. Is there a way to prevent this, especially the first login using a normal login screen and the second login using Query Analyzer?
SQL Server is a data repository and not a full access control system. Your database application should be the one in charge of controlling access to the back-end data. One popular way that I've seen this performed is by having the application login using one set of credentials and then managing the user credentials inside your custom application. This way, when a user attempts to login concurrently, your application can query a "currently logged in" users list and display the appropriate error message. The user's password won't allow him into Query Analyzer so there's no harm in attempting a connection.
Dig Deeper on SQL Server Database Modeling and Design
Learn how to create a SQL Server user authentication schema having password and tracked data changes requirements and how it involves Windows ...
Learn why SQL Server 2000 connection is lost on the client side when database administrator changes 'SA' password on the SQL Server domain.
Find how to create a SQL Server 2000 login account and then set user account rights to specific databases with "db_owner."
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.