Post reply

"Something" wants to open up databases

  • August 20, 2004 at 12:32 am

    #360689

    Hi

    I have something that wants to access databases. Databases that are even not being used. They are old test databases. But when I look in the log, it looks like this :

    2004-08-19 10:30:39.35 spid74 Starting up database 'SR'.

    2004-08-19 10:30:39.82 spid74 Starting up database 'SO'.

    2004-08-19 10:30:40.20 spid74 Starting up database 'SR'.

    2004-08-19 10:30:40.65 spid74 Starting up database 'SO'.

    2004-08-19 10:30:41.07 spid74 Starting up database 'SR'.

    2004-08-19 10:30:41.49 spid74 Starting up database 'SO'.

    2004-08-19 10:30:41.87 spid74 Starting up database 'SR'.

    2004-08-19 10:30:42.27 spid74 Starting up database 'SO'.

    2004-08-19 10:30:42.80 spid74 Starting up database 'SR'.

    2004-08-19 10:30:43.21 spid74 Starting up database 'SO'.

    2004-08-19 10:30:43.59 spid74 Starting up database 'SR'.

    2004-08-19 10:30:43.99 spid74 Starting up database 'SO'.

    2004-08-19 10:30:44.38 spid74 Starting up database 'SR'.

    2004-08-19 10:30:44.84 spid74 Starting up database 'SO'.

    2004-08-19 10:30:45.18 spid74 Starting up database 'SR'.

    2004-08-19 10:30:45.59 spid74 Starting up database 'SO'.

    2004-08-19 10:30:46.49 spid74 Starting up database 'SR'.

    2004-08-19 10:31:37.10 spid74 Starting up database 'SO'.

     

    What can it be ?  How can i trace this ?

    Thx a lot !

    El Jefe


    JV

  • August 23, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • August 23, 2004 at 12:03 pm

    #520219

    When this is occuring, run DBCC INPUTBUFFER(##) in Query Analyzer. Run it in the instance where the databases are being openned. Replace the ## with the SPID (DBCC INPUTBUFFER(74)). That will tell you what they are running.

    In Enterprise Manager, you could expand down to Mangement/Current Processes and see what that SPID is being used by. (Remember to use the SPID from the current messages as the SPID is reused).

    Then if that doesn't give you enough information, run Profiler to create a trace. Look in BOL for more information on Profiler and traces.

    Also, check the databases in Enterprise Manager, right click on them and check their properties.  Make sure they are not set for AutoClose.

    -SQLBill

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

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