This post is more than 5 years old
31 Posts
0
682
November 17th, 2008 07:00
SQL2005 on autostart 5.3 SP1
After I finished installation and configuration, I tried to failover to test all its function.
I found when I failover to the second node, the "start up" icon in the SQL management studio was RED，It should be a green arrow as normal. The strange is that I can still open the database and open all the "+" mark. And I check the services in the MMC, SQL server and SQL agent were startup successfully.
After I failback to node one, the icons in management studio was correct.
I also tried to not to use autostart to bring up the SQL services, I bring up SQL services on node tow manually, and icons were correct too. I don't know what's wrong with that, please give me some advice.
My environment:
OS:Windows2003 ent X64
SQL2005 SP2
data source: SRDF
I found when I failover to the second node, the "start up" icon in the SQL management studio was RED，It should be a green arrow as normal. The strange is that I can still open the database and open all the "+" mark. And I check the services in the MMC, SQL server and SQL agent were startup successfully.
After I failback to node one, the icons in management studio was correct.
I also tried to not to use autostart to bring up the SQL services, I bring up SQL services on node tow manually, and icons were correct too. I don't know what's wrong with that, please give me some advice.
My environment:
OS:Windows2003 ent X64
SQL2005 SP2
data source: SRDF
No Events found!
yito1
262 Posts
0
November 17th, 2008 23:00
The instance name that I was describing is Admin guide P.197-198.
-New SQL Server Instance -Instance Startup Name dialog box
Moreover, the alias that I described is Admin guide P.196.
-New SQL Server Instance - Node Alias Selection dialog box
The phenomenon will occur if the physical node name is input.
Because service starts by Node1 when the SQL Server service starts.
When starting with node2, this starts service with node1.
Therefore, if Server Manegement console is started, it becomes red status.
Following Event log is sure to be displayed.
Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6011
Date: 11/18/2008
Time: 4:09:35 PM
User: N/A
Computer: node2
Description:
The NetBIOS name and DNS host name of this machine have been changed from node2 to node1.
yito1
262 Posts
0
November 17th, 2008 20:00
Did you use and compose SQL2005 Module?
Did you input the alias to module wizard's Instance name?
This phenomenon occurs if the alias is not input to Instance name when composed of Module.
Correct the following if you correct it.
Resource group--settings tab--Startup Sequence--Startup scan Script
$errorCode = &ft::SetActiveComputerName("alias"); <-----
Fill in the alias that you made in the part of Alias.
power3
31 Posts
0
November 17th, 2008 22:00
I did use the SQL 2005 module to create the resource group.
I am still a little confuse.
Did you mean the "instance name" dialog box in admin guide page 199?
This is a required information from 5.3SP1, and I fill in the SQL instance name as server name of node one(default instance name is server name).
Is it correct? Or what instance name should I input?
power3
31 Posts
0
November 18th, 2008 01:00
I think I may know what the problem is.
The root cause should be that there are different instance name between two nodes.
Do you know how to change instance name in SQL?
yito1
262 Posts
0
November 18th, 2008 02:00
The instance of SQL is default.
The setup of your SQLServer is correct.
It only has to make alias with AutoStart and to input the alias to "Instance Startup Name dialog box".
Anyway, test the method taught by me.
power3
31 Posts
0
November 23rd, 2008 20:00
I install two SQL with default instance name, and that will be the server name.
That makes two servers with different instance name.
I found a way to make them identically.
1.select @@servername
2.
sp_dropserver 'old_name'
GO
sp_addserver 'alias_server_name', 'local'
GO
3. --restart services.....
4.select @@servername
5.change the script content you taught.
After these, I can failover SQL resource group with correct service icon.
Thanks for your fully help.