Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are planning to migrate sql server from 2005 to 2008.We have decided to create user logins manually instead of migrating from 2005 server, as we have different applications (windows services) accessing our DBs.

Intention behind is , we want to categorize entires in Activity Monitor based on user login.So that we can identify which process consuming more DB reources.

Please suggest whether this is the best way or not and what is the maximum no of user login can be created on Database.

Thanks in advance...

share|improve this question

Separating logins for each different service is a good idea IMO to isolate the potential problems. The technical limit is 32767 for user connections but no one should be creating that many logins.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.