Hello there... thanks for reading my post.
Our company seems to have an issue that occurs consistently on EVERY
Sunday that several of my tech guys (and several outside sources) have
been unable to diagnose.
Basically the symptoms of the issue are this... (all simultaneously)
1) Inserts and update queries fail or timeout
2) BUT, Select queries and searches on our web site function perfectly
Enterprise manager loads fine... and there are no issues as far as
disk space or memory or CPU usage (its been monitored while the
symptoms have persisted). We have pretty solid machines - dual Xeons,
2 Gig mem, etc. There are no real scheduled tasks set for every
sunday, except one basic DB maintenance Job, and even when we
"descheduled" it, the same problem STILL popped up on Sunday.
Again, this occurs every Sunday like clockwork... usually 2 or 3
times during the day (and if I'm really lucky... 4:30 AM yay). The
server simply gets rebooted (stopping and starting the service does
not fix it), and the problem is remedied.
This has been troubling us for months now... If anyone has an answer
to this, I would be forever indebted to you.
Any help would be appreciated. Thanks!!On Mon, 4 Aug 2003 21:17:24 -0700, "Hassan" <fatima_ja@.hotmail.com>
wrote:
>Do you have any maintenance job running or scheduled around that time .
>Again, whats the error message received ?
>What SQL server version and OS are you using ?
>"Paul" <vibronic2k@.hotmail.com> wrote in message
>news:1l5uivcuc51fmbc2tusl9t8ukv8tfg1bv1@.4ax.com...
>> Hello there... thanks for reading my post.
>> Our company seems to have an issue that occurs consistently on EVERY
>> Sunday that several of my tech guys (and several outside sources) have
>> been unable to diagnose.
>> Basically the symptoms of the issue are this... (all simultaneously)
>> 1) Inserts and update queries fail or timeout
>> 2) BUT, Select queries and searches on our web site function perfectly
>> Enterprise manager loads fine... and there are no issues as far as
>> disk space or memory or CPU usage (its been monitored while the
>> symptoms have persisted). We have pretty solid machines - dual Xeons,
>> 2 Gig mem, etc. There are no real scheduled tasks set for every
>> sunday, except one basic DB maintenance Job, and even when we
>> "descheduled" it, the same problem STILL popped up on Sunday.
>> Again, this occurs every Sunday like clockwork... usually 2 or 3
>> times during the day (and if I'm really lucky... 4:30 AM yay). The
>> server simply gets rebooted (stopping and starting the service does
>> not fix it), and the problem is remedied.
>> This has been troubling us for months now... If anyone has an answer
>> to this, I would be forever indebted to you.
>> Any help would be appreciated. Thanks!!
Hi Hassan,
We're running MS SQL Server 2000 on Windows 2000. We're all up to
date on our patches and updates.
There seems to be no "error message" per se... it simply times out or
doesn't respond to insert or update commands.
Please refer to my other reply to mountainman if you can... a lot of
other details are in that post.
Thanks for trying to help.|||...[trimmed]...
> >5) Double-check that maintenance task by scheduling it outside
> >the weekend for a few weeks (eg: 11:00am during the week).
> >I have seen badly written maintenance tasks hang the system,
> >exactly as you have described, especially if multiple tasks are
> >executed in parallel. Are you positive there is only one task?
> >Are you positive it was "DESCHEDULED"?
> >What is its code?
> We have 5 jobs in the job list, 4 of which are daily, and one of which
> is weekly (on Sunday). The one scheduled on Sunday is...
> "Optomizations Job for DB Maintenance Plan 'DB Maintenance Plan1' I'm
> not sure what the "code" is, but when I look in the "schedules" tab
> for it, there is an ID of "94" with the name "Schedule1". Not sure if
> thats what you're looking for. In any case, we've turned off the job
> for a period of weeks at a time, and sure enough, it still rears its
> ugly head.
> Thanks for any help.
At what time on Sunday is this task scheduled?
Does the task show a history with normal start and end times?
(Right click task, select history - check/tick show step details)
>the server is housed at a web hosting facility - Interland to be
>specific. I don't believe the issue is related to the physical
>location.
Is the server dedicated to your organization alone?
If not, is there a likelihood that the server is hosting other databases and
process queues?
Specifically, running processes on the machine at these times which compete
with the
writing of your data to your database(s) on the server.
Has Interland provided any advice on the matter?
Are they responsible for the service on the machine?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment