Installing sql: sp4

Showing posts with label sp4. Show all posts

Wednesday, March 21, 2012

Installing SQL Server 2005, then upgrading to Windows 2003 from 20

We have plans to upgrade all our current SQL Server 2000 SP4 servers to SQL
Server 2005. Most of those servers are running on Windows 2000 with plans
to also upgrade to Windows 2003. Are there any risks to upgrading the SQL
Server, then upgrading the OS to 2003 at a later time? Or is it recommended
to upgrade the OS, then SQL Server for better results? In other words,
should these upgrades be tied together or does really not make a difference?I haven't tried this sequence, but here is what I have learned fro upgrades
in the past. I prefer to upgrade in release sequence. Therefore, upgrade
to Windows 2003 then upgrade SQL 2000 to SQL 2005. Personally, I don't like
upgrading in place. I try to rebuild servers from scratch when I get a
chance. I use home-grown log shipping scripts to handle the cutover and can
generally keep the downtime to just a few minutes. Of course, this requires
a bit of spare hardware and some decent prep time but I really like having a
clean build. You also have the existing server as a fail-back for however
long you choose.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
news:D594190B-9FA1-4E80-BE41-E7C1680768F2@.microsoft.com...
> We have plans to upgrade all our current SQL Server 2000 SP4 servers to
> SQL
> Server 2005. Most of those servers are running on Windows 2000 with
> plans
> to also upgrade to Windows 2003. Are there any risks to upgrading the
> SQL
> Server, then upgrading the OS to 2003 at a later time? Or is it
> recommended
> to upgrade the OS, then SQL Server for better results? In other words,
> should these upgrades be tied together or does really not make a
> difference?|||Hi
I would concur with Geoff, as Windows 2003 is an environmental change is
should have less impact and less likely to require any application changes
(although configuration changes may be necessary!) and therefore I would do
it first. An upgrade to SQL 2005 is more likely to require code changes and
so require more time for preparation and testing.
John
"SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
news:D594190B-9FA1-4E80-BE41-E7C1680768F2@.microsoft.com...
> We have plans to upgrade all our current SQL Server 2000 SP4 servers to
> SQL
> Server 2005. Most of those servers are running on Windows 2000 with
> plans
> to also upgrade to Windows 2003. Are there any risks to upgrading the
> SQL
> Server, then upgrading the OS to 2003 at a later time? Or is it
> recommended
> to upgrade the OS, then SQL Server for better results? In other words,
> should these upgrades be tied together or does really not make a
> difference?|||We are looking at the extact ame scenerio. When you say you don't like
upgrading in place, do you mean Windows OS , SQL Server or both ? We agree
that a server rebuild it cleaner but we have never done a SQL server upgrade.
I am wondering if that is true for SQL server as well e.e Is a side-by-side
migration cleaner than an in-place upgrade ?
--
Thanks,
Flora
"Geoff N. Hiten" wrote:
> I haven't tried this sequence, but here is what I have learned fro upgrades
> in the past. I prefer to upgrade in release sequence. Therefore, upgrade
> to Windows 2003 then upgrade SQL 2000 to SQL 2005. Personally, I don't like
> upgrading in place. I try to rebuild servers from scratch when I get a
> chance. I use home-grown log shipping scripts to handle the cutover and can
> generally keep the downtime to just a few minutes. Of course, this requires
> a bit of spare hardware and some decent prep time but I really like having a
> clean build. You also have the existing server as a fail-back for however
> long you choose.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "SandiDBA" <SandiDBA@.discussions.microsoft.com> wrote in message
> news:D594190B-9FA1-4E80-BE41-E7C1680768F2@.microsoft.com...
> > We have plans to upgrade all our current SQL Server 2000 SP4 servers to
> > SQL
> > Server 2005. Most of those servers are running on Windows 2000 with
> > plans
> > to also upgrade to Windows 2003. Are there any risks to upgrading the
> > SQL
> > Server, then upgrading the OS to 2003 at a later time? Or is it
> > recommended
> > to upgrade the OS, then SQL Server for better results? In other words,
> > should these upgrades be tied together or does really not make a
> > difference?
>
>

Installing SQL Server 2005, then upgrading to Windows 2003 from 20

Friday, February 24, 2012

Installing SQL 7 SP4 is a Domain are domain accounts required

When installing SQL 7 (non clustered) on a server is it neccessary to use
domain accounts.
e.g. We have a web server that is part of the workgroup "workgroup" this web
server is to access via the application on it the SQL database that resides
on a separate server (also in "workgroup") is it neccessary to create a
domain and have both these servers as members?
Thank youThere is no domain account for a workgroup topology. You will want to use
sql login for your authentication.
-oj
http://www.rac4sql.net
"Bruce Gilbert" <bruce.gilbert@.cgi.com> wrote in message
news:%23GsIqzCDEHA.2424@.TK2MSFTNGP09.phx.gbl...
> When installing SQL 7 (non clustered) on a server is it neccessary to use
> domain accounts.
> e.g. We have a web server that is part of the workgroup "workgroup" this
web
> server is to access via the application on it the SQL database that
resides
> on a separate server (also in "workgroup") is it neccessary to create a
> domain and have both these servers as members?
> Thank you
>|||To answer you question specifically. You do not need a domain. However, all
connectivity to the SQL Server machine will either have to be done with SQL
authentication or passthrough authentication (the same NT user and password
on both the client and SQL Server machine)
Rand
This posting is provided "as is" with no warranties and confers no rights.

Sunday, February 19, 2012

Installing SP4 on New node in cluster on Win2K3

We have a single node cluster using SQL2K EE running on Win2K EE, and this
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:

> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas

"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony

installing SP4 for SQL 2000 on a cluster node

Hello,
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem Ã?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ekrem Ã?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> > Hello,
> >
> > I recently added a new win2k3 node to an existing SQL cluster and
> > installed
> > SQL Server 2000. The SQL installation for the new node was performed from
> > the active node.
> > I also installed SP4 from the active node. However, I am having SQL
> > connectivity issues when I fail over to the new node. I noticed that I
> > get
> > the following event log on the new node. It thinks that SP4 is not
> > installed
> > although it is. Does anyone know if SP4 should be installed from the
> > passive
> > node (the new node)? Does it matter which node we run the SP4
> > installation?
> >
> > Thank-you,
> >
> > WG
> >
> > Event Type: Information
> > Event Source: MSSQLSERVER/MSDE
> > Event Category: None
> > Event ID: 1
> > Date: 12/3/2007
> > Time: 3:02:41 PM
> > User: N/A
> > Computer: EAGNMNST18C
> > Description:
> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> > Server 2000 Desktop Engine (also called MSDE) that has known security
> > vulnerabilities when used in conjunction with the Microsoft Windows Server
> > 2003 family. To reduce your computer's vulnerability to certain virus
> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> > MSDE,
> > or both have been disabled. To enable these ports, you must install a
> > patch,
> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> > http://www.microsoft.com/sql/downloads/default.asp
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem Ã?nsoy" wrote:
>> Take a look at this page and ensure you followed the right direction.
>> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
>> --
>> Ekrem Ã?nsoy
>>
>> "Walid" <Walid@.discussions.microsoft.com> wrote in message
>> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>> > Hello,
>> >
>> > I recently added a new win2k3 node to an existing SQL cluster and
>> > installed
>> > SQL Server 2000. The SQL installation for the new node was performed
>> > from
>> > the active node.
>> > I also installed SP4 from the active node. However, I am having SQL
>> > connectivity issues when I fail over to the new node. I noticed that I
>> > get
>> > the following event log on the new node. It thinks that SP4 is not
>> > installed
>> > although it is. Does anyone know if SP4 should be installed from the
>> > passive
>> > node (the new node)? Does it matter which node we run the SP4
>> > installation?
>> >
>> > Thank-you,
>> >
>> > WG
>> >
>> > Event Type: Information
>> > Event Source: MSSQLSERVER/MSDE
>> > Event Category: None
>> > Event ID: 1
>> > Date: 12/3/2007
>> > Time: 3:02:41 PM
>> > User: N/A
>> > Computer: EAGNMNST18C
>> > Description:
>> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
>> > Server 2000 Desktop Engine (also called MSDE) that has known security
>> > vulnerabilities when used in conjunction with the Microsoft Windows
>> > Server
>> > 2003 family. To reduce your computer's vulnerability to certain virus
>> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
>> > MSDE,
>> > or both have been disabled. To enable these ports, you must install a
>> > patch,
>> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE
>> > from
>> > http://www.microsoft.com/sql/downloads/default.asp
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >

INstalling SP4 for MS SQLServer 2000

I'm updating my local database installation using my netowrk login as
the id under which SQLServer is being update (Administrator on the
operating system and SA role on the database server itself).

Has anyone encountered any problems and what is the work-around?What error are you getting?

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"byrocat" <bdealhoy@.sympatico.ca> wrote in message
news:1119981740.417309.35500@.o13g2000cwo.googlegro ups.com...
> I'm updating my local database installation using my netowrk login as
> the id under which SQLServer is being update (Administrator on the
> operating system and SA role on the database server itself).
> Has anyone encountered any problems and what is the work-around?

Wednesday, March 21, 2012

Installing SQL Server 2005, then upgrading to Windows 2003 from 20

Installing SQL Server 2005, then upgrading to Windows 2003 from 20

Installing SQL Server 2005, then upgrading to Windows 2003 from 20

Friday, February 24, 2012

Installing SQL 7 SP4 is a Domain are domain accounts required

Sunday, February 19, 2012

Installing SP4 on New node in cluster on Win2K3

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

INstalling SP4 for MS SQLServer 2000

Installing sql

Blog Archive

About Me