SQLServer: problem with the Read-Only database.


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: SQLServer: problem with the Read-Only database.

  1. #1
    Michael Guest

    SQLServer: problem with the Read-Only database.


    Hi team, we have a problem with the read-only database.

    Problem description: We have 2 databases life databases our desktop application
    uses: one is production 'psccs00' and the other is archived 'ASCCS00', which
    is read-only. These databases are running on one server.

    We've noticed that for the last 3 of months (from September 2002, this is
    when the conversion from SQLServer 6.5 has been done) the log file looks
    a bit strange. Sample is shown below (Lines 2, 3, 4 and 5).

    2002-12-04 08:00:02.03 backup Log backed up: Database: psccs00, creation
    date(time): 2002/09/25(12:59:13), f
    2002-12-04 08:06:51.78 spid60 Starting up database 'ASCCS00'.
    2002-12-04 08:06:58.64 spid60 Starting up database 'ASCCS00'.
    2002-12-04 08:59:29.82 spid66 Starting up database 'ASCCS00'.
    2002-12-04 08:59:38.03 spid66 Starting up database 'ASCCS00'.
    2002-12-04 09:00:02.21 backup Log backed up: Database: psccs00, creation
    date(time): 2002/09/25(12:59:13), f
    2002-12-04 10:00:02.26 backup Log backed up: Database: psccs00, creation
    date(time): 2002/09/25(12:59:13), f

    It looks that the ASCCS00 (which is read-only database) is trying to restart
    itself for number of times within only a couple of seconds of the interval.
    Those lines "Starting up database 'ASCCS00'" appears mostly early in the
    morning but will be in the log file for at least once a day. We have the
    production database PSCCS00 which I believe does not do the same thing. The
    VB6 application, which uses those databases accessing them fine.

    Now, the question:
    - is anyone have experienced anything like this before
    - under which circurmstances that would possibly happen
    - would that be anything to do with the fact that this is the read-only database

    Any suggestions would be very much appreciated


  2. #2
    Daniel Reber Guest

    Re: SQLServer: problem with the Read-Only database.

    Is this SQL Server 2000? This looks like you have the "Auto Close" option
    on. The " Starting up database 'ASCCS00'" message may be from somebody
    trying to access it and SQL Server is opening the database. Try turning this
    off and see what happens.

    Daniel Reber
    Datamasters, Inc


    "Michael" <m2@hotmail.com> wrote in message
    news:3dee8534$1@tnews.web.devx.com...
    >
    > Hi team, we have a problem with the read-only database.
    >
    > Problem description: We have 2 databases life databases our desktop

    application
    > uses: one is production 'psccs00' and the other is archived 'ASCCS00',

    which
    > is read-only. These databases are running on one server.
    >
    > We've noticed that for the last 3 of months (from September 2002, this is
    > when the conversion from SQLServer 6.5 has been done) the log file looks
    > a bit strange. Sample is shown below (Lines 2, 3, 4 and 5).
    >
    > 2002-12-04 08:00:02.03 backup Log backed up: Database: psccs00,

    creation
    > date(time): 2002/09/25(12:59:13), f
    > 2002-12-04 08:06:51.78 spid60 Starting up database 'ASCCS00'.
    > 2002-12-04 08:06:58.64 spid60 Starting up database 'ASCCS00'.
    > 2002-12-04 08:59:29.82 spid66 Starting up database 'ASCCS00'.
    > 2002-12-04 08:59:38.03 spid66 Starting up database 'ASCCS00'.
    > 2002-12-04 09:00:02.21 backup Log backed up: Database: psccs00,

    creation
    > date(time): 2002/09/25(12:59:13), f
    > 2002-12-04 10:00:02.26 backup Log backed up: Database: psccs00,

    creation
    > date(time): 2002/09/25(12:59:13), f
    >
    > It looks that the ASCCS00 (which is read-only database) is trying to

    restart
    > itself for number of times within only a couple of seconds of the

    interval.
    > Those lines "Starting up database 'ASCCS00'" appears mostly early in the
    > morning but will be in the log file for at least once a day. We have the
    > production database PSCCS00 which I believe does not do the same thing.

    The
    > VB6 application, which uses those databases accessing them fine.
    >
    > Now, the question:
    > - is anyone have experienced anything like this before
    > - under which circurmstances that would possibly happen
    > - would that be anything to do with the fact that this is the read-only

    database
    >
    > Any suggestions would be very much appreciated
    >




  3. #3
    Uri Guest

    Re: SQLServer: problem with the Read-Only database.


    Hi Daniel,
    thanks for your message.

    I've just checked the database and it seems that this option was already
    OFF.

    Would you have any other idea why this would happen every time anyone tries
    to access it.

    Why it's then not happening with the normal (not read-only) database.

    Any suggestions would be very much appreciated.

    Thanks in advance

    Regards





    "Daniel Reber" <dreber@nospam.dminconline.com> wrote:
    >Is this SQL Server 2000? This looks like you have the "Auto Close" option
    >on. The " Starting up database 'ASCCS00'" message may be from somebody
    >trying to access it and SQL Server is opening the database. Try turning

    this
    >off and see what happens.
    >
    >Daniel Reber
    >Datamasters, Inc
    >
    >
    >"Michael" <m2@hotmail.com> wrote in message
    >news:3dee8534$1@tnews.web.devx.com...
    >>
    >> Hi team, we have a problem with the read-only database.
    >>
    >> Problem description: We have 2 databases life databases our desktop

    >application
    >> uses: one is production 'psccs00' and the other is archived 'ASCCS00',

    >which
    >> is read-only. These databases are running on one server.
    >>
    >> We've noticed that for the last 3 of months (from September 2002, this

    is
    >> when the conversion from SQLServer 6.5 has been done) the log file looks
    >> a bit strange. Sample is shown below (Lines 2, 3, 4 and 5).
    >>
    >> 2002-12-04 08:00:02.03 backup Log backed up: Database: psccs00,

    >creation
    >> date(time): 2002/09/25(12:59:13), f
    >> 2002-12-04 08:06:51.78 spid60 Starting up database 'ASCCS00'.
    >> 2002-12-04 08:06:58.64 spid60 Starting up database 'ASCCS00'.
    >> 2002-12-04 08:59:29.82 spid66 Starting up database 'ASCCS00'.
    >> 2002-12-04 08:59:38.03 spid66 Starting up database 'ASCCS00'.
    >> 2002-12-04 09:00:02.21 backup Log backed up: Database: psccs00,

    >creation
    >> date(time): 2002/09/25(12:59:13), f
    >> 2002-12-04 10:00:02.26 backup Log backed up: Database: psccs00,

    >creation
    >> date(time): 2002/09/25(12:59:13), f
    >>
    >> It looks that the ASCCS00 (which is read-only database) is trying to

    >restart
    >> itself for number of times within only a couple of seconds of the

    >interval.
    >> Those lines "Starting up database 'ASCCS00'" appears mostly early in the
    >> morning but will be in the log file for at least once a day. We have the
    >> production database PSCCS00 which I believe does not do the same thing.

    >The
    >> VB6 application, which uses those databases accessing them fine.
    >>
    >> Now, the question:
    >> - is anyone have experienced anything like this before
    >> - under which circurmstances that would possibly happen
    >> - would that be anything to do with the fact that this is the read-only

    >database
    >>
    >> Any suggestions would be very much appreciated
    >>

    >
    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center