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
>
Showing posts with label installing. Show all posts
Showing posts with label installing. Show all posts
Tuesday, March 27, 2012
Tuesday, February 14, 2012
do you have to recreate ODBC after installing MDAC 2.8
Hello:
I just want to ask a quick question just for my future reference. There's
no emergency or anything. Take this scenario.
Client workstations have an ODBC connection, and the Terminal Services box
has an ODBC connection. The versions of the ODBC driver are different, and
you want to make them the same.
So, you download and install MDAC 2.8 on the client workstations and the
Terminal Services box. The version of the ODBC driver, unfortunately, does
not change.
In order to get the versions updated, do the ODBC connections themselves
need to be recreated?
Thanks!
childofthe1980s
No...not necessarily. The only problems I've seen have been
just the general install issues on Terminal Server.
The driver version change doesn't change on which - TS or
the workstations? Did you verify with Component Checker? Did
you reboot? There are some different steps for installing
MDAC on TS - did you follow those?
How to Install ODBC or MDAC on Terminal Server
http://support.microsoft.com/?id=216149
-Sue
On Sun, 14 Jan 2007 09:59:00 -0800, childofthe1980s
<childofthe1980s@.discussions.microsoft.com> wrote:
>Hello:
>I just want to ask a quick question just for my future reference. There's
>no emergency or anything. Take this scenario.
>Client workstations have an ODBC connection, and the Terminal Services box
>has an ODBC connection. The versions of the ODBC driver are different, and
>you want to make them the same.
>So, you download and install MDAC 2.8 on the client workstations and the
>Terminal Services box. The version of the ODBC driver, unfortunately, does
>not change.
>In order to get the versions updated, do the ODBC connections themselves
>need to be recreated?
>Thanks!
>childofthe1980s
I just want to ask a quick question just for my future reference. There's
no emergency or anything. Take this scenario.
Client workstations have an ODBC connection, and the Terminal Services box
has an ODBC connection. The versions of the ODBC driver are different, and
you want to make them the same.
So, you download and install MDAC 2.8 on the client workstations and the
Terminal Services box. The version of the ODBC driver, unfortunately, does
not change.
In order to get the versions updated, do the ODBC connections themselves
need to be recreated?
Thanks!
childofthe1980s
No...not necessarily. The only problems I've seen have been
just the general install issues on Terminal Server.
The driver version change doesn't change on which - TS or
the workstations? Did you verify with Component Checker? Did
you reboot? There are some different steps for installing
MDAC on TS - did you follow those?
How to Install ODBC or MDAC on Terminal Server
http://support.microsoft.com/?id=216149
-Sue
On Sun, 14 Jan 2007 09:59:00 -0800, childofthe1980s
<childofthe1980s@.discussions.microsoft.com> wrote:
>Hello:
>I just want to ask a quick question just for my future reference. There's
>no emergency or anything. Take this scenario.
>Client workstations have an ODBC connection, and the Terminal Services box
>has an ODBC connection. The versions of the ODBC driver are different, and
>you want to make them the same.
>So, you download and install MDAC 2.8 on the client workstations and the
>Terminal Services box. The version of the ODBC driver, unfortunately, does
>not change.
>In order to get the versions updated, do the ODBC connections themselves
>need to be recreated?
>Thanks!
>childofthe1980s
Subscribe to:
Posts (Atom)