Applying SQL hotfixes to a SQL cluster

Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
SpinRecent hotfix installers are typically cluster aware. So in general you don'
t
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes fo
r
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:

> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it i
s
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>

Applying SQL hotfixes to a SQL cluster

Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
--
SpinRecent hotfix installers are typically cluster aware. So in general you don't
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes for
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it is
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>|||Hi gurus,
I have a problem. For security purposes I work with two databases; I
use one as production DB (pdb) and the other (cdb) serves as a secure
copy of the production database; and I want to regularly update the
secure copy with the work that I do in the production databasse i.e.
update exsiting stored procedures, tables, views and diagrams or copy
new ones into the secure copy.
A program that at the end of each session in the production db asks if
I want to update the secure copy.
Anyone has an idea for a begginner?
Thanks
Yao
Tony Rogerson wrote:
> Make sure Windows Task Schedular is running on both machines, the setup uses
> it to apply the hotfix to the other node.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
> Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Spin" <Spin@.spin.com> wrote in message
> news:4ifir0F3grg8U1@.individual.net...
> > Gurus,
> >
> > Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> > 2003 SP1 is the OS. Are there any special rules I must follow to execute
> > the SQL hotfix on each node of the cluster? I am assuming I just need to
> > apply the SQL hotfix to each cluster node and that's it. I am hoping it
> > is that easy.
> >
> > --
> > Spin
> >
> >sql

Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangås" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.207.46.248.16...
> http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangås
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP

Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.

Basically, I have 2 servers. Server A runs a default instance and another instance. While the default services is disabled and the other instance is running, Server B runs the default instance and has the other instance disabled. This basically acts like a 2 way cluster (active/passive).

How can I apply SQL Server 2000 SP4 on the 2 servers and have all the nodes come up the correct way? What are the steps to achieve this?Since SQL Server is a shared resource on a clustered server, installing SP4 on one server is automatically done on the other. Everything is transparent to the user/admin.sql

Applying SP4 on an active/passive 2 way cluster

I have a 2 way cluster and I want to apply SP4 on it.
Basically, I have 2 servers. Server A runs a default instance and
another instance. While the default services is disabled and the other
instance is running, Server B runs the default instance and has the other
instance disabled. This basically acts like a 2 way cluster
(active/passive).
How can I apply SQL Server 2000 SP4 on the 2 servers and have all the
nodes come up the correct way? What are the steps to achieve this?http://download.microsoft.com/downl...584E-4DE0-B36F-
C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||This is not going to help me. I have explicitly mentioned that I have a 2
way cluster in my original email. So a standard article like you have given
me is NOT going to help.
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns981DB671F914Folekristianbangaas@.
207.46.248.16...
> http://download.microsoft.com/downl...584E-4DE0-B36F-
> C44E06B0D2A3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:

> This is not going to help me. I have explicitly mentioned that I have
> a 2 way cluster in my original email. So a standard article like you
> have given me is NOT going to help.
Yes, and I don't quite get the problem. Let me quote point two in the
article I gave a link to:
"Run the service pack from the node that owns the group containing the
virtual server that you plan to upgrade. This installs the service pack
files on all nodes in the failover cluster."
Can you please explain what your problem is? As I understand your scenario
you have a two-node two-instance active-passive SQL cluster. An upgrade of
that cluster should be rather straightforward.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||"Shiva" <arbitsquare@.hotmail.com> wrote in
news:OTKiIkivGHA.2120@.TK2MSFTNGP03.phx.gbl:
Correction to my previous post, You actually have an active/active
confuguration, with one instance on each server, but the upgrade procedure
is still valid.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP

Applying SP3a to SQL 2000 cluster - Problem

I have added two new nodes to the cluster and successfully installed SQL 2000
on both. I am trying to apply SP3a to both and am getting the message
"18:01:30 One or more errors occurred while running remote setup on the
clustered machines.
18:01:35 Setup failed to perform required operations on the cluster nodes."
Active/passive cluster. active node is up and working. But I have only a 1
node cluster at the moment.
Additonal from sqlsp.log:
17:55:49 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=1
Server.1=GSOSVSQLCLS1D
[Server.1]
NumRemoteServices=1
1.app="\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\ x86\setup\setupsql.exe"
1.server=GSOSVSQLCLS1D
1.script=\\GSOSVSQLCLS1A\admin$\GSOSVSQLCLS1D_MSSQ LSERVER.iss
1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
"\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\x86\se tup\setup.ins" -f1 %s -f2
"\\GSOSVSQLCLS1D\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
1.user=GILBARCO\skipper
1.name=SQLSetup1
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
17:55:49 Setup is performing required operations on cluster nodes. This may
take a few minutes...
17:55:49 "C:\DOCUME~1\hall\LOCALS~1\Temp\SqlSetup\Bin\remse tup.exe"
C:\WINNT\remsetup.ini
18:01:30 Process Exit Code: (-12)
18:01:30 Begin Action : GetRemsetupRetCode
18:01:30 Installation return status on GSOSVSQLCLS1D : -12
18:01:30 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 05/26/07 17:55:49 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x84] created for execution.
CThread::Process [0x84]
CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=0
Script file copied to '\\GSOSVSQLCLS1D\ADMIN$\GSOSVSQLCLS1D_MSSQLSERVER. iss'
successfully.
Installing remote service (GSOSVSQLCLS1D)...
CRemoteProcess::RunUntilComplete [0x84] exit code: -12
Remote process exit code was '-12' (GSOSVSQLCLS1D).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
Thread [0x84] exit code: [0xfffffff4]
CThreadPool::RunUntilComplete returned -12
CThreadPool::RunUntilComplete execution level=1, need execution: 0
One or more errors occurred while running the remote/unattended setups.
Disconnecting from remote machine (GSOSVSQLCLS1D)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 05/26/07 18:01:30 ####
18:01:30 End Action : Run setup on cluster nodes
18:01:30 One or more errors occurred while running remote setup on the
clustered machines.
18:01:35 Setup failed to perform required operations on the cluster nodes.
18:01:35 Begin Action : ClusterErrorCleanup
18:01:35 End Action : ClusterErrorCleanup
18:01:35 End Action : ClusterSetupHelper
18:01:35 Begin Action : LogEvent
18:01:35 End Action : LogEvent
18:01:35 Begin Action : CloseEventLog
18:01:35 End Action : CloseEventLog
Pat is there anything in the cluster log, application log or the system log.
Need more information so troubleshoot.
Thanks
John Vandervliet
"Pat Hall" wrote:

> I have added two new nodes to the cluster and successfully installed SQL 2000
> on both. I am trying to apply SP3a to both and am getting the message
> "18:01:30 One or more errors occurred while running remote setup on the
> clustered machines.
> 18:01:35 Setup failed to perform required operations on the cluster nodes."
> Active/passive cluster. active node is up and working. But I have only a 1
> node cluster at the moment.
> Additonal from sqlsp.log:
> 17:55:49 Begin Action : Run setup on cluster nodes
> [args]
> NumRemoteServers=1
> Server.1=GSOSVSQLCLS1D
> [Server.1]
> NumRemoteServices=1
> 1.app="\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\ x86\setup\setupsql.exe"
> 1.server=GSOSVSQLCLS1D
> 1.script=\\GSOSVSQLCLS1A\admin$\GSOSVSQLCLS1D_MSSQ LSERVER.iss
> 1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
> "\\GSOSVSQLCLS1A\C$\Service_Packs\sql2ksp3a\x86\se tup\setup.ins" -f1 %s -f2
> "\\GSOSVSQLCLS1D\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
> 1.user=GILBARCO\skipper
> 1.name=SQLSetup1
> 1.sqlsetup=Y
> 1.copyexe=cnvsvc1.exe
> 17:55:49 Setup is performing required operations on cluster nodes. This may
> take a few minutes...
> 17:55:49 "C:\DOCUME~1\hall\LOCALS~1\Temp\SqlSetup\Bin\remse tup.exe"
> C:\WINNT\remsetup.ini
> 18:01:30 Process Exit Code: (-12)
> 18:01:30 Begin Action : GetRemsetupRetCode
> 18:01:30 Installation return status on GSOSVSQLCLS1D : -12
> 18:01:30 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 05/26/07 17:55:49 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x84] created for execution.
> CThread::Process [0x84]
> CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=0
> Script file copied to '\\GSOSVSQLCLS1D\ADMIN$\GSOSVSQLCLS1D_MSSQLSERVER. iss'
> successfully.
> Installing remote service (GSOSVSQLCLS1D)...
> CRemoteProcess::RunUntilComplete [0x84] exit code: -12
> Remote process exit code was '-12' (GSOSVSQLCLS1D).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
> Thread [0x84] exit code: [0xfffffff4]
> CThreadPool::RunUntilComplete returned -12
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> One or more errors occurred while running the remote/unattended setups.
> Disconnecting from remote machine (GSOSVSQLCLS1D)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 05/26/07 18:01:30 ####
>
>
>
>
>
>
>
> 18:01:30 End Action : Run setup on cluster nodes
> 18:01:30 One or more errors occurred while running remote setup on the
> clustered machines.
> 18:01:35 Setup failed to perform required operations on the cluster nodes.
> 18:01:35 Begin Action : ClusterErrorCleanup
> 18:01:35 End Action : ClusterErrorCleanup
> 18:01:35 End Action : ClusterSetupHelper
> 18:01:35 Begin Action : LogEvent
> 18:01:35 End Action : LogEvent
> 18:01:35 Begin Action : CloseEventLog
> 18:01:35 End Action : CloseEventLog
>
|||Found the problem, a bug in the SP3a install that will not let youi apply
SP3a to 2 new nodes at the same time. See KB318672.
Got SP3a applied and will be failing over tonight.
"John Vandervliet" wrote:
[vbcol=seagreen]
> Pat is there anything in the cluster log, application log or the system log.
> Need more information so troubleshoot.
> Thanks
> John Vandervliet
> "Pat Hall" wrote:

applying SP to 2005 active/active cluster

I have a 2005 active/active cluster and want to apply SQL server 2005 SP2 to both node.
I know that for active/passive , the sp can simple be installed on the active node(instance) and everything will be replicated to the other node.
bear in mind what I have SSIS and SSAS and SSRS running on the active/active cluster.

what is the rigth method for applying the SP to active\active cluster?

Thanks

We had the same situation a couple of weeks ago. When had several problems applying SP2 to the clustered machines. After talking to MS for several hrs about our problems, we finally corrected it....it was issues with different settings on our cluster. However, MS did recommend having both instances on one server, the primary, when you do the upgrade. I can't remember if the SP was applied to both nodes though. If it is not, its no big deal. Just apply it to the second node. I hope you have better luck than we did.

PS. Make sure that DCOM is enabled on both servers.

Applying SP on SQL Cluster (active/passive) after new nodes Added

Ran into a problem in scheduling applying the Service Pack to our SQL
2000 active/passive cluster when we add new nodes. 50 plus databases and an
unknown number of apps.
I'm wondering what people do to ensure that no apps/people are trying to
access the databases when the service pack is applied.
Our application staff says there is no way they can guarantee that an
app or person will not try to access one of the databases while the service
pack is being installed.
My plan is to evict one of the existing nodes then add the two new nodes
one at a time and set up the heartbeat. Then install SQL 2000; then apply
SP3a. Yes I know SP4 is available; however, one of the apps will not run
with SP4.
The service pack brings the database engine up in single-user mode during
the SP install. Unless your applications are connecting as SA or
equivalent, there should be no conflict.
If the apps are connecting as SA, change the password before applying the SP
and change it back when you are done. Then fix that glaring security and
managability hole.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:FA6E93F9-78FC-497E-A4F0-E4D459F85CA9@.microsoft.com...
> Ran into a problem in scheduling applying the Service Pack to our SQL
> 2000 active/passive cluster when we add new nodes. 50 plus databases and
> an
> unknown number of apps.
> I'm wondering what people do to ensure that no apps/people are trying
> to
> access the databases when the service pack is applied.
> Our application staff says there is no way they can guarantee that an
> app or person will not try to access one of the databases while the
> service
> pack is being installed.
> My plan is to evict one of the existing nodes then add the two new
> nodes
> one at a time and set up the heartbeat. Then install SQL 2000; then
> apply
> SP3a. Yes I know SP4 is available; however, one of the apps will not run
> with SP4.
|||I thought in single-user mode, that any ID could be used and the 1st one
wins. SA or not. I also thought that the service pack brings the database
engine up and down several times while it is applying the service pack.
The other restriction (db_owner, sysadmin, bd_creator) isn't an option for
us either since many of the app IDs are db_owner in their database.
"Geoff N. Hiten" wrote:

> The service pack brings the database engine up in single-user mode during
> the SP install. Unless your applications are connecting as SA or
> equivalent, there should be no conflict.
>
> If the apps are connecting as SA, change the password before applying the SP
> and change it back when you are done. Then fix that glaring security and
> managability hole.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
> news:FA6E93F9-78FC-497E-A4F0-E4D459F85CA9@.microsoft.com...
>
|||There is single-user mode for a database, and then there is single-user mode
for the entire database service. The SP starts the entire service in
single-user mode and immediately claims the connection.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:98107803-0953-4B12-986E-FB82CDCBA45B@.microsoft.com...[vbcol=seagreen]
>I thought in single-user mode, that any ID could be used and the 1st one
> wins. SA or not. I also thought that the service pack brings the
> database
> engine up and down several times while it is applying the service pack.
> The other restriction (db_owner, sysadmin, bd_creator) isn't an option for
> us either since many of the app IDs are db_owner in their database.
> "Geoff N. Hiten" wrote:
|||Thanks. So do I even need to get all the apps down before I start applying
a service pack? I would think so, so they close out of what they are doing
in an orderly fashion. Just not worry about them trying to get in while the
service pack is running.
"Geoff N. Hiten" wrote:

> There is single-user mode for a database, and then there is single-user mode
> for the entire database service. The SP starts the entire service in
> single-user mode and immediately claims the connection.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
> news:98107803-0953-4B12-986E-FB82CDCBA45B@.microsoft.com...
>
|||You need a standard practice for maintenance, regardless of whether you are
applying a hotfix or an internal update. This includes procedures for
stopping and starting the entire system.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Pat Hall" <PatHall@.discussions.microsoft.com> wrote in message
news:D497CBD2-637D-490C-9BAD-6AA49F145000@.microsoft.com...[vbcol=seagreen]
> Thanks. So do I even need to get all the apps down before I start
> applying
> a service pack? I would think so, so they close out of what they are
> doing
> in an orderly fashion. Just not worry about them trying to get in while
> the
> service pack is running.
> "Geoff N. Hiten" wrote:

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft an
d
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:

> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQ
L
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
[vbcol=seagreen]
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft
and
> they have absolutely no idea what the problem is and haven't really offere
d
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I
am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 S
P1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:
>

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.
We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft and
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:

> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.
|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
[vbcol=seagreen]
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft and
> they have absolutely no idea what the problem is and haven't really offered
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 SP1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:

Applying 2003 SP1 to a SQL Cluster running SP3

Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
issues that we want to wait.We did just this on Saturday and it has been a nightmare. Everything was
running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
wreaked havoc!
Our overall performance has dropped dramatically. What used to take 2
seconds to run now takes upwards of 6. We've been working with Microsoft and
they have absolutely no idea what the problem is and haven't really offered
much in terms of troubleshooting ideas either.
One suggestion we've heard is to update statictics on all tables (which I am
doing right now) but it doesn't seem to make a difference.
Of course Microsoft says that all of this should work fine and that W2K3 SP1
and SQL 2000 SP3 should co-exist fine in a cluster...
Good luck!
"JGTKD" wrote:
> Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> issues that we want to wait.|||Any updates on this thread? I am looking to do the same thing (sp1 on 2003
Enterprise Server running mssql2000 sp3) in the near future.
Thanks.
"Drinian" wrote:
> We did just this on Saturday and it has been a nightmare. Everything was
> running fine with Windows 2003 and SQL2000 SP3 but installing W2K3 SP1 has
> wreaked havoc!
> Our overall performance has dropped dramatically. What used to take 2
> seconds to run now takes upwards of 6. We've been working with Microsoft and
> they have absolutely no idea what the problem is and haven't really offered
> much in terms of troubleshooting ideas either.
> One suggestion we've heard is to update statictics on all tables (which I am
> doing right now) but it doesn't seem to make a difference.
> Of course Microsoft says that all of this should work fine and that W2K3 SP1
> and SQL 2000 SP3 should co-exist fine in a cluster...
> Good luck!
> "JGTKD" wrote:
> > Are there any known problems applying 2003 SP1 to a 2003 Active/Passive SQL
> > Cluster running SQL SP3, not 3a? We have seen enough posts about SQL SP4
> > issues that we want to wait.

Apply sql2k post sp4 fix 2162 on cluster

I applied sql2k post sp4 fix 2040 and 2162 on active node of the cluster without error, the version number is 8.00.2162. When failover the cluster and double check version number again, it's 8.00.2040. That means fix 2162 didn't push to passive node. So I tried apply fix 2162 on current active node but stopped with KB904660(ENU) setup error: An error in updating your system has occurred. Can't find any log file, and OS is win2k3 enterprise edition with sp1. Anyone got similar issue?

You should get a higher build of Hotfix package. The issue you are reporting is a known bug and has been fixed in later builds.

thanks

Raja

Information on this page is posted as is and no warranty as to the accuracy of any of the presented information

Application Databases storing location

We have SQL Database in Cluster volume F:
Cluster volume is mounted in the primary server A1.
We have production and test databases of the applications
stored in the Cluster Storage F:.
Is it possible to store all the test databases of the
applications in the Clocal harddisk) of the primary
server?
If there is a solution pls advice.
You can copy data to anywhere you would like. To use the data with
clustering, you have to have the ability for that data to be reached by any
clustered node, even after a failure. If you keep anything local, and that
machine
fails, other nodes will not be able to access it.
Cheers,
Rod
"Anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:743201c430db$f3018270$a401280a@.phx.gbl...
> We have SQL Database in Cluster volume F:
> Cluster volume is mounted in the primary server A1.
> We have production and test databases of the applications
> stored in the Cluster Storage F:.
> Is it possible to store all the test databases of the
> applications in the Clocal harddisk) of the primary
> server?
> If there is a solution pls advice.
>
|||A clustered SQL server must store data on a drive that is in the same
resource group. The SQL server must be dependant on the physical disk(s)
that clustered data is stored on.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:743201c430db$f3018270$a401280a@.phx.gbl...
> We have SQL Database in Cluster volume F:
> Cluster volume is mounted in the primary server A1.
> We have production and test databases of the applications
> stored in the Cluster Storage F:.
> Is it possible to store all the test databases of the
> applications in the Clocal harddisk) of the primary
> server?
> If there is a solution pls advice.
>
|||Can the Clocal harddisk) of the primary server be
included as part of the same resource group as the
clustered SQL server?

>--Original Message--
>A clustered SQL server must store data on a drive that is
in the same
>resource group. The SQL server must be dependant on the
physical disk(s)
>that clustered data is stored on.
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Anonymous" <anonymous@.discussions.microsoft.com> wrote
in message[vbcol=seagreen]
>news:743201c430db$f3018270$a401280a@.phx.gbl...
applications
>
>.
>
|||Fine. We do not want the test data in the cluster mode and
need not be available in case of failure.
Is it possible to have SQL server in Cluster and
applications data in the local?

>--Original Message--
>You can copy data to anywhere you would like. To use the
data with
>clustering, you have to have the ability for that data to
be reached by any
>clustered node, even after a failure. If you keep
anything local, and that
>machine
>fails, other nodes will not be able to access it.
>Cheers,
>Rod
>"Anonymous" <anonymous@.discussions.microsoft.com> wrote
in message[vbcol=seagreen]
>news:743201c430db$f3018270$a401280a@.phx.gbl...
applications
>
>.
>
|||No. C: is not a shared cluster resource.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:886301c4326d$56ac1a00$a301280a@.phx.gbl...[vbcol=seagreen]
> Can the Clocal harddisk) of the primary server be
> included as part of the same resource group as the
> clustered SQL server?
> in the same
> physical disk(s)
> in message
> applications
|||No, sorry you can't do that. All SQL data needs to be on the shared storage.
Cheers,
Rod
"Anonymous" <anonymous@.discussions.microsoft.com> wrote in message
news:886b01c4326e$406dde30$a301280a@.phx.gbl...[vbcol=seagreen]
> Fine. We do not want the test data in the cluster mode and
> need not be available in case of failure.
> Is it possible to have SQL server in Cluster and
> applications data in the local?
> data with
> be reached by any
> anything local, and that
> in message
> applications

Anyone using Polyserve for clustering ?

Let me know what you think of the product.Is it worth considering than say
the MSFT cluster ?
Thanks

Quote:

Originally Posted by Hassan

Let me know what you think of the product.Is it worth considering than say
the MSFT cluster ?
Thanks

We use it, replaced our Windows 2000 filers with a cluster, evaluating SQL Server cluster. Enables real-time relocation of resources|||First, it is MSCS clustering. MSFT is Microsoft Full-Text...Engine or
Search.
I wouldn't say either is better. They are different, satisfying two
different solution requirements.
My experience is that Polyserve is a consolidation management solution.
Something like Neverfail would be closer to failover MSCS clustering.
Sincerely,
Anthony Thomas

"Hassan" <hassan@.hotmail.com> wrote in message
news:%23Gd%23SWTsHHA.3468@.TK2MSFTNGP05.phx.gbl...
> Let me know what you think of the product.Is it worth considering than say
> the MSFT cluster ?
> Thanks
>
|||No! MSFT is Microsoft Stock Ticker You SQL guys are so geeky ;)
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:%23ZREH2jxHHA.404@.TK2MSFTNGP03.phx.gbl...
> First, it is MSCS clustering. MSFT is Microsoft Full-Text...Engine or
> Search.
> I wouldn't say either is better. They are different, satisfying two
> different solution requirements.
> My experience is that Polyserve is a consolidation management solution.
> Something like Neverfail would be closer to failover MSCS clustering.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:%23Gd%23SWTsHHA.3468@.TK2MSFTNGP05.phx.gbl...
>

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the s
ecurity
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the
security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:[vbcol=seagreen]
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the security
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
> >I attempted installing yesterday on a cluster, and the installation
> > went fine, but when I kicked off the backup via Litespeed, I received
> > the following error...
> >
> > [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> > environment for VDI. Ensure that the SQL Server Service account has
> > administrator access to this server. Note: Administrator privilege
> > can be restriced by registry/file and policy changes that can prevent
> > this operation from succeeding.
> >
> > The SQL Service acct does have admin rights on the server. I installed
> > it as someone in the admin group. And I kicked off the backup as an
> > admin. I'm waiting for a call back from Imceda software on this, but
> > wanted to see if anyone out there had any ideas.
> >

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the security
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.
Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegro ups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>
|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:[vbcol=seagreen]
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegro ups.com...