Results 1 to 6 of 6
  1. #1
    Join Date
    Jan 2004
    Posts
    32

    Unanswered: Repeatedly starting databases

    Hi all,

    I've been handed a SQL Server that is used as an MIS source. There are 4 databases that carry out the task of importing data from various sources, then manipulting that data, and offering the data for reporting purposes.

    The vendor has also created several other databases (of which there are also 4), but no-one in my company seems to know the purpose of these dbs.

    In the logs, there are approximately 8/9 messages per second - not every second, but numberous seconds per minute - stating....

    Starting up database 'db_name'.

    ... each time, all 4 of the mysterious dbs appear.

    I've checked the spid that is running this job this morning, and it seems to be NT AUTHORITY\SYSTEM connected to one of the original 4 report databases.

    Does this have any affect on the performance of the server, or the specific db attached to the user?

    Thanks in advance.

    Duncan

  2. #2
    Join Date
    Jan 2003
    Location
    India
    Posts
    523

    Re: Repeatedly starting databases

    check the AUTO CLOSE option, i bet it is checked.

  3. #3
    Join Date
    Nov 2003
    Location
    Edinburgh
    Posts
    149
    Hi Duncan,

    The first thing I would do is get in touch with the vendor and find out what the purpose of these databases is???


    Cheers

  4. #4
    Join Date
    Jan 2004
    Posts
    32
    Thanks guys

    Yes auto close is checked.

    And yes, I'll contact the vendor to find out why they've done this.

    Before I do, could there be any benefit to this since the databases are used at least once a second (or maybe two seconds at most) throughout the day???

  5. #5
    Join Date
    Jan 2003
    Location
    India
    Posts
    523
    Originally posted by zinedunc
    Thanks guys

    Yes auto close is checked.

    And yes, I'll contact the vendor to find out why they've done this.

    Before I do, could there be any benefit to this since the databases are used at least once a second (or maybe two seconds at most) throughout the day???

    What this option does is closes the database connection after the last user disconnects from the database. when a user tries to acces the databases again and requests for the same, then the database has to be reopened, which takes time and overhead.
    Since your database is accessed frequentl, it has to be closed and reopened frequently which puts a large performance on the server and the users or the application which is using it.

  6. #6
    Join Date
    Jan 2004
    Posts
    32
    Thanks harshal_in

    I knew that that's what was happening, I just wanted a second opinion before I go banging some heads :-)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •