Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts

Tuesday, March 27, 2012

Do I need to install SQL Server to second node in cluster prior to adding the node?

I read these instructions:

http://msdn2.microsoft.com/en-us/library/ms191545(SQL.90).aspx

But I'm not sure if I have to install SQL Server first on node 2, then add it to the cluster. Or does adding it to the cluster also install the software?

Thanks

From your question, I assume that you have an functioning single node cluster.

Add Node2 to the Windows MSCS cluster, and then install SQL Server on Node2. SQL Server will locate the cluster and ask if you are adding this Node to the SQL Server Virtual Server.

Thursday, March 22, 2012

do I need a domain in order to run a cluster?

Hi, I am a complete newbie with windows clustering -
still reading the white papers etc. From what I have read
it seems that I need a Windows Domain in order to run
clustering. Is this true? Is there any way I can cluster
SQL server without having to setup a domain?
thanks
christos
Yes. You must have a domain to run a cluster. No, you can't get around
having a domain.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Christos Kritikos" <anonymous@.discussions.microsoft.com> wrote in message
news:030001c49b56$400d9060$a301280a@.phx.gbl...
> Hi, I am a complete newbie with windows clustering -
> still reading the white papers etc. From what I have read
> it seems that I need a Windows Domain in order to run
> clustering. Is this true? Is there any way I can cluster
> SQL server without having to setup a domain?
> thanks
> christos
>
|||Hi Geoff,
I too have the same doubt. What are some Technical
reasons forcing cluster to run in a domain?
Thanks
Chip.
>--Original Message--
>Yes. You must have a domain to run a cluster. No, you
can't get around
>having a domain.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Christos Kritikos"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:030001c49b56$400d9060$a301280a@.phx.gbl...
read[vbcol=seagreen]
cluster
>
>.
>
|||You have to have a common security context for the cluster service to manage
resources on multiple machines. Parallel usernames and paswords will not
work. You have to have a domain (NT4 or AD) to provide cluster-wide access
to resources.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Chip" <anonymous@.discussions.microsoft.com> wrote in message
news:150e01c49c9d$f0cd9560$a301280a@.phx.gbl...[vbcol=seagreen]
> Hi Geoff,
> I too have the same doubt. What are some Technical
> reasons forcing cluster to run in a domain?
> Thanks
> Chip.
> can't get around
> <anonymous@.discussions.microsoft.com> wrote in message
> read
> cluster
|||There is some good information in
281662 Windows 2000 and Windows Server 2003 Cluster Nodes As Domain Controllers
http://support.microsoft.com/?id=281662
Here is a section from the same.
To have Windows Clustering function properly (where the Cluster service starts on each node) the node that forms the cluster must be able to validate the Cluster service domain account, which is the account that you
configure during the Windows Clustering installation. To accomplish this, each node must be able to establish a secure channel with a domain controller to validate this account. If the node cannot validate the
account, the Cluster service does not start. This is also true for other clustered programs that must have account validation for services to start, such as Microsoft SQL Server and Microsoft Exchange.
If you have a cluster deployment in which there is no link with either a Windows NT 4.0 domain, a Windows 2000 domain, or a Windows Server 2003 domain, you must configure the cluster nodes as domain
controllers so that the Cluster service account can always be validated to allow for proper cluster functionality.
If the connectivity between cluster nodes and domain controllers is such that the link is either slow or unreliable, consider having a domain controller co-located with the cluster, or configuring the cluster nodes as
domain controllers.
Consider the following important points when you are deploying Windows Clustering nodes as domain controllers:
--> See the above KB (http://support.microsoft.com/?id=281662)
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
|||Thanks Geoff & Uttam.
Chip
>--Original Message--
>There is some good information in
>281662 Windows 2000 and Windows Server 2003 Cluster Nodes
As Domain Controllers
>http://support.microsoft.com/?id=281662
>Here is a section from the same.
>To have Windows Clustering function properly (where the
Cluster service starts on each node) the node that forms
the cluster must be able to validate the Cluster service
domain account, which is the account that you
>configure during the Windows Clustering installation. To
accomplish this, each node must be able to establish a
secure channel with a domain controller to validate this
account. If the node cannot validate the
>account, the Cluster service does not start. This is also
true for other clustered programs that must have account
validation for services to start, such as Microsoft SQL
Server and Microsoft Exchange.
>If you have a cluster deployment in which there is no
link with either a Windows NT 4.0 domain, a Windows 2000
domain, or a Windows Server 2003 domain, you must
configure the cluster nodes as domain
>controllers so that the Cluster service account can
always be validated to allow for proper cluster
functionality.
>If the connectivity between cluster nodes and domain
controllers is such that the link is either slow or
unreliable, consider having a domain controller co-located
with the cluster, or configuring the cluster nodes as
>domain controllers.
>Consider the following important points when you are
deploying Windows Clustering nodes as domain controllers:
> --> See the above KB
(http://support.microsoft.com/?id=281662)
>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
>
>.
>

Wednesday, March 21, 2012

DMX to read cluster characteristics

Hi,

Can you send me or point me to a DMX code to read cluster characteristics programatically ?

Thanks,

The information displayed in the Cluster Characteristics viewer is available through a stored procedure call.

CALL System.Microsoft.AnalysisServices.System.DataMining.Clustering.GetClusterCharacteristics('Table1_CL','001',0.0005)

The first parameter is the model name, the second is the NODE_UNIQUE_NAME for the cluster whose characteristics are to be rendered and the last parameter is a threshold.

You can get the list of all clusters and their associated NODE_UNIQUE_NAME with a query like:

SELECT NODE_UNIQUE_NAME, NODE_CAPTION, NODE_DESCRIPTION, NODE_TYPE FROM [Table1_CL].CONTENT WHERE NODE_TYPE=5

(NODE_TYPE=5 identifies a Cluster node)

Hope this helps

|||

Hi Bogdan,

This worked greart. Thanks.

Can you also let me know the online material or book where I can get some more information of this kind about DMX to access information from SSAS DataMining model ? We are looking forward to write more of such codes to get information from the mining model programatically.

Thanks,

Vikas

|||

There isn't a lot of documentation on the stored procedures that retrieve summarized/derived information from the algorithms. All of the information is derived from the content (i.e. SELECT * FROM <model>.CONTENT). You can use SQL Profiler to inspect the queries that are sent from the viewers to the server to access the syntax and how the sprocs are called. Also, you can look at the sample thin client viewer code that ships with the product to see the characteristic and discrimination calls against clustering and naive bayes models.

To get a better idea of how the content looks per algorithm, you can download a sample plug-in viewer we wrote from http://www.sqlserverdatamining.com/DMCommunity/Downloads/Links_LinkRedirector.aspx?id=1349. This viewer provides a nicer interface for navigating generic content, decoding node types and value types and such.

|||

Here's one way of getting the characteristics that distinguish a cluster. Feedback welcome:

http://www.codeplex.com/ASStoredProcedures/Wiki/View.aspx?title=ClusterNaming&referringTitle=Home

DMX to read cluster characteristics

Hi,

Can you send me or point me to a DMX code to read cluster characteristics programatically ?

Thanks,

The information displayed in the Cluster Characteristics viewer is available through a stored procedure call.

CALL System.Microsoft.AnalysisServices.System.DataMining.Clustering.GetClusterCharacteristics('Table1_CL','001',0.0005)

The first parameter is the model name, the second is the NODE_UNIQUE_NAME for the cluster whose characteristics are to be rendered and the last parameter is a threshold.

You can get the list of all clusters and their associated NODE_UNIQUE_NAME with a query like:

SELECT NODE_UNIQUE_NAME, NODE_CAPTION, NODE_DESCRIPTION, NODE_TYPE FROM [Table1_CL].CONTENT WHERE NODE_TYPE=5

(NODE_TYPE=5 identifies a Cluster node)

Hope this helps

|||

Hi Bogdan,

This worked greart. Thanks.

Can you also let me know the online material or book where I can get some more information of this kind about DMX to access information from SSAS DataMining model ? We are looking forward to write more of such codes to get information from the mining model programatically.

Thanks,

Vikas

|||

There isn't a lot of documentation on the stored procedures that retrieve summarized/derived information from the algorithms. All of the information is derived from the content (i.e. SELECT * FROM <model>.CONTENT). You can use SQL Profiler to inspect the queries that are sent from the viewers to the server to access the syntax and how the sprocs are called. Also, you can look at the sample thin client viewer code that ships with the product to see the characteristic and discrimination calls against clustering and naive bayes models.

To get a better idea of how the content looks per algorithm, you can download a sample plug-in viewer we wrote from http://www.sqlserverdatamining.com/DMCommunity/Downloads/Links_LinkRedirector.aspx?id=1349. This viewer provides a nicer interface for navigating generic content, decoding node types and value types and such.

|||

Here's one way of getting the characteristics that distinguish a cluster. Feedback welcome:

http://www.codeplex.com/ASStoredProcedures/Wiki/View.aspx?title=ClusterNaming&referringTitle=Home

Tuesday, February 14, 2012

Distributed Transaction Coordinator/Cluster

Hi there. I'm new to this clustering mularky and I've a couple of questions
regarding a linked-server query I have.
1. Server A is a regular server. Server B is a clustered server with shared
storage.
From A, I want to call a stored proc that sits on B.
Q: I need to add B(cluster) as a Linked server on A - Do I need to add A as
a linked server on B also?
2. Depending on the answer to my first question, I might need to get MSDTC
running on the clustered server - is there some special configuration I
should undergo? I've come across some msdn articles regarding use of
"Comclust.exe" but I don't know if I need to use it.....
Any help would be appreciated - I'm a bit worried about this stuff!
I can answer #2 - Follow 817064, then 301600
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"len" <len@.discussions.microsoft.com> wrote in message
news:D1696F91-B3EF-485F-A362-785E910D02D7@.microsoft.com...
> Hi there. I'm new to this clustering mularky and I've a couple of
> questions
> regarding a linked-server query I have.
> 1. Server A is a regular server. Server B is a clustered server with
> shared
> storage.
> From A, I want to call a stored proc that sits on B.
> Q: I need to add B(cluster) as a Linked server on A - Do I need to add A
> as
> a linked server on B also?
>
> 2. Depending on the answer to my first question, I might need to get MSDTC
> running on the clustered server - is there some special configuration I
> should undergo? I've come across some msdn articles regarding use of
> "Comclust.exe" but I don't know if I need to use it.....
> Any help would be appreciated - I'm a bit worried about this stuff!
|||Dhanks for that - it's just what I was looking for! I have one question
regarding 301600 though:
Part of the instructions state that after creating a Cluster group for
MSDTC, I need to add an IP Address resource to that group.
What I don't know is: where should this IP address come from? I've already
tried the IP address of both of my cluster nodes AND the virtual IPAddress of
my shared storage/SQL server but errors are thrown up about these being in
use already. do I need to create an entirely ne IP address?
thanks again!
"Rodney R. Fournier [MVP]" wrote:

> I can answer #2 - Follow 817064, then 301600
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "len" <len@.discussions.microsoft.com> wrote in message
> news:D1696F91-B3EF-485F-A362-785E910D02D7@.microsoft.com...
>
>
|||You are most welcome.
The IP has to be a new IP address, it needs to be in the same subnet as the
SQL & Cluster IP.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"len" <len@.discussions.microsoft.com> wrote in message
news:08F90F15-972F-41D6-87E1-F34C1EBCFAB3@.microsoft.com...[vbcol=seagreen]
> Dhanks for that - it's just what I was looking for! I have one question
> regarding 301600 though:
> Part of the instructions state that after creating a Cluster group for
> MSDTC, I need to add an IP Address resource to that group.
> What I don't know is: where should this IP address come from? I've already
> tried the IP address of both of my cluster nodes AND the virtual IPAddress
> of
> my shared storage/SQL server but errors are thrown up about these being in
> use already. do I need to create an entirely ne IP address?
> thanks again!
>
> "Rodney R. Fournier [MVP]" wrote: