Does sql server 2000 require a reboot?

Hi All,
I'm installing 2k developer, and the service pack 3a. Do either of these
require a reboot?
Thanks in advance
RyanSee the SP3a readme, section 3.4 (but I always reboot the computer after
installing a service pack. You need to take down SQL Server anyway if you
install an SP, so what's another 2 minutes for a server reboot?):
3.4 Stop Services and Applications Before Running SP3a Setup
The following information applies to all components.
You can apply SP3a without shutting down services. If you do not shut down
services, you are prompted to reboot the computer when Setup is complete.
Without rebooting, the following services fail to start:
a.. Microsoft Distributed Transaction Coordinator (MS DTC) and the
Microsoft Search and MSSQLServerOLAPService services.
b.. The MSSQLServer and SQLServerAgent services for the instance being
upgraded (for example, MSSQL$NamedInstance).
c.. Microsoft Component Services, Microsoft Message Queuing, and Microsoft
COM Transaction Integrator.
d.. All applications, including Control Panel. (optional)
You can apply SP3a without restarting your computer by stopping these
services and applications before applying the SP3a.
You cannot stop the services in a clustered environment. For more
information, see Section 3.10 Installing on a Failover Cluster.
Jacco Schalkwijk
SQL Server MVP
"Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
news:%23WDWxN0CEHA.688@.tk2msftngp13.phx.gbl...
> Hi All,
> I'm installing 2k developer, and the service pack 3a. Do either of these
> require a reboot?
> Thanks in advance
> Ryan
>|||Sorry, maybe I didn't make it clear. I'm installing SQL Server 2000
developer as well as the 3a service pack. I've since read that the service
pack requires a restart of the SQL Server services (which I'm not worried
about). I will do a re-boot at the end of the day, but the server is also a
file server, so don't want to do a reboot now after installing MS SQL Server
2000. Is this required?
Thanks
Ryan
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:esUq4m0CEHA.3132@.TK2MSFTNGP11.phx.gbl...
> See the SP3a readme, section 3.4 (but I always reboot the computer after
> installing a service pack. You need to take down SQL Server anyway if you
> install an SP, so what's another 2 minutes for a server reboot?):
> 3.4 Stop Services and Applications Before Running SP3a Setup
> The following information applies to all components.
> You can apply SP3a without shutting down services. If you do not shut down
> services, you are prompted to reboot the computer when Setup is complete.
> Without rebooting, the following services fail to start:
> a.. Microsoft Distributed Transaction Coordinator (MS DTC) and the
> Microsoft Search and MSSQLServerOLAPService services.
>
> b.. The MSSQLServer and SQLServerAgent services for the instance being
> upgraded (for example, MSSQL$NamedInstance).
>
> c.. Microsoft Component Services, Microsoft Message Queuing, and
Microsoft
> COM Transaction Integrator.
>
> d.. All applications, including Control Panel. (optional)
> You can apply SP3a without restarting your computer by stopping these
> services and applications before applying the SP3a.
> You cannot stop the services in a clustered environment. For more
> information, see Section 3.10 Installing on a Failover Cluster.
>
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
> news:%23WDWxN0CEHA.688@.tk2msftngp13.phx.gbl...
these
>|||You have to reboot your server after installing SQL Server 2000. You can
install it now though, and only do the reboot at the end of the day, before
you install the service pack.
Jacco Schalkwijk
SQL Server MVP
"Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
news:%23DlS7t0CEHA.1588@.tk2msftngp13.phx.gbl...
> Sorry, maybe I didn't make it clear. I'm installing SQL Server 2000
> developer as well as the 3a service pack. I've since read that the
service
> pack requires a restart of the SQL Server services (which I'm not worried
> about). I will do a re-boot at the end of the day, but the server is also
a
> file server, so don't want to do a reboot now after installing MS SQL
Server
> 2000. Is this required?
> Thanks
> Ryan
> "Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
> news:esUq4m0CEHA.3132@.TK2MSFTNGP11.phx.gbl...
you
down
complete.
> Microsoft
> these
>|||OK, thanks
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:ueIl8y0CEHA.464@.TK2MSFTNGP11.phx.gbl...
> You have to reboot your server after installing SQL Server 2000. You can
> install it now though, and only do the reboot at the end of the day,
before
> you install the service pack.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Breakspear" <r.breakspear@.removespamfdsltd.co.uk> wrote in message
> news:%23DlS7t0CEHA.1588@.tk2msftngp13.phx.gbl...
> service
worried
also
> a
> Server
after
> you
> down
> complete.
being
message
>

Do you regularly rebooting your server?

I would like to know if you reboot your SQL Server on a regular basis and why...

I do not regularly reboot our SQL Servers. They do get reboots when patches adn service packs are applied, but past that, I have found no need to reboot the servers.
|||Not by choice but monthly due to patches|||No. Only by office power cutoff (occurs time to time).|||

Never :-)

|||

If you don′t wanna have your data cache and your execution plans dropped every time you boot up the server, don′t do it. :-)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||If there weren't so dang many OS security patches, we would choose never. But, our company has opted for applying patches every other month. Many of our servers are using WSUS and unattended installs/reboots. We've had no troubles with this.
|||Come on, don't be shy, no one will judge you here. Or you could email me at dr_remove_sql@.hotmail.com if you don't want to tell the world.|||

Louis Davidson - SQL Server MVP wrote:

I would like to know if you reboot your SQL Server on a regular basis and why...

Funny you should ask...

Actually about a week ago our SQL 2005 server began to require a reboot about once per day. I'm no DB engineer or sys engineer so I can't tell you why. Our co-host is looking at he issue for us. I can tell you that there did not seem to be any irregularities in the logs and there's no storage issues. The websites just go down because the service fails, and I reboot it.

Drew

|||

We have our SQL server Servers rebooted every weekend if possible.

Why :

Patches

Some of our older SQL Servers are still on NT and SQL7 due to legacy application.

Development servers run applications that can have memory leaks.

If problems occure on reboot you will have a datum from when the server last rebooted successfully. Although servers are secured you can never be sure that someone has not been installing and not finished of with a reboot to ensure all that was working still works and no other errors have been introduced.

Prevents the 'worry' when a reboot is required and no ones done one for ages - we get this 'worry' with the unix server guys mostly. Rebooting apparently once introduced disk error problems due to power off on.

Cluster Servers - when failing over manually and rebooting the target before the switch ensures the servers are fully functioning and able to reboot. We have had problems with reboots in the past. -normally down to changes that have been made.

|||Hi, everybody.

Opened up a poll for this thread on http://www.sqlserver2005.de/Polls

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Awesome. Can't wait to see the results :)

Do you regularly reboot your server? (funny you should ask)

I would like to know if you reboot your SQL Server on a regular basis and why...

I do not regularly reboot our SQL Servers. They do get reboots when patches adn service packs are applied, but past that, I have found no need to reboot the servers.
|||Not by choice but monthly due to patches|||No. Only by office power cutoff (occurs time to time).|||

Never :-)

|||

If you don′t wanna have your data cache and your execution plans dropped every time you boot up the server, don′t do it. :-)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||If there weren't so dang many OS security patches, we would choose never. But, our company has opted for applying patches every other month. Many of our servers are using WSUS and unattended installs/reboots. We've had no troubles with this.
|||Come on, don't be shy, no one will judge you here. Or you could email me at dr_remove_sql@.hotmail.com if you don't want to tell the world.|||

Louis Davidson - SQL Server MVP wrote:

I would like to know if you reboot your SQL Server on a regular basis and why...

Funny you should ask...

Actually about a week ago our SQL 2005 server began to require a reboot about once per day. I'm no DB engineer or sys engineer so I can't tell you why. Our co-host is looking at he issue for us. I can tell you that there did not seem to be any irregularities in the logs and there's no storage issues. The websites just go down because the service fails, and I reboot it.

Drew

|||

We have our SQL server Servers rebooted every weekend if possible.

Why :

Patches

Some of our older SQL Servers are still on NT and SQL7 due to legacy application.

Development servers run applications that can have memory leaks.

If problems occure on reboot you will have a datum from when the server last rebooted successfully. Although servers are secured you can never be sure that someone has not been installing and not finished of with a reboot to ensure all that was working still works and no other errors have been introduced.

Prevents the 'worry' when a reboot is required and no ones done one for ages - we get this 'worry' with the unix server guys mostly. Rebooting apparently once introduced disk error problems due to power off on.

Cluster Servers - when failing over manually and rebooting the target before the switch ensures the servers are fully functioning and able to reboot. We have had problems with reboots in the past. -normally down to changes that have been made.

|||Hi, everybody.

Opened up a poll for this thread on http://www.sqlserver2005.de/Polls

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Awesome. Can't wait to see the results :)

Do you regularly reboot your server?

I would like to know if you reboot your SQL Server on a regular basis and why...

I do not regularly reboot our SQL Servers. They do get reboots when patches adn service packs are applied, but past that, I have found no need to reboot the servers.
|||Not by choice but monthly due to patches|||No. Only by office power cutoff (occurs time to time).|||

Never :-)

|||

If you don′t wanna have your data cache and your execution plans dropped every time you boot up the server, don′t do it. :-)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||If there weren't so dang many OS security patches, we would choose never. But, our company has opted for applying patches every other month. Many of our servers are using WSUS and unattended installs/reboots. We've had no troubles with this.
|||Come on, don't be shy, no one will judge you here. Or you could email me at dr_remove_sql@.hotmail.com if you don't want to tell the world.|||

Louis Davidson - SQL Server MVP wrote:

I would like to know if you reboot your SQL Server on a regular basis and why...

Funny you should ask...

Actually about a week ago our SQL 2005 server began to require a reboot about once per day. I'm no DB engineer or sys engineer so I can't tell you why. Our co-host is looking at he issue for us. I can tell you that there did not seem to be any irregularities in the logs and there's no storage issues. The websites just go down because the service fails, and I reboot it.

Drew

|||

We have our SQL server Servers rebooted every weekend if possible.

Why :

Patches

Some of our older SQL Servers are still on NT and SQL7 due to legacy application.

Development servers run applications that can have memory leaks.

If problems occure on reboot you will have a datum from when the server last rebooted successfully. Although servers are secured you can never be sure that someone has not been installing and not finished of with a reboot to ensure all that was working still works and no other errors have been introduced.

Prevents the 'worry' when a reboot is required and no ones done one for ages - we get this 'worry' with the unix server guys mostly. Rebooting apparently once introduced disk error problems due to power off on.

Cluster Servers - when failing over manually and rebooting the target before the switch ensures the servers are fully functioning and able to reboot. We have had problems with reboots in the past. -normally down to changes that have been made.

|||Hi, everybody.

Opened up a poll for this thread on http://www.sqlserver2005.de/Polls

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Awesome. Can't wait to see the results :)