|
Home > Archive > MS SQL Server > December 2006 > System Commands used by SQL 2K Maintenance Plans?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
System Commands used by SQL 2K Maintenance Plans?
|
|
|
| I have a weekly maintenance plan set up using the maintenance plan wizard to
run optimizations to reindex the indexes. The name of the job that gets
created is like "Optimizations Job for DB Maintenance Plan 'DB Maintenance
Plan name'".
Lately it appears that this job has been conflicting with a non-SQL backup
job that is causing the server to shut down and my server manager would like
to know what exactly I am running. I have described what happens in general
terms but my server manager would like to know exactly what commands are
being run (SQL and Non-SQL commands) and I cannot find any information on
what commands are being run.
Thanks
| |
| Tracy McKibben 2006-12-12, 7:12 pm |
| Mike wrote:
> I have a weekly maintenance plan set up using the maintenance plan wizard to
> run optimizations to reindex the indexes. The name of the job that gets
> created is like "Optimizations Job for DB Maintenance Plan 'DB Maintenance
> Plan name'".
>
> Lately it appears that this job has been conflicting with a non-SQL backup
> job that is causing the server to shut down and my server manager would like
> to know what exactly I am running. I have described what happens in general
> terms but my server manager would like to know exactly what commands are
> being run (SQL and Non-SQL commands) and I cannot find any information on
> what commands are being run.
>
> Thanks
>
Nothing in the maintenance plans will cause a server to "shut down".
Can you provide a better description of what happens? Maybe with some
real error messages?
Depending on what options you've chosen in the plan wizard, it will some
mix of:
DBCC DBREINDEX
DBCC CHECKDB
Books Online will have more info..
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
| |
|
| I agree that nothing should be causing the server to shut down but that is
what is happening. From the Event Logs that I have looked at after these
"shut downs" when the server is brought back up, an entry in the System event
log says "The server shutdown/restart @ XX:XX:XX YYYYMMDD was unexpected..."
I have not seen any other error messages, etc. but there could be items in
our Corporate Backup solution regarding this, but I do not have access to
this.
We think there is a conflict between my job and the backup becuase the
shutdown occurs about 1 minute 30 seconds after my job starts. The
maintenance job is not complete in this case, because it typically takes 1.5
hours to run to completion.
This job usually only runs once a week but I was asked to schedule it last
night to see if one of the corporate backup configuration change corrected
this - it did not and the server went offline.
Unfortunetly at this point, this is all the info I have to provide.
Needless to say, my weekly optimization job has been disabled for the time
being.
Thanks for the info
"Tracy McKibben" wrote:
> Mike wrote:
>
> Nothing in the maintenance plans will cause a server to "shut down".
> Can you provide a better description of what happens? Maybe with some
> real error messages?
>
> Depending on what options you've chosen in the plan wizard, it will some
> mix of:
>
> DBCC DBREINDEX
> DBCC CHECKDB
>
> Books Online will have more info..
>
>
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
| |
| Scott Morris 2006-12-12, 7:12 pm |
| You can use the profiler to capture the actual statements issued by any
connection.
| |
| Tibor Karaszi 2006-12-12, 7:12 pm |
| .... and perhaps use the "blackbox" type of Profiler trace, to see what happens just before this
shutdown.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
"Scott Morris" <bogus@bogus.com> wrote in message news:u0czxyfHHHA.3424@TK2MSFTNGP02.phx.gbl...
> You can use the profiler to capture the actual statements issued by any connection.
>
| |
| Tracy McKibben 2006-12-12, 7:12 pm |
| Mike wrote:
> I agree that nothing should be causing the server to shut down but that is
> what is happening. From the Event Logs that I have looked at after these
> "shut downs" when the server is brought back up, an entry in the System event
> log says "The server shutdown/restart @ XX:XX:XX YYYYMMDD was unexpected..."
>
> I have not seen any other error messages, etc. but there could be items in
> our Corporate Backup solution regarding this, but I do not have access to
> this.
>
> We think there is a conflict between my job and the backup becuase the
> shutdown occurs about 1 minute 30 seconds after my job starts. The
> maintenance job is not complete in this case, because it typically takes 1.5
> hours to run to completion.
>
> This job usually only runs once a week but I was asked to schedule it last
> night to see if one of the corporate backup configuration change corrected
> this - it did not and the server went offline.
>
> Unfortunetly at this point, this is all the info I have to provide.
> Needless to say, my weekly optimization job has been disabled for the time
> being.
>
I would be looking at a possible hardware or driver problem that causes
an OS crash under heavy disk I/O. Could also be a memory issue.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|
|
|
|
|