cannot write to sql 2000 database after about 2 hours uptime

Hi
I have a sql 2000 sp3 database running on SBS 2003 that seems to
ignore any writes after about 2 hours of it being up. It works fine after i
reboot the server or restart the sql service, but after a couple hours it
will not edit the database again. If i restart the service, it works fine
again. Also, i was looking at the sql logs and they are odd. it says
'starting up database {my database name}' about 20 times in a row when the
database is started, then says 'Configuration option 'show advanced options'
changed from 1 to 1. Run the RECONFIGURE statement to install' and then
gives an error 15457. Please help me fix my database.
Thanks in advance.
Leszek
Hi
Error 15457 is just an informational one. Ig gets generated the Enterprise
Manager and has nothing to do with the Db issue.
If there are no other errors in you event log, it means that SQL is Ok and
your application is the problem.
You may want to make sure that your DB is not set as 'Auto Close' as this
affects performance.
Regards
Mike
"Leszek" wrote:

> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>
>
|||Hi
Db is not set as 'Auto Close'. I have noticed that problem occured when is
more then 100 process in sql .
Regards
Leszek
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...[vbcol=seagreen]
> Hi
> Error 15457 is just an informational one. Ig gets generated the Enterprise
> Manager and has nothing to do with the Db issue.
> If there are no other errors in you event log, it means that SQL is Ok and
> your application is the problem.
> You may want to make sure that your DB is not set as 'Auto Close' as this
> affects performance.
> Regards
> Mike
> "Leszek" wrote:
after i[vbcol=seagreen]
it[vbcol=seagreen]
fine[vbcol=seagreen]
the[vbcol=seagreen]
options'[vbcol=seagreen]
then[vbcol=seagreen]
|||The problem here is not going to be an easy one to fix.
There are a couple of things you can look at however to
get a bit closer to the proble.
Firstly have you run the performance monitor to see what
is happening to your server i.e. Disk, Memory and the like.
Secondly you may want to set up a trace to see what
commands are being sent to the server.
Finally another thing you can do is send me a copy of your
database script, I don't need the table definitions, sp,
views or functions, just the configuration options when
you create the database, for security purposes leave the
create database statement in, but change the db name. I
will have a quick look at it and see if I can spot
anything odd.
Finally what is your server specification i.e. ram, hard
disk space ect.
My email if you need it is
peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
Peter
"The length of this document defends it well against the
risk of its being read."
Winston Churchill

>--Original Message--
>Hi
>Db is not set as 'Auto Close'. I have noticed that
problem occured when is
>more then 100 process in sql .
>Regards
>Leszek
>
>"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
message[vbcol=seagreen]
>news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
generated the Enterprise[vbcol=seagreen]
that SQL is Ok and[vbcol=seagreen]
as 'Auto Close' as this[vbcol=seagreen]
2003 that seems to[vbcol=seagreen]
It works fine[vbcol=seagreen]
>after i
after a couple hours[vbcol=seagreen]
>it
service, it works[vbcol=seagreen]
>fine
are odd. it says[vbcol=seagreen]
times in a row when[vbcol=seagreen]
>the
option 'show advanced[vbcol=seagreen]
>options'
to install' and
>then
>
>.
>
|||Aplication works since few monts on other server and there everything is
fine.
Regarding performance monitor. When system works fine and i try to open site
with many difficult query , procesor usage show about 50 % and it take 10
sec - site is loaded. If it doesn't work procesor usage is always about 1%
but i can't load the site.
Sql Profile show that query is sent to server.
Leszek
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:158001c4a221$b242cfc0$a301280a@.phx.gbl...[vbcol=seagreen]
> The problem here is not going to be an easy one to fix.
> There are a couple of things you can look at however to
> get a bit closer to the proble.
> Firstly have you run the performance monitor to see what
> is happening to your server i.e. Disk, Memory and the like.
> Secondly you may want to set up a trace to see what
> commands are being sent to the server.
> Finally another thing you can do is send me a copy of your
> database script, I don't need the table definitions, sp,
> views or functions, just the configuration options when
> you create the database, for security purposes leave the
> create database statement in, but change the db name. I
> will have a quick look at it and see if I can spot
> anything odd.
> Finally what is your server specification i.e. ram, hard
> disk space ect.
> My email if you need it is
> peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
> Peter
> "The length of this document defends it well against the
> risk of its being read."
> Winston Churchill
>
> problem occured when is
> message
> generated the Enterprise
> that SQL is Ok and
> as 'Auto Close' as this
> 2003 that seems to
> It works fine
> after a couple hours
> service, it works
> are odd. it says
> times in a row when
> option 'show advanced
> to install' and
|||Hi Leszek,
Have you used the enterprise manager to see if anything is locking a table
and preventing the updates? Perhaps a certain function or piece of code is
being executed after about 2 hours and that may look like the database won't
accept updates.
Wayne
"Leszek" <aaa@.addressnotexists.com> wrote in message
news:Odc7a3goEHA.2380@.TK2MSFTNGP14.phx.gbl...
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after
> i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced
> options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>