Ive a got an sql server that crashes whenever a job runs for a minimum of
5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
doesnt matter if the job is scheduled, run manually, a backup, a reindex, a
data transfer, whatever, if it runs between 5 and 10 minutes, the box
crashes. Of course it happens most frquently during backups as they are run
the most. All ideas are appreicated.
--
SQL2K SP3
TIA, ChrisR"ChrisR" <bla@.noemail.com> wrote in message
news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> Ive a got an sql server that crashes whenever a job runs for a minimum of
> 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> doesnt matter if the job is scheduled, run manually, a backup, a reindex,
> a
> data transfer, whatever, if it runs between 5 and 10 minutes, the box
> crashes. Of course it happens most frquently during backups as they are
> run
> the most. All ideas are appreicated.
> --
> SQL2K SP3
> TIA, ChrisR
>
What do you mean by crashes? Does the O/S die and you get a blue screen?
Does SQL Server stop running, but the O/S is okay?
What version of O/S, what version of SQL Server? What service packs have
you installed.
What are you using for backups? Is it a standard SQL Server backup or are
you using some other program?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA|||> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
Blue screen.
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
Win2K sp4
SQL2K sp3a
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
Standard SQL.
Let me know if more info is required.
Thanks, ChrisR
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OZwiGUT4EHA.1452@.TK2MSFTNGP11.phx.gbl...
> "ChrisR" <bla@.noemail.com> wrote in message
> news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> > Ive a got an sql server that crashes whenever a job runs for a minimum
of
> > 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> > doesnt matter if the job is scheduled, run manually, a backup, a
reindex,
> > a
> > data transfer, whatever, if it runs between 5 and 10 minutes, the box
> > crashes. Of course it happens most frquently during backups as they are
> > run
> > the most. All ideas are appreicated.
> >
> > --
> > SQL2K SP3
> >
> > TIA, ChrisR
> >
> >
> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||What does the Application Log say?
Do you have anything else running on that server besides SQL 2k? (Exchange
maybe?).
Have you tried setting a max server memory for SQL Server? Tune it down a
bit and ensure that you leave enough RAM for the O/S.
(EM-> right-click on Server, Properties)
Rick Sawtell
MCT, MCSD, MCDBA|||The Event Viewer just says "the shut down at (time) was unexpected."
I just changed the memory so we'll see if that fixes anything.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OPykeeU4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> What does the Application Log say?
> Do you have anything else running on that server besides SQL 2k?
(Exchange
> maybe?).
> Have you tried setting a max server memory for SQL Server? Tune it down a
> bit and ensure that you leave enough RAM for the O/S.
> (EM-> right-click on Server, Properties)
> Rick Sawtell
> MCT, MCSD, MCDBA
>
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Wednesday, March 28, 2012
long running jobs crashing the box
Ive a got an sql server that crashes whenever a job runs for a minimum of
5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
doesnt matter if the job is scheduled, run manually, a backup, a reindex, a
data transfer, whatever, if it runs between 5 and 10 minutes, the box
crashes. Of course it happens most frquently during backups as they are run
the most. All ideas are appreicated.
SQL2K SP3
TIA, ChrisR
"ChrisR" <bla@.noemail.com> wrote in message
news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> Ive a got an sql server that crashes whenever a job runs for a minimum of
> 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> doesnt matter if the job is scheduled, run manually, a backup, a reindex,
> a
> data transfer, whatever, if it runs between 5 and 10 minutes, the box
> crashes. Of course it happens most frquently during backups as they are
> run
> the most. All ideas are appreicated.
> --
> SQL2K SP3
> TIA, ChrisR
>
What do you mean by crashes? Does the O/S die and you get a blue screen?
Does SQL Server stop running, but the O/S is okay?
What version of O/S, what version of SQL Server? What service packs have
you installed.
What are you using for backups? Is it a standard SQL Server backup or are
you using some other program?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
|||> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
Blue screen.
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
Win2K sp4
SQL2K sp3a
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
Standard SQL.
Let me know if more info is required.
Thanks, ChrisR
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OZwiGUT4EHA.1452@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> "ChrisR" <bla@.noemail.com> wrote in message
> news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
of[vbcol=seagreen]
reindex,
> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||What does the Application Log say?
Do you have anything else running on that server besides SQL 2k? (Exchange
maybe?).
Have you tried setting a max server memory for SQL Server? Tune it down a
bit and ensure that you leave enough RAM for the O/S.
(EM-> right-click on Server, Properties)
Rick Sawtell
MCT, MCSD, MCDBA
|||The Event Viewer just says "the shut down at (time) was unexpected."
I just changed the memory so we'll see if that fixes anything.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OPykeeU4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> What does the Application Log say?
> Do you have anything else running on that server besides SQL 2k?
(Exchange
> maybe?).
> Have you tried setting a max server memory for SQL Server? Tune it down a
> bit and ensure that you leave enough RAM for the O/S.
> (EM-> right-click on Server, Properties)
> Rick Sawtell
> MCT, MCSD, MCDBA
>
sql
5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
doesnt matter if the job is scheduled, run manually, a backup, a reindex, a
data transfer, whatever, if it runs between 5 and 10 minutes, the box
crashes. Of course it happens most frquently during backups as they are run
the most. All ideas are appreicated.
SQL2K SP3
TIA, ChrisR
"ChrisR" <bla@.noemail.com> wrote in message
news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
> Ive a got an sql server that crashes whenever a job runs for a minimum of
> 5 - 10 minutes. It doesnt happen 100% of the time, probably 80-90%. It
> doesnt matter if the job is scheduled, run manually, a backup, a reindex,
> a
> data transfer, whatever, if it runs between 5 and 10 minutes, the box
> crashes. Of course it happens most frquently during backups as they are
> run
> the most. All ideas are appreicated.
> --
> SQL2K SP3
> TIA, ChrisR
>
What do you mean by crashes? Does the O/S die and you get a blue screen?
Does SQL Server stop running, but the O/S is okay?
What version of O/S, what version of SQL Server? What service packs have
you installed.
What are you using for backups? Is it a standard SQL Server backup or are
you using some other program?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
|||> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
Blue screen.
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
Win2K sp4
SQL2K sp3a
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
Standard SQL.
Let me know if more info is required.
Thanks, ChrisR
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OZwiGUT4EHA.1452@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> "ChrisR" <bla@.noemail.com> wrote in message
> news:u%23$pQDT4EHA.936@.TK2MSFTNGP12.phx.gbl...
of[vbcol=seagreen]
reindex,
> What do you mean by crashes? Does the O/S die and you get a blue screen?
> Does SQL Server stop running, but the O/S is okay?
> What version of O/S, what version of SQL Server? What service packs have
> you installed.
> What are you using for backups? Is it a standard SQL Server backup or are
> you using some other program?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||What does the Application Log say?
Do you have anything else running on that server besides SQL 2k? (Exchange
maybe?).
Have you tried setting a max server memory for SQL Server? Tune it down a
bit and ensure that you leave enough RAM for the O/S.
(EM-> right-click on Server, Properties)
Rick Sawtell
MCT, MCSD, MCDBA
|||The Event Viewer just says "the shut down at (time) was unexpected."
I just changed the memory so we'll see if that fixes anything.
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:OPykeeU4EHA.4092@.TK2MSFTNGP14.phx.gbl...
> What does the Application Log say?
> Do you have anything else running on that server besides SQL 2k?
(Exchange
> maybe?).
> Have you tried setting a max server memory for SQL Server? Tune it down a
> bit and ensure that you leave enough RAM for the O/S.
> (EM-> right-click on Server, Properties)
> Rick Sawtell
> MCT, MCSD, MCDBA
>
sql
Wednesday, March 21, 2012
logs of creating and deleteing jobs
Hello
Does anybody know where/if MSSQL (especially 2005) keeps logs of
creating and deleteing jobs?
Does anybody know where/if MSSQL (especially 2005) keeps logs of
creating and deleteing jobs?
Thanks in advance
BartoloNo, it does not. Jobs are simple entries in the MSDB database, if you
want to keep track of that you will either have to tweak the appropiate
procedure that access these tables or write a trigger on the tables if
you are not sure if someone directly manipulates the tables.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Thanks Jens,
I wrote that because, I realized that one of my db haven't got backup
job since few days. Job had been written before and I dont know who
could do that or why it disappeard.
Regards,
Bartolosql
Labels:
creating,
database,
deleteing,
especially,
hellodoes,
jobs,
jobsthanks,
logs,
microsoft,
mssql,
mysql,
ofcreating,
oracle,
server,
sql
Wednesday, March 7, 2012
Login Times
Yes there is.
Have a couple of jobs running.
Start the job at a specific time
In the first job put in EXEC sp_denylogin '<usr_name>'
Then if you need to kill any of the processes for that
user still in there.
in the second login put EXEC sp_grantlogin '<usr_name>'.
So you start the first job at say 7pm
And the second job at say 8.30am
Peter
"I may be drunk, Miss, but in the morning I will be sober
and you will still be ugly."
Winston Churchill
>--Original Message--
>Helo,
>Is there any way I could grant or deny a user login based
on the time of
>day?
>I'm running mad with this issue, since not everybody is a
full time
>employee, and for security reasons I would want to block
their logins when
>they are supposed to be out of the office.
>Thanks in advance.
>
>.
>Thanks!
I wasn't thinking about jobs at all... I was running mad trying to pull in
triggers, and even thinking about changing the network configuration... but
my head wasn't thinking on jobs at all and it's a really nice answer.
Thank you Peter.
"Peter The Spate" <anonymous@.discussions.microsoft.com> escribi en el
mensaje news:19dd01c4bb6a$f99c8b10$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes there is.
> Have a couple of jobs running.
> Start the job at a specific time
> In the first job put in EXEC sp_denylogin '<usr_name>'
> Then if you need to kill any of the processes for that
> user still in there.
> in the second login put EXEC sp_grantlogin '<usr_name>'.
> So you start the first job at say 7pm
> And the second job at say 8.30am
> Peter
> "I may be drunk, Miss, but in the morning I will be sober
> and you will still be ugly."
> Winston Churchill
>
> on the time of
> full time
> their logins when
Have a couple of jobs running.
Start the job at a specific time
In the first job put in EXEC sp_denylogin '<usr_name>'
Then if you need to kill any of the processes for that
user still in there.
in the second login put EXEC sp_grantlogin '<usr_name>'.
So you start the first job at say 7pm
And the second job at say 8.30am
Peter
"I may be drunk, Miss, but in the morning I will be sober
and you will still be ugly."
Winston Churchill
>--Original Message--
>Helo,
>Is there any way I could grant or deny a user login based
on the time of
>day?
>I'm running mad with this issue, since not everybody is a
full time
>employee, and for security reasons I would want to block
their logins when
>they are supposed to be out of the office.
>Thanks in advance.
>
>.
>Thanks!
I wasn't thinking about jobs at all... I was running mad trying to pull in
triggers, and even thinking about changing the network configuration... but
my head wasn't thinking on jobs at all and it's a really nice answer.
Thank you Peter.
"Peter The Spate" <anonymous@.discussions.microsoft.com> escribi en el
mensaje news:19dd01c4bb6a$f99c8b10$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes there is.
> Have a couple of jobs running.
> Start the job at a specific time
> In the first job put in EXEC sp_denylogin '<usr_name>'
> Then if you need to kill any of the processes for that
> user still in there.
> in the second login put EXEC sp_grantlogin '<usr_name>'.
> So you start the first job at say 7pm
> And the second job at say 8.30am
> Peter
> "I may be drunk, Miss, but in the morning I will be sober
> and you will still be ugly."
> Winston Churchill
>
> on the time of
> full time
> their logins when
Subscribe to:
Posts (Atom)