Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

sql 2005 cluster name or sql virtual name????? Expand / Collapse
Author
Message
Posted Thursday, July 3, 2008 1:42 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
Windows 2003, sql 2005 sp2 cluster

when you open up a sql server properties....

one of my systems shows virtual sql server name
second one shows the cluster name

when i'm connecting to those systems, i have no problems to connect to them
by specifying the sql virt name.

what is the right way for clusterd sql server...?
should it show the cluster name or sql virt name in the server properties?

BTW, the one that shows the clustername wqas not working properly.... like i couldn't open the error log files
fix was to create an alias in sql server configuration window
alias had the clustername as an allias and the virtual sql server name as a server, also named pipes type of connection has been used



Post #528368
Posted Saturday, July 5, 2008 10:55 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, July 28, 2014 7:59 PM
Points: 344, Visits: 285
you should connect using SQL Virtual server name not windows cluster name.
Post #528869
Posted Saturday, July 5, 2008 10:55 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, July 28, 2014 7:59 PM
Points: 344, Visits: 285
you should connect using SQL Virtual server name not windows cluster name.
Post #528870
Posted Sunday, July 6, 2008 7:15 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
i understand that...
I'm just trying to find an answer why even though i follow the same
installation configuration, one of my clustered sql server shows in properties name
the same name that we chose for vitrual sql name
and second clustered sql shows the clustername in properties name for sql server
but i still have no problems connecting to it by sql server virtual name.
like i said before, i had to create an alias for that second cluster
where alias name is a cluster name and server is a virtual sql name, using named pipes connection.
So my question is why when you going to properties for clustered sql server,
in the name line it shows me a cluster group name instead of virt sql name???



Post #529005
Posted Sunday, July 6, 2008 8:49 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 1:03 PM
Points: 4,388, Visits: 9,510
The only thing I can think of is that maybe you have SQL Server setup in the cluster group on that server instead of in the SQL group.

Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #529017
Posted Sunday, July 6, 2008 10:14 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 11:23 PM
Points: 744, Visits: 472
Hi,

I'm a bit confused, however it does sound like the 2nd instance was installed in the cluster group.
Do you have access to Cluster Admin (Start -> Run -> Cluadmin )? What do you see when you run this? How many groups do you see?

From the sounds of it, you should have about 4 groups
1. Cluster Group
2. Virtual SQL Server 1
3. Virtual SQL Server 2
4. MSDTC

The 'Cluster Group' usually only contains 'Cluster Name', 'Cluster IP Address' & and a cluster disk for the Quorum.

Post #529036
Posted Monday, July 7, 2008 6:55 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
Here is more details:

Windows 2003 standard, sql 2005 sp2,

QA environment:

1. Cluster group name - CL1
2. Consist of two active/passive nodes
ND1 and ND2
3. Virtual sql server name SQLQA01

Right click on sql server properties:

Server name - SQLQA01 - Looks good!

Now second installation,

PR environment:

1. Cluster group name – CL2
2. Consist of two active/passive nodes
ND3 and ND4
3. Virtual sql server name SQLPR01

Right click on sql server properties:

Server name - CL2 - ?????????

The vierd part is that I was able to connect to this virtual sql server by specifying the sql virt name.
Some of the sql fetures like error log or dbmail were not working.
So the way around was: create an alias in sql configuration manager.
Where alias name CL2, net protocol Named Pipes, server SQLPR01.
Working just great.
It just bothers me, WHY it has different properties name if the same installation procedure was followed during both setups.
Also please someone explain, what is the difference between instance name and virtual sql name?
Is the default instance name has the same name as a cluster group name?



Post #529233
Posted Monday, July 7, 2008 6:04 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 11:23 PM
Points: 744, Visits: 472
I can only think of 2 reasons why you have this problem.
1. SQL Server was installed into the cluster group 'CL2' on your PR server.
2. The 'SQL Network Name' was setup / configured incorrectly within the SQL Server cluster group

To confirm this, we will need a bit more information from Cluster Administrator.
What are the group names?
And more importantly, what resources are within each group?
e.g.
Group: CL1
Resources:
- Cluster Name
- Cluster IP
- Disk X

Also, could you please run the below query on both QA & PR and post the output? I am happy for you to change the server names as long you keep it consistent.
SELECT CAST( SERVERPROPERTY('InstanceName') AS NVARCHAR(128)) AS 'InstanceName'
SELECT CAST( SERVERPROPERTY('IsClustered') AS NVARCHAR(128)) AS 'IsClustered'
SELECT CAST( SERVERPROPERTY('MachineName') AS NVARCHAR(128)) AS 'MachineName'
SELECT CAST( SERVERPROPERTY('ServerName')AS NVARCHAR(128)) AS 'ServerName'
SELECT CAST( SERVERPROPERTY('ComputerNamePhysicalNetBIOS')AS NVARCHAR(128)) AS 'ComputerNamePhysicalNetBIOS'

I am hoping the output of the query will help explain the difference between instance name, virtual SQL server & server name
Post #529711
Posted Tuesday, July 8, 2008 7:55 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, May 5, 2014 8:20 AM
Points: 201, Visits: 405
QA

SQL VIRT Name QA1

InstanceName
NULL

IsClustered
1

MachineName
QA1

ServerName
QA1

ComputerNamePhysicalNetBIOS
ND1
===================================

PR

SQL VIRT Name PR1

InstanceName
NULL

IsClustered
1

MachineName
CL2

ServerName
CL2

ComputerNamePhysicalNetBIOS
ND3
-----------------------------------------------

most likely the cluster\windows configuration was done differently.

during the installation we chose default for instance name (so it should be a machine name)

the solution might be to give to a cluster and to a virt sql the same name
because now we have clustername cl1, nodename nd1, clustergrpoupe name sql and virtual sql name QA1

this is all tooooooo confusing







Post #530046
Posted Tuesday, July 8, 2008 4:37 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 11:23 PM
Points: 744, Visits: 472
It certainly looks like the installation was different between QA & PR.

The information you gave is still suggesting that the SQL Server instance was not installed in the Virtual Server named 'PR1'. Instead it has been installed into the cluster group CL2.
If you would like to confirm this, please check Cluster Admin as mentioned in my previous 2 posts...

Where to from here?

It might be possible to move a Clustered SQL Server instance into a different cluster group (e.g. Move all the SQL resources from CL2 into PR1), however unless you can find a solid reference on how this can be done I highly recommend you do not follow this path.
Even if you do manage to move the SQL resources into PR1, you will always have a difference between QA & PR. This difference may not be visible straight away, but somewhere in the registry there could be a difference, and when it comes time to install a hotfix, service pack, or upgrade to SQL 2008, that’s when the problems will arise...
If it were my cluster, I would rebuild it (including OS). If that was not possible then uninstall / reinstall the SQL instance only.
Post #530412
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse