Post reply

Database Setting to single user

  • July 9, 2004 at 10:51 pm

    #108496

    we are having individual systems having win2k and sql2k running and application developed on vb.  Some times the database status was automatically setting to single user mode.  Is it any installation problem or application or maintenance problem..

     

     

  • July 10, 2004 at 9:57 pm

    #514207

    To find out what is causing this, set up Profiler to trace the events.  You will need this event:

    SucurityAudit..Audit Object Permissions Event

    You'll want to include Database Name, DBUserName, HostName, TextData, ApplicationName, NTUserName, LoginName, and ClientProcessID (PID on Host Server).

    This should give you plenty of information to pinpoint what's causing the status to change.  Dump the results of the Profiler to a table in SQL Server and use this query to search it.

    SELECT

     [Database Name],

     DBUserName,

     HostName,

     TextData,

     ApplicationName,

     NTUserName,

     LoginName,

     ClientProcessID

    FROM

     tablename

    WHERE

     TextData LIKE '%sp_dboption%'

    Derrick Leggett
    Mean Old DBA
    When life gives you a lemon, fire the DBA.

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

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