title: SQL Server Logins, and Database Engine Connection States
body: <p>Earlier today I tried to deprecate an old SQL Login by opening the Login's property Window, navigating to the Status page and then I changed the <strong>Permission to connect to databae engine</strong> property to deny.</p>
  
  <p>The login was associated with an active directory group and although the group still exists and users are in it, the group (and associated login) are no longer used in SQL Server.  Bad idea.  Apparently this locked out all of my users that were in that group, even though they were associated with numerous other SQL Logins that had access to the databases they needed.</p>
  
  <p>As soon as I gave the Login Grant access again, my users had access to the Databases Server.</p>
  
  <p>My question is, is there thorough documentation on this behavior and any other gotchas that may arise when disabling/modifying old, deprecated SQL Server accounts?</p>
  
  <p>I have found <a href="http://msdn.microsoft.com/en-us/library/ms180015%28v=SQL.90%29.aspx" rel="nofollow">this MSDN article</a> which is the reference to this property, however, it doesn't mention that it would lock out any user associated with the Login.  Is there more information available?  I still have quite a bit of work to do and I'd prefer to not lock my user's out of the system again because of ignorance.</p>