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