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 SQL 2005 SP1 to a local copy of Workstation Components

I have installed the Workstation components on my local PC, which also contains VS 2005 and SQL Express. I installed the WS components so that I could run the full blown version of SQL Management Studio from my PC, to remove SQL 2005 servers.

I tried to update the Workstation components to SP1, but the SP1 package stops at the Setup Support Files, step and terminates claiming the package does not support SQL Express. I realize the package is not intended for Express, I simply need to update Management studio.

I tried running the Post SP1 Tools hotfix and it complains that it will not update SP0 of the tools.

I have successfully updated Express to SP1 and applied the Post hotfixes as well. Is there any way to patch just Management studio on a system with Express installed?

Thank,
Jim

Jim, were you able to get this installed? Your scenario sounds valid for sure and I'd like to hear if you got this resolved.

Thanks,

Sam

|||Sam,

No I never got this installed.... I ended up removing the Workstation components and installing Management Studio Express. I wanted to keep the build of mgt. studio inline with the build of SQL Server 2005. I'm hurting now as the management tools are missing from the express version.

I'm sorry about the delay in responding to this. I stopped watching the post when I didn't get any answers. I would really like to get this problem fixed....

Jim

Applying SQL 2005 SP1 to a local copy of Workstation Components

I have installed the Workstation components on my local PC, which also contains VS 2005 and SQL Express. I installed the WS components so that I could run the full blown version of SQL Management Studio from my PC, to remove SQL 2005 servers.

I tried to update the Workstation components to SP1, but the SP1 package stops at the Setup Support Files, step and terminates claiming the package does not support SQL Express. I realize the package is not intended for Express, I simply need to update Management studio.

I tried running the Post SP1 Tools hotfix and it complains that it will not update SP0 of the tools.

I have successfully updated Express to SP1 and applied the Post hotfixes as well. Is there any way to patch just Management studio on a system with Express installed?

Thank,
Jim

Jim, were you able to get this installed? Your scenario sounds valid for sure and I'd like to hear if you got this resolved.

Thanks,

Sam

|||Sam,

No I never got this installed.... I ended up removing the Workstation components and installing Management Studio Express. I wanted to keep the build of mgt. studio inline with the build of SQL Server 2005. I'm hurting now as the management tools are missing from the express version.

I'm sorry about the delay in responding to this. I stopped watching the post when I didn't get any answers. I would really like to get this problem fixed....

Jim

Applying SQL 2005 SP1 to a local copy of Workstation Components

I have installed the Workstation components on my local PC, which also contains VS 2005 and SQL Express. I installed the WS components so that I could run the full blown version of SQL Management Studio from my PC, to remove SQL 2005 servers.

I tried to update the Workstation components to SP1, but the SP1 package stops at the Setup Support Files, step and terminates claiming the package does not support SQL Express. I realize the package is not intended for Express, I simply need to update Management studio.

I tried running the Post SP1 Tools hotfix and it complains that it will not update SP0 of the tools.

I have successfully updated Express to SP1 and applied the Post hotfixes as well. Is there any way to patch just Management studio on a system with Express installed?

Thank,
Jim

Jim, were you able to get this installed? Your scenario sounds valid for sure and I'd like to hear if you got this resolved.

Thanks,

Sam

|||Sam,

No I never got this installed.... I ended up removing the Workstation components and installing Management Studio Express. I wanted to keep the build of mgt. studio inline with the build of SQL Server 2005. I'm hurting now as the management tools are missing from the express version.

I'm sorry about the delay in responding to this. I stopped watching the post when I didn't get any answers. I would really like to get this problem fixed....

Jim

Applying SP1 on Sql Server Express production environment

How do you apply Service Pack 1 to Sql Server Express 2005?Hi,

this can be directly read from the setup instructions:

http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/ReadmeSQLEXP2005.htm

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Applying CSS to SRS Reports

Hi , I hava a quick question about can we apply Css to actual repots in the
SRS ?
Since i figured out there is one property comes with SP1 i.e.,
rc:Stylesheet=Mystylename (without css extension) but this solution can only
resolve my half problem i.e., it applies only to parameter section and
toolbar section of the report but i wanted to apply for complete report
display while rendering it or displaying with the use of ReportViewer control.
Any Help is appreciated.
Thanks in advance.
APatelWe have the same want, we ended up using a near identity xsl to transorm the
unstyled report into 3 styles that we use as a subreport. The outer report
uses the style as a parameter, then we show/hide the subreports based on the
style...Yes it's very clunky, I'm looking for suggestions on a better way.
Here's my xsl file:
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="2.0"
xmlns:msrs="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:fn="http://www.w3.org/2005/02/xpath-functions"
exclude-result-prefixes="msrs xs fn">
<xsl:output encoding="iso-8859-1" method="xml" omit-xml-declaration ="yes"
indent="yes"/>
<xsl:template match="//msrs:FontFamily">
<msrs:FontFamily>Tahoma</msrs:FontFamily>
</xsl:template>
<xsl:template
match="//msrs:Textbox/msrs:Style[msrs:BackgroundColor='#fbee83']/msrs:BackgroundColor">
<msrs:BackgroundColor>#4e0000</msrs:BackgroundColor>
<msrs:Color>White</msrs:Color>
</xsl:template>
<xsl:template
match="//msrs:Textbox/msrs:Style[msrs:BackgroundColor='SandyBrown']/msrs:BackgroundColor">
<msrs:BackgroundColor>Maroon</msrs:BackgroundColor>
<msrs:Color>White</msrs:Color>
</xsl:template>
<xsl:template match="//msrs:Textbox/msrs:Style[contains(., 'Mod 2,
"White", "Wheat"')]/msrs:BackgroundColor">
<msrs:BackgroundColor>= iif(RowNumber(Nothing) Mod 2, "White",
"LightGrey")</msrs:BackgroundColor>
</xsl:template>
<xsl:template match="@.* | node()" priority="-2">
<xsl:copy>
<xsl:apply-templates select="@.* | node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
"APatel" <APatel@.discussions.microsoft.com> wrote in message
news:B6D65976-EF0D-4BD0-A8A0-798CD71678A5@.microsoft.com...
> Hi , I hava a quick question about can we apply Css to actual repots in
> the
> SRS ?
> Since i figured out there is one property comes with SP1 i.e.,
> rc:Stylesheet=Mystylename (without css extension) but this solution can
> only
> resolve my half problem i.e., it applies only to parameter section and
> toolbar section of the report but i wanted to apply for complete report
> display while rendering it or displaying with the use of ReportViewer
> control.
> Any Help is appreciated.
> Thanks in advance.
> APatel

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.