MSSQL 7 Bug? sysxlogins Default DB? Security?

  • Hi,

    We still support a box with MSSQL 7/SP2 on NT4 ... mixed authentication

    Has anyone ever experienced the following or heard of this ...

    Our methodology for creating DEV databases is to backup a prod db and restore it, but as another name. We've done this successfully for years. Recently, maybe unrelated to backup methodology, we noticed 2 anomalies with sysxlogins; or Ent.Man > Security > Logins:

    1. several NT/mssql accounts default db's were NULL (yes, I've seen this when the account's default db has been dropped ... Note: no PROD db's are ever dropped from this server except for the DEV ones, and all NT/mssql accounts default db's are set to the PROD db's.) 

    2. several other NT/mssql accounts deafault db's were changed/set to a test/DEV db that they do not have access to.

    Any thoughts besides someone hacking and changing each account's default db manually?

     

    Many thanks. Jeff

  • 1st I hve seen when the account SID in the DB does not match that of the Server login. Not uncommon at all.

    2n however, I just have never come across or given any thought to if I have.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply