cluster SSAS and SQL

Hi,
We have a default clusterd SQL server 2005 with sp2 installed in one cluster
group and then I have installed a default SSAS clustered instance in another
cluster group and it works fine (can failover and user can connect). However,
when I applying the sp2 to SSAS instance (with SSAS checked only) and it
failed; it not noly just failed but also take down my default clustered sql
server! We have to call MS to get our server up. It seems that, somehow,
registry for default sql server got messed up by SSAS sp2. My question are:
1.Is it possible or supported to install a default SQL server and a default
Analysis server on a cluster (each one in its own cluster group) with sp2;
2.why applying sp2 on a default AD instance in one cluster group affect a
default sql instance in another cluster group.
thanks much in advance.
Zack.
The answer is that SQL services share some common components. Plus, the
installer has some generic setup logic. Finally, are you using the same
service account for both services? If so, then permissions can get hosed
during a broken update.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"dp" <dp@.discussions.microsoft.com> wrote in message
news:90BAC728-916F-4497-B293-55920962EDE8@.microsoft.com...
> Hi,
> We have a default clusterd SQL server 2005 with sp2 installed in one
> cluster
> group and then I have installed a default SSAS clustered instance in
> another
> cluster group and it works fine (can failover and user can connect).
> However,
> when I applying the sp2 to SSAS instance (with SSAS checked only) and it
> failed; it not noly just failed but also take down my default clustered
> sql
> server! We have to call MS to get our server up. It seems that, somehow,
> registry for default sql server got messed up by SSAS sp2. My question
> are:
> 1. Is it possible or supported to install a default SQL server and a
> default
> Analysis server on a cluster (each one in its own cluster group) with sp2;
> 2. why applying sp2 on a default AD instance in one cluster group affect a
> default sql instance in another cluster group.
> thanks much in advance.
> Zack.
>
|||Zack, were you ever able to upgrade your SSAS in the cluster?
We are having the same or similar issues. We upgraded our cluster from SP1
to SP2. The SQL Server components upgraded to SP2, but the SSAS failed and
is still at SP1. After the upgrade one of our clustered instances did not
come back online. Error logs read something like, "...Cluster IP/Network
resource already in use..."
Well, I called MS because our production SQL 2005 cluster was hosed. The
issue, reg key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
Server\MSSQL.1\Cluster\ClusterName" had the incorrect instance name for the
MSSQL.1 instance (in our case). We had to run some cluster commands to
remove the MSCS checkpoint, changed the key value to the correct instance
name, then reapply MSCS checkpoint.
This got our SQL Server instance back online. But we still can't update
SSAS to SP2. Maybe the two issues are not related, but I have a gut feeling
they are. The incorrect 'ClusterName' value happened to be the instance name
for our SSAS.
I still have the MS support ticket open trying to determine if the cluster
registry keys are in the correct state on both nodes.
Anyone else having issues with failover cluster anaylsis server upgrade to
SP2?
"dp" wrote:

> Hi,
> We have a default clusterd SQL server 2005 with sp2 installed in one cluster
> group and then I have installed a default SSAS clustered instance in another
> cluster group and it works fine (can failover and user can connect). However,
> when I applying the sp2 to SSAS instance (with SSAS checked only) and it
> failed; it not noly just failed but also take down my default clustered sql
> server! We have to call MS to get our server up. It seems that, somehow,
> registry for default sql server got messed up by SSAS sp2. My question are:
> 1.Is it possible or supported to install a default SQL server and a default
> Analysis server on a cluster (each one in its own cluster group) with sp2;
> 2.why applying sp2 on a default AD instance in one cluster group affect a
> default sql instance in another cluster group.
> thanks much in advance.
> Zack.
>

Cluster SQL 2000

My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
SQL 2000, each instance is on different node, we noticed that every
instances have configured with TCP port 1433.
Is it possible on Cluster?
Hello.K
Since SQL uses 1433 as the default port and each instance sounds like its
running on its own node, I would say yes?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"kersob" <lkm> wrote in message
news:ODcWDPdWEHA.3016@.tk2msftngp13.phx.gbl...
> My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
> SQL 2000, each instance is on different node, we noticed that every
> instances have configured with TCP port 1433.
> Is it possible on Cluster?
>
> Hello.K
>
|||Host nodes don't have anything to do with port numbers. Notice that each
SQL resource group (virtual server) has its own IP address and network name.
Therefore, you can have each instance on 1433 if you desire. HOWEVER, there
are some gotchas. If you are hoping to connect to VirtualServername rather
than VirtualServerName\InstanceName, it won't work with anything higher than
MDAC 2.6. Even if you put a named instance on 1433, the client library
'knows' it isn't the default instance. MDAC will report an error that you
are connecting to the wrong instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"kersob" <lkm> wrote in message
news:ODcWDPdWEHA.3016@.tk2msftngp13.phx.gbl...
> My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
> SQL 2000, each instance is on different node, we noticed that every
> instances have configured with TCP port 1433.
> Is it possible on Cluster?
>
> Hello.K
>

Cluster setup question

Im viewing the Cluster setup instructions at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
_clustering_51rm.asp
But it doesnt say where to install SQL. It seems to me that if I wanted to
have an Active/ Passive Cluster I would need to intsall it on both boxes? Is
this correct? Are there better links I should be using?
--
SQL2K SP3
TIA, ChrisRYou begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||Well, that is close, but not quite accurate.
Even on a stand-alone installation, when you run the setup dialogue in
interactive mode, all that really happens is that a custom .iss file is
generated from your responses to the questions. Once all of the information
is gathered, setup then executes the setupsql with the newly created
setup.iss file as a parameter.
A cluster install is similar, except the setup.iss is deployed to both
nodes. During the installation, the cluster fails the disk over to each
node so that the individual setup.iss files can be ran against two
independently executed setupsql commands. This creates registry keys.
However, since the first install already created the directory structure,
deployed the binaries, installed the .sql scripts to master, model, and
msdb, this part of the process does not run again a second time. Just the
registry keys, performance counters, and client side tools. And, of course,
the MDAC, which is client side and IS NOT cluster aware.
Also, there is such a thing as the "Primary Node." This is nothing more
than the node from which you started the installation. It does not matter
which node you begin the installation on, as long as it is the node that
currently owns the disk resource you plan on installing SQL Server to.
However, it is important that you keep in mind which node this was.
This node will be the only one that maintains a record of the setup logs.
There is also special CLSIDs that only this node will contain that will not
propagate to the other. The nodes are close to the same configuration, BUT
NOT EXACT. This will be important in the future when you try to add
additional disk resources or swap out old disks for new, if you ever need to
modify or add an additional IP resource, or change the domain the cluster
belongs to. Keeping in mind which node was PRIMARY will only be to your
benefit.
Sincerely,
Anthony Thomas
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
You begin the installation from the node that currently owns the disk
resource you want SQL data files installed to. You can add additional disk
resources after the installation. The SQL installer adds code automagically
to the nodes you specify, provided they actually exist and are running at
install time. You can add or remove nodes from the SQL installation later
if you need to. Once SQL is installed, there is no difference between
installed nodes except for which one is actually running SQL at a given
moment.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"ChrisR" <bla@.noemail.com> wrote in message
news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> Im viewing the Cluster setup instructions at:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> _clustering_51rm.asp
> But it doesnt say where to install SQL. It seems to me that if I wanted to
> have an Active/ Passive Cluster I would need to intsall it on both boxes?
Is
> this correct? Are there better links I should be using?
> --
> SQL2K SP3
> TIA, ChrisR
>|||I have had to change accounts and add/remove disk resources. As long as I
use the current owner node, everything works fine.
Yes, there are some subtle differences such as log files between nodes but
that is only relevant during installation failure troubleshooting. Once
everythign is running, there is no practical difference between nodes,
unlike SQL 7.0 clustering.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:OfrkU8e$EHA.1084@.tk2msftngp13.phx.gbl...
> Well, that is close, but not quite accurate.
> Even on a stand-alone installation, when you run the setup dialogue in
> interactive mode, all that really happens is that a custom .iss file is
> generated from your responses to the questions. Once all of the
information
> is gathered, setup then executes the setupsql with the newly created
> setup.iss file as a parameter.
> A cluster install is similar, except the setup.iss is deployed to both
> nodes. During the installation, the cluster fails the disk over to each
> node so that the individual setup.iss files can be ran against two
> independently executed setupsql commands. This creates registry keys.
> However, since the first install already created the directory structure,
> deployed the binaries, installed the .sql scripts to master, model, and
> msdb, this part of the process does not run again a second time. Just the
> registry keys, performance counters, and client side tools. And, of
course,
> the MDAC, which is client side and IS NOT cluster aware.
> Also, there is such a thing as the "Primary Node." This is nothing more
> than the node from which you started the installation. It does not matter
> which node you begin the installation on, as long as it is the node that
> currently owns the disk resource you plan on installing SQL Server to.
> However, it is important that you keep in mind which node this was.
> This node will be the only one that maintains a record of the setup logs.
> There is also special CLSIDs that only this node will contain that will
not
> propagate to the other. The nodes are close to the same configuration,
BUT
> NOT EXACT. This will be important in the future when you try to add
> additional disk resources or swap out old disks for new, if you ever need
to
> modify or add an additional IP resource, or change the domain the cluster
> belongs to. Keeping in mind which node was PRIMARY will only be to your
> benefit.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%23e8GA4Z$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> You begin the installation from the node that currently owns the disk
> resource you want SQL data files installed to. You can add additional
disk
> resources after the installation. The SQL installer adds code
automagically
> to the nodes you specify, provided they actually exist and are running at
> install time. You can add or remove nodes from the SQL installation later
> if you need to. Once SQL is installed, there is no difference between
> installed nodes except for which one is actually running SQL at a given
> moment.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "ChrisR" <bla@.noemail.com> wrote in message
> news:ugjtmqZ$EHA.2136@.TK2MSFTNGP10.phx.gbl...
> > Im viewing the Cluster setup instructions at:
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
> > _clustering_51rm.asp
> >
> > But it doesnt say where to install SQL. It seems to me that if I wanted
to
> > have an Active/ Passive Cluster I would need to intsall it on both
boxes?
> Is
> > this correct? Are there better links I should be using?
> >
> > --
> > SQL2K SP3
> >
> > TIA, ChrisR
> >
> >
>sqlsql

Cluster Setting Failure Stay On Same Node

What is the Cluster setting if the present node has 3 failures (default) to
stay on the same server node?
What is the Cluster setting if the present node has 3 failures (default) to
move to another server node?
Thanks,
Joe K.
If I understand you correctly, this type of behavior is specified in the
Advanced tab of the resource Properties dialog form. There, you can specify
whether the cluster service tries to restart a resource or simply lets the
resource to fail.
If you want the cluster service to restart the resource, then you must
specify whether the resource failure should affect the group that contains
the resource. If you want to failover the group when the resource fails,
check 'Affect the group', and specify the Threshold and Period values. These
values determine how many times the cluster service will restart the resource
before failover and the amount of time in which the threshold number of
restart attempts should take place.
Linchi
"Joe K." wrote:

> What is the Cluster setting if the present node has 3 failures (default) to
> stay on the same server node?
> What is the Cluster setting if the present node has 3 failures (default) to
> move to another server node?
> Thanks,
> Joe K.

Cluster Server installation other than default directory

Is anyone aware of any issues that can arise from installing MS SQL Server
2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
I have always installed to the root directory be it stand-alone or clustered
installs without any issues but I need to know whether there might be
issues especially regarding virtual sql servers installs.
Thanks
I have not seen any differences with clustering, you should be fine with any
path, as long as all possible owners have the same paths.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Gboyega Adepegba" <muyid@.hotmail.com> wrote in message
news:u5IVSaOZEHA.3752@.TK2MSFTNGP12.phx.gbl...
> Is anyone aware of any issues that can arise from installing MS SQL Server
> 2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
> the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
> I have always installed to the root directory be it stand-alone or
clustered
> installs without any issues but I need to know whether there might be
> issues especially regarding virtual sql servers installs.
> Thanks
>
|||No issues. I have installed clustered instances of SQL Server 2000 on non-default locations without any problems.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
sqlsql

Cluster Parameters in BIDS Wizard?

I am wondering how to change the default parameters for the Clustering algorithm in BIDS. I set up an initial MiningStructure with the wizard but i want to tweak the

Clustering_Method and Cluster_Count parameters prior to training the dataset but I do not see where to do this..

thanks!

aem

Open the mining structure in BIDS, navigate to the Mining Models tab (2nd tab), right click on the mining model and select "Set Algorithm Parameters" in the context menu. You can also select "Properties" for the mining model and modify the algorithm parameters from the property grid.

Please let me know if you have any additional questions

Client-side Printing and page hesitation

When printing reports from my normal computer to my default printer, all but
one report print without any hesitation between pages. My boss prints
reports and gets a lot of hesitation between pages for most of the reports.
If I print to a differnt printer I too get a lot of hesitation betwen pages.
Does SRS print pages as graphics or as text? Are there any settings on the
server that can alter printing performance? Anyone else having issues with
print hesitation and found a solution to the problem?When u want 2 controll the print properties u should set them at the Report
Properties->layout.
All properties in this tab are 4 the print setting.
"Rob 'Spike' Stevens" wrote:
> When printing reports from my normal computer to my default printer, all but
> one report print without any hesitation between pages. My boss prints
> reports and gets a lot of hesitation between pages for most of the reports.
> If I print to a differnt printer I too get a lot of hesitation betwen pages.
> Does SRS print pages as graphics or as text? Are there any settings on the
> server that can alter printing performance? Anyone else having issues with
> print hesitation and found a solution to the problem?

Client Net Library Changes

I have been asked to consider changing the Net Library TCP/IP port for SQL
Server from the default 1433 to a different one.
The problem is the 1800 user stations.
Is there a scriptable way to change the port on the clients without having
to visit each one to do it manually?When you create an alias o the client (start->run->cliconfg.exe->alias tab)
- a registry key value with the alias properties will be created under:
HKLM\SW\Microsoft\MSSQLServer\Client\Con
nectTo . So you can write a script
to add this registry key value. If this a named instance then the clients
should be able to "dynamically" determine the port number and no registry
key modification should be necessary.
See the MSDN article : How To Use the Windows Script Host to Read, Write,
and Delete Registry Keys
for more details on how to write to the registry through script.
reference:
Books online topics:
- Client Network Utility
- Managing Clients
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Client Net Library Changes

I have been asked to consider changing the Net Library TCP/IP port for SQL
Server from the default 1433 to a different one.
The problem is the 1800 user stations.
Is there a scriptable way to change the port on the clients without having
to visit each one to do it manually?
When you create an alias o the client (start->run->cliconfg.exe->alias tab)
- a registry key value with the alias properties will be created under:
HKLM\SW\Microsoft\MSSQLServer\Client\ConnectTo . So you can write a script
to add this registry key value. If this a named instance then the clients
should be able to "dynamically" determine the port number and no registry
key modification should be necessary.
See the MSDN article : How To Use the Windows Script Host to Read, Write,
and Delete Registry Keys
for more details on how to write to the registry through script.
reference:
Books online topics:
- Client Network Utility
- Managing Clients
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Client Net Library Changes

I have been asked to consider changing the Net Library TCP/IP port for SQL
Server from the default 1433 to a different one.
The problem is the 1800 user stations.
Is there a scriptable way to change the port on the clients without having
to visit each one to do it manually?When you create an alias o the client (start->run->cliconfg.exe->alias tab)
- a registry key value with the alias properties will be created under:
HKLM\SW\Microsoft\MSSQLServer\Client\ConnectTo . So you can write a script
to add this registry key value. If this a named instance then the clients
should be able to "dynamically" determine the port number and no registry
key modification should be necessary.
See the MSDN article : How To Use the Windows Script Host to Read, Write,
and Delete Registry Keys
for more details on how to write to the registry through script.
reference:
Books online topics:
- Client Network Utility
- Managing Clients
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx