Hi,
I have 2 W2K box's and want to install 4 SQL servers on each box & each different character set and want to setup clustering (Active - passive).
Do any one of you setup this type environment ?, Pl. let me know if you have any suggestions ..
Regards,
Madhu
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
We have 5 instances on our clients old machine with SQL 2005, now they want us to move on cluster environment with SQL 2012.
Once I have installed and configured SQL cluster with single instance, but how to install SQL Cluster environment for Multiple instances.
Should I install all the instances first and than have to configure cluster ?
OR
Is there any way that first I will install cluster and than we can add the instances ?
What I have- Sql server 2012 (Standard Ed) Cluster on Windows 2012 R2 with both instances running on the same node- just to save on License, i.e. technically it’s Act/Pas cluster.
What I am looking for- how to configure cluster (e.g. via quorum, etc) to force both instances failed together? Means if for some reason 1-st instance will fail to node 2 another instance should follow (otherwise it will be Act/Act cluster and 2-nd license is required).
If there is no standard way (cluster configuration I mean) to do it I should create some custom process to monitor where each instance is running.
My environment has a 4 node cluster , 2 in primary and 2 in sec dc. Storage is sperate for both.
Need to setup always on for 4 Instances there on the 2 nodes of the primary dc. Is there any restriction in setting up always on for multiple instances for a cluster.
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
View 4 Replies View RelatedI've a SQL server 2014 setup on a server recently. Can I add a new(second) instance to the SQL server (already running one instance)?
View 6 Replies View RelatedHi All..
We are planning to build a cluster environment on MS SQL 2005. We want to install multiple named instances in a single database server and use cluster for that database server.
Is this option possible ? Any relevant documentation would be helpful
Thanks in advance
Regards
Madhav
Hi There
I have found no real documentation on this, so any links would be greatly appreciated.
We have an existing 2 node active active cluster.
A default and and named instance SS2005 Enterprise Edition are installed on the cluster.
Recently we acquired new hardware, 2 servers, which we added to the cluster so we now have a 4 node cluster.
The 2 new nodes have OS etc installed.
Now i have installed sql on a new multi node cluster, i have upgraded sql server in an existing cluster BUT i have never installed sql on an existing cluster for new nodes for multiple instances.
Now i presume you simply run the install on one of the new nodes, do this for a default instance, selecting both 2 new nodes to installl on. And do this again for the named instance.
But in the past I have never been promoted for which nodes to install sql on, it simply does all the nodes BUT i do not want this.
And how will the cluster know where the binary files are for each instance on the new nodes?
In a nutshell, how do i install sql server 2005 for 2 new nodes in an existing 4 node cluster for multiple instances ?
Thanx
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .
Â
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
2. Run the following commands.
a). Command: Winmgmt /salvagerepository %windir%System32wbem
b). Command: Â Winmgmt /resetrepository %windir%System32wbem
3. Re-enable the WMI service
Command:Â Â Â Â Â Â Â Â Â sc config winmgmt start= autoÂ
Last command to run after above steps
4. Command:Â Â Â Â mofcomp "%programfiles(x86)%Microsoft SQL Server100Sharedsqlmgmproviderxpsp2up.mof"
File not found Error for above command.
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
View 4 Replies View RelatedI an involved in a project that will have five sql server instances on an NT cluster.
I cannot find anywhere on Technet info on what happens when a single instance fails. Do they all have to fail over or just the failed instance. This is important so that we get the disk layout correct.
Can anybody help ? or point me to any docs on this.
Hi
I have a cluster with 4 sql server 2000 instances and would like to upgrade 2 of these to sql server 2005 - is there any document or list of things to ensure I do
Thanks
Hi,
We have a new failover cluster (Windows 2003 SP1, Microsoft SQL 2000 SP4) with each node of the cluster hosting 7 SQL Server instances in a 2-node active-active configuration connected to a SAN. We are planning to move some SQL Server Instances(from existing stand-alone servers) into this Cluster. Any insight into the process of moving SQL Servers into the cluster would be highly appreciated.
Best Regards,
Himansu
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server.
Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move.
I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance.
For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work.
Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
thanks,
Garth
I'm reading up on Always on and I am confused what is the difference between AlwaysOn Availability Groups and AlwaysOn Failover Cluster Instances.
View 3 Replies View RelatedIt is an active passive cluster which doesn’t allow any testing. All instances have to be failed over together, we aren’t allowed to just failover 1 even for testing purposes. Node 1 is the active node and we can failover to node 2 for 30 days free of charge but services have to then be failed back.
We need to run the cluster with node 1 as the primary node always and 2 just use for failover testing or for less than 30 day periods whilst performing cluster patch upgrades etc.
Now l am sure we could fail over 1 instances at a time for testing and diagnosing issues plus if add a new instance that's not production to get to the platform level as the rest of the instances this would avoid taking production down in the fail over process.
I am trying to install multi instances on my server cluster 2003 R2 Sp2. Because of the compatibility issues with my services I need to install both SQL 2000 and 2005. With 2000 I can easily specify the instance and servername. The server name can be the same, but the instance has to be different. Is this true for 2005? I have found so far that for every new instance that you create that you need to have a different virtual server name. How can you utilize the same virtual name and have multi insances
servername$instance1
servername$instance2
and so on
ThatGuy
We are running with a 2 node windows cluster having three SQL instances on it.Â
OS: Windows server 2008R2 SP1
SQL : SQL server 2008R2 (10.50.6529)
Currently both nodes have 256 GB or memory and we are having multiple auto failover for resources. What will be the best practice for OS memory reservation (OS+tools) so that we can set SQL max memory settings accordingly?
Will installing another instance restart other instances?Server is Windows Server 2012 R2, SQL Server is 2012.
View 3 Replies View RelatedIF you need to change the IP Address of a SQL Server Failover Cluster instance, here is the steps:
1. Open up Failover Cluster manager.
2. Expand the MS Cluster Instance that your SQL Cluster instance resides on.
3. Expand Services and applications.
4. Select the SQL Server Service.
5. In the main window pane (Middle Screen), you should see your SQL Server Cluster name, expand the plus to the left of it.
6. Under your SQL Server Cluster name, you should now see an 'IP address' section, right click on it and go to properties.
7. In the properties pane, you can change your IP address by entering a static IP.....or assigning a DHCP enabled IP.
We have a SQL 2014 active passive cluster with 5 instances. When the cluster was installed one of the nodes was a virtual machine. As we started to have problems and this is not a Microsoft supported configuration we decided to replace the virtual node with a phyiscal one. On 3 of these 5 instances we configured static ports (1433 TCP) this was required for applications and firewall implementation.
Now with the physical node joined to the cluster we have issues with these three instances. Whenever one of these instances is moved to the passive node the server authentication is changed from mixed to windows only. I'm no SQL expert at all but to me it looks like the configuration of the instances are not replicated to the passive node? I found some similar problems on the net but these are mostly under sql 2008.
Hi,
I think this is a question for the specialists among us.
Can I use one general reporting server (installed on instance MAINREPORTING)
for multiple customers who all have their own sql instance (CUST1, CUST2, CUST3, ..)
I would use UserAuthenciation on the reportserver url to display the specific reports customers can use.
Is this possible, and what do i have to take care off concerning installation and/or configuration (especially on
the reporting side) ?
Greetings
Vinnie
We have 2 clustered SQL instances (2 physical servers in each cluster). Instance2 needs to be setup as a linked server on Instance1.
At this time port 1433 between them is not open. I am referring to the port on the network switch, not in the Windows Firewall (ports in Windows Firewall are already open).
Is opening the port between virtual IP-s sufficient? Or does port need to be open between all physical source/destination IP-s as well?
Have a production server, 12 Enterprise, and we are adding a new app to an existing instance. Â Next app needs SSRS and that was not put in the install request a year ago for the instance. Â
I do not think a reboot is required but have been wrong before. There are no SPs applied to this server and only last week we were given go ahead from one app vendor to apply SPs. Â That would have been done in monthly maintenance cycle next weekend. Â Our test server is doing just fine with all apps on SP1.
We are on SQL Server 2000 A/A cluster and are moving to SQL Server 2005 cluster.
Following are the list of things before proceeding, please let me know if it needs any corrections and add-ons:
(side-by-side) Planning for new installation of SQL Server 2005 ( SQL2005INST1 and SQL2005INST2) on node1 and node2 and restoring the databases on SQL2005INST1 and SQL2005INST2 from respective 2000 instances.
1) SQL2005INST1
SQL Network Name
SQL IP address
2) SQL2005INST2
SQL Network Name
SQL IP address
As 2000 is already existing on the cluster.Want some clarity on following questions.
Can I keep the data files on the same disk as 2000 was using ?
Do I need to have new disk for the Quoram drive?
Under "Virtual Server Configuration" wizard during the setup under "Network to use"--- for "private cluster network" and "public cluster network" do that IP Address and network address and network subnet will be different from what we gave for SQL 2000.
Thanks
ITTECH
If I install a new named instance of SQL Server 2008 R2 on a machine that already has 3 named instances that are upgraded to service pack 3, will the install of the new instance overwrite any of the current SP3 files? Will I have to re-apply SP 3 to the existing instances?
View 4 Replies View Relatedam trying to install sql 2005 with cluster option in win 2003 R2
servers
and keep getting sql database setup failed error.Summary log show that
it failed with error number 67.
It doesn't even create a SQLSetup0004_M2MTPONE_SQL.log file. core log
shows
Complete: DetectLocalBootstrapAction at: 2006/5/1 18:15:31, returned
true
Running: LaunchLocalBootstrapAction at: 2006/5/1 18:15:31
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe"
finished and returned: 67
Aborting queue processing as nested installer has completed
Message pump returning: 67
We have two machines in running enterprises version of R2 in a cluster.
I tried running the setup from both machines and got the same error.
I am trying to find a solution for more than week but no luck. Any
help is appreciated.
thanks - Kailash
Part of Summary log:
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : \M2MTPONEC$Program FilesMicrosoft SQL
Server90Setup BootstrapLOGFilesSQLSetup0004_NEWTPNT1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%Microsoft SQL Server90Setup
BootstrapLOGSummary.txt.
Time : Thu Jun 01 18:18:54 2006
Installing SQl2005 into on Win2003 2 node cluster, at the very end of the
setup receive a message 'Remote Setup failed'. Referred to some sql logs
and found this;
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe"
finished and returned: 1603
Aborting queue processing as nested installer has completed
Message pump returning: 1603
I've seen some similar errors on the web and suggestions about the Task
Scheduler being started on both nodes, but I ensured these were both started
before the install. SQL2005 does seem to be ok on the node1 where the
install was made, but fails when trying to failover to node 2.
Any help would be much appreciated here.
Thanks
Darren
Ok Here is the story with hopefully all the details.
I had a single node cluster Itanium server running W2k3 IA 64 Ent. SP2 with 2 x sql2000 ent sp4 and 1 sql2005 sp1 instances installed and a clustered file share.
All is well with them.
I attempted to add an additional node to my cluster which started out fine but when I tried to run the sql2000 setup to add this node, there are no warning or errors. Its a silent failure.
I tried many different scenarios but the results are the same. I evicted the node and then tried to run the setup on the evicted node. The setup ran without error. I tried to run setup on my single node cluster and it fails in the same manner. I read and read and from the sqlstp.log this is what I find. Does anyone have a clue what is wrong? i have check all my permissions but I can't put my finger on what it could be.Help Help.
1
<Func Name='InitDataFolder'
<EndFunc Name='InitDataFolder' Return='0' GetLastError='18'>
<Func Name='DetectComputers'>
1
<Func Name='DetectVersionOnMachine'>
NYCTDB04 D:SQL Server ENT 2000 - 64 BitSetupIA64inn 1
<Func Name='InsertVersionRecord'>
NYCTDB04 MSSQLSERVER 0 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2099209 1 NYCTDB41 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 BIZTALK 1 9.00.2047.00 1033 0 -1 -1 (64-bit) 133124 0 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 MYOFFICE 2 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2230280 1 NYCTDB42 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<Func Name='InsertVersionRecord'>
NYCTDB04 SHARED_TEMP 3 8.00.760 1033 0 3 1804890536 Enterprise Edition (64-bit) 2230276 0 0 1
<EndFunc Name='InsertVersionRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectVersionOnMachine' Return='0' GetLastError='183'>
<Func Name='InsertComputerNameRecord'>
NYCTDB04 0 50010 539101189
<EndFunc Name='InsertComputerNameRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectComputers' Return='0' GetLastError='0'>
<Func Name='DetectIpResources'>
<Func Name='InsertIpResourceRecord'>
_sql$IpResources 0 144.210.119.64 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='DetectIpResources' Return='0' GetLastError='183'>
<Func Name='DetectGroupResources'>
<Func Name='EnumerateGroupResources'>
SQL 2000 Shared Group(NYCTDB41) NYCTDB04 Disk Q: 0
<Func Name='GetDiskResourceLetters'>
SQL 2000 Shared Group(NYCTDB41) Disk V 0
<Func Name='InsertDiskResourceRecord'>
Disk V 0 V SQL 2000 Shared Group(NYCTDB41)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetDiskResourceLetters'>
SQL 2000 Shared Group(NYCTDB41) Disk W 1
<Func Name='InsertDiskResourceRecord'>
Disk W 1 W SQL 2000 Shared Group(NYCTDB41)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetVSInfo'>
SQL 2000 Shared Group(NYCTDB41) NYCTDB04 0
<Func Name='EnumVSIPResources'>
NYCTDB41
<Func Name='InsertIpResourceRecord'>
NYCTDB41 0 144.210.119.88 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSIPResources' Return='0' GetLastError='183'>
<Func Name='EnumVSResourceOwners'>
NYCTDB41
<Func Name='InsertVSNodeInfoRecord'>
NYCTDB41 NYCTDB04
<EndFunc Name='InsertVSNodeInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSResourceOwners' Return='0' GetLastError='183'>
<Func Name='InsertVSInfoRecord'>
SQL 2000 Shared Group(NYCTDB41) 0 NYCTDB41 MSSQLSERVER 1 D:Program FilesMicrosoft SQL Server V:Program FilesMicrosoft SQL Server ipgnasharedsql.service ipgnasharedsql.service
<EndFunc Name='InsertVSInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetVSInfo' Return='0' GetLastError='183'>
<Func Name='InsertGroupResourceRecord'>
SQL 2000 Shared Group(NYCTDB41) 0 0 NYCTDB04
<EndFunc Name='InsertGroupResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumerateGroupResources' Return='0' GetLastError='183'>
<Func Name='EnumerateGroupResources'>
Cluster Group NYCTDB04 Disk Q: 1
<Func Name='GetDiskResourceLetters'>
Cluster Group Disk Q: 0
<Func Name='InsertDiskResourceRecord'>
Disk Q: 0 Q Cluster Group
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='InsertGroupResourceRecord'>
Cluster Group 1 1 NYCTDB04
<EndFunc Name='InsertGroupResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumerateGroupResources' Return='0' GetLastError='183'>
<Func Name='EnumerateGroupResources'>
SQL 2005 Biztalk Group(NYCTDB40) NYCTDB04 Disk Q: 2
<Func Name='GetDiskResourceLetters'>
SQL 2005 Biztalk Group(NYCTDB40) Disk T 0
<Func Name='InsertDiskResourceRecord'>
Disk T 0 T SQL 2005 Biztalk Group(NYCTDB40)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetDiskResourceLetters'>
SQL 2005 Biztalk Group(NYCTDB40) Disk U 1
<Func Name='InsertDiskResourceRecord'>
Disk U 1 U SQL 2005 Biztalk Group(NYCTDB40)
<EndFunc Name='InsertDiskResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='GetDiskResourceLetters' Return='0' GetLastError='183'>
<Func Name='GetVSInfo'>
SQL 2005 Biztalk Group(NYCTDB40) NYCTDB04 2
<Func Name='EnumVSIPResources'>
NYCTDB40
<Func Name='InsertIpResourceRecord'>
NYCTDB40 0 144.210.119.90 255.255.255.224 Public
<EndFunc Name='InsertIpResourceRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSIPResources' Return='0' GetLastError='183'>
<Func Name='EnumVSResourceOwners'>
NYCTDB40
<Func Name='InsertVSNodeInfoRecord'>
NYCTDB40 NYCTDB04
<EndFunc Name='InsertVSNodeInfoRecord' Return='0' GetLastError='183'>
<EndFunc Name='EnumVSResourceOwners' Return='0' GetLastError='183'>
<EndFunc Name='GetVSInfo' Return='1168' GetLastError='203'>
<EndFunc Name='EnumerateGroupResources' Return='1168' GetLastError='183'>
<EndFunc Name='DetectGroupResources' Return='1168' GetLastError='183'>
<EndFunc Name='PerformDetections' Return='1168' GetLastError='0'>
Does anyone know how to install SQL 2005 integration services on a cluster machine?
I have an a-a cluster machine. Both nodes are using SQL 2005 naming instance. During the SQL installation, I did include integration services option as one of my setup items. The setup process was running fine but I can€™t connect to integration services via MS SQL Server management studio. I see below errors:
€œInvalid server name "TESTServerB123". SSIS service does not support multi-instance, use just server name instead of "server nameinstance".
Looks like I must use default instance for 2005 integration services. I re-ran the setup program and added a default instance on the same cluster node. (On that node I have one default instance and one naming instance). Now I can connect to the default SQL Server but when I click on €œstored packages€?, I don€™t see file system and MSDB. It shows nothing at all. Any idea how to make integration services running on a cluster machine?
Thanks
We are setting up a SQL 2005 cluster at our ISP and would like some feedback from anyone or DBAs for the pros and cons for the following setups.
Option 1.
http://img3.freeimagehosting.net/image.php?d2e8e7e923.gif
Option 2.
http://img3.freeimagehosting.net/image.php?11742dda91.gif
Basically, we need to know which set up is the preferred method.