Nightly Windows reboot

Is it OK to restart Windows every night when SQL Server 2000 is running on
the system? It just seems strange to me to shut the system down without
stopping SQL Server first.
Hello,
It is always good to restart the Server after SQL Server shutdown. What you
could do is create a batch file to stop SQL Server and SQL Server Agent and
keep it in a
folder which can be accessible only to operations. So as operations can
execute the batch file and restart the SQL Server machine...
This will ensure that all the transction will be either rollback or roll
forwared before the server shutdown.
Thanks
Hari
"JayKon" <JayKon@.discussions.microsoft.com> wrote in message
news:C1A3F257-EB2B-46FC-B117-2C4C406D20A5@.microsoft.com...
> Is it OK to restart Windows every night when SQL Server 2000 is running on
> the system? It just seems strange to me to shut the system down without
> stopping SQL Server first.
|||Operations? vas is das operations
Seriously, I'm on a government contract and they really do close at 5PM. So,
anything done overnight is automated.
Its just that I'm annoyed at the thought of anything but a controlled
shutdown.
"Hari Prasad" wrote:

> Hello,
> It is always good to restart the Server after SQL Server shutdown. What you
> could do is create a batch file to stop SQL Server and SQL Server Agent and
> keep it in a
> folder which can be accessible only to operations. So as operations can
> execute the batch file and restart the SQL Server machine...
> This will ensure that all the transction will be either rollback or roll
> forwared before the server shutdown.
> Thanks
> Hari
> "JayKon" <JayKon@.discussions.microsoft.com> wrote in message
> news:C1A3F257-EB2B-46FC-B117-2C4C406D20A5@.microsoft.com...
>
>
|||I did ask and got a vague response having to do with "system stability". I
think it is a belief going back to pre-NT 4.0, reinforced by the system hangs
that have since been identified as a Terminal Services/single user print
driver issues and what I suspect is a small memory leak in their primary
application.
Anyway, I'm really looking for a way to do a clean shutdown of the database
before the system shuts down, rather than let the system reboot do it, or to
find out if that reall even matters.
"Tibor Karaszi" wrote:

> I'd ask the one who decided this why he/she wanted to do it? It certainly isn't normal to restart
> windows or SQL Server regularly.
>
> I suggest that whenever you *do* need to shutdown Windows, that you first stop the SQL Server
> service. At Windows shutdown, Windows will give each service a "grace period" to stop. If the
> service haven't stopped itself within that grace period, Windows will do a hard stop of the service.
> And you probably want to avoid this. Some details and why you might not want this you find in:
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JayKon" <JayKon@.discussions.microsoft.com> wrote in message
> news:C1A3F257-EB2B-46FC-B117-2C4C406D20A5@.microsoft.com...
>
|||> >I did ask and got a vague response having to do with "system stability". I
> Yes, some tend to ignore how much the Windows platform has evolved over the past 1.5 decade.
Agreed.

>
>
> So did they/you fix the issue? Perhaps this was and old, and now fixed, issue and the reboot routine
> can be removed?
The printer issue is current and took me a week to ID. Someone is working on
it. The memory leak is suspected, but not confirmed.
Until I know much more, I have no intention of removing it.

>
> Did you read the article I posted a link to? That answers your "if that really matters" question.
I think we made our posts about the same time, I have scanned it now. It
basically says the server needs a little time to shutdown cleanly - always a
good idea.

> And if you want to let the service to have the time to shut down normally, just schedule a normal
> NET STOP command before the re-boot (and give it plenty of time to stop...).
I think this is what I want. Can I put it directly into Scheduled Events
15-30 minutes before the reboot?
|||Since I'm dealing with a vendor that is doing the admin, I've sent them a
question about adding it to the at file.
The "funny" part, is the manager is so comfortable doing this restart just
the way it is and I always have trouble explaining that when you set things
up properly, you just don't get issues.
His argument is an old one: is it really worth the time to fix it properly,
when rebooting will keep us running? My answer (which goes unspoken a lot) is
that it never should have been done that way in the first place.
Anyway, thanks.
"Tibor Karaszi" wrote:

> Yes, that seems reasonable. Or, depending on how you do the reboot, you might be able to add the NET
> STOP in the same job/event as the reboot (assuming you do the reboot from some bat file).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JayKon" <JayKon@.discussions.microsoft.com> wrote in message
> news:534C179A-E188-4867-8B14-74156E95C960@.microsoft.com...
>