We have an active/active two-node QA cluster with four instances of sql. I need to add a fifth. In the past I always moved existing instances to the other node while installing a new instance.
Other than impacts to users from install reboots, is that a hard requirement?
QA is reluctant to have me put the four existing instances on one node for most of a day, fearing big performance slowdowns. Each node has 250GB of memory and each instance is allowed 50GB. Netapp disk backend.
I am new to SQL Server 2012 clustering.I added a new instance to one of the two nodes.when I try to move it to the other node it fails.Do I need to install it on both?If so, what options do you install on the second node?
When adding a node to a SQL Server 2012 Standard edition cluster, how I do I identify the location for SQL server shared components and the rest of the SQL Server installation binaries?
When adding a node to a SQL Server 2012 Standard edition cluster all the binaries went to the C: drive default location. We put those files on a different drive when installing the first node. What needs to be done so both nodes have the binaries on the same drives and folders?
In QA we have a two-node cluster with four instances of sql. In trying to add a fifth, I was given an IP address already in use so the install hung.
I removed it from the cluster but it is still there in the registry etc on the node I was working on.
I read about using the maintenance tab of the sql server install to "remove a node" but the terminology is confusing. To me a node is a physical server and an instance is an instance of sql server -- not the same at all but they are often referred to as the same thing.
I definitely don't want to remove one of the servers from the cluster.
I am trying to install the MS SQL Server 2012 Failover Cluster on Windows Server 2012 . I successfully Installed the Failover cluster instance on my primary node.
But when I am running the installation process on passive node to add node in the failover cluster I am stuck with very unique kind of issue.
I am following the Standard process of Installation and I am getting the same windows for each next process, but after License Agreement window when I get the Cluster Node Configuration window, then in "SQL Server Instance Name" drop down box I am not getting the Name of Instance which is already installed on the primary node. But this Instance complete information is appearing in below given box.
Only issue is Instance name is not appearing in the drop down list, that's why I am not able to select and when I click on next it trough error and do not proceed.
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).
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.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
I have installed a SQL Server cluster recently.Noticed below errors logged in the error log. I understand that SPN is not getting registered, hence this error.What permissions SQL Server service account? Service account is admin in local nodes anyway.
"SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service.
This is an informational message. No user action is required.SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon atte
2015-06-12 18:11:06.970 Logon Error: 18452, Severity: 14, State: 1. 2015-06-12 18:11:06.970 Logon Login failed. The login is from an untrusted domain and cannot be used with Windows authentication "
SQL Server 2005 cluster. Active-Active. We want to create two instances. The two nodes are named:
mike-940-01 mike-940-02
I read somewhere that there can only be ONE default instance in a 2005 cluster. So I interpret that as meaning that I can only have one instance named after a virtual server (example: mike-940-03) and the other instance has to be a slashed instance (example: mike-940-03/instance1). But what if I create another virtual server (example: mike-940-04). Can I install a default instance in that server? Can someone help me clarify this?
Also, if I'm using all slashed instance names, then what does it choose as the base name before the slash? In other words, what decides which virtual server name is used? Is it the management node? Is it one of the nodes?
My objective is to keep consistency in the naming on the cluster. If I have to use slashed instances, then I want all sql server instances to have a slash.
Sorry about the confusing explanation, but that's probably a symptom of MY confusion.
If i have a 2 node cluster running a single instance (default) and i want to add another instance to the cluster , can i install the second instance as a defualt instance ?
Since the cluster instances are referred to their virtual names/ip's and if i choose to intall the binaries of the second instance to a different location is this possible?
Since in theory you never have 2 default instances running on a single server but each within a virtual server?
Normally i install a named instance but do i have to ?
We currently have a 2 node Active/Passive 2 named instance SQL 2000 cluster. We will be chaning the configuration to Active/Active, basically moving 1 instance to the passive node (so we can take advantage of the resources on the passive node).
We would also like to add 3 nodes to the cluster making it a 5 node SQL cluster. What we are thinking of doing is basically making it an Active/Active/Active/Active with the 5th server being passive. The question I have is will I be able to add and install the 3 new nodes without having to redo the SQL cluster? Should I install the two new active nodes with the default SQL instace or do I have to install SQL with named instances? (actually I think the named instances is the way to go but then I wouldn't be posting here if I was sure about the answer).
I've installed MSCS on two Win2k3 x64 Enterprise systems. On the first I installed SQL 2005, and all went well. All resources are online and SQL works, migrated 25 databases into the new install. Installing SQL 2005 on the second node is problematic. If I select install cluster resources, I have to define new stuff for a new group. If I don't install cluster resources, then the install is all local (nothing on the unseen shared disk resource.)
It does not see the shared disk resource during install, the Quorum is good. I can move the Cluster Group between servers with no problems. None of the SQL resources is available on the second node. Error is basically "a cluster node is not available for this operation".
The Sql Server and Sql Server Agent do not even acknowledge the existence of the second node, and it is not available as a possible owner. i can't find any specific instructions on installing the second node. The other SQL resources say the second server is an available possible owner. None of them will take ownership and run the resource.
I have a sql server 2005 standard edition with Active/Passive Cluster in production.
I have a new requirement where i need to create a new instance on this active/passive cluster that can be used by our sharepoint servers. Can somebody please let me know what are the steps that i need to follow like
1.What i need to ask my network admin? 2.How i need to proceed installing? I am planing to do this over the weekend where i have the liberty of some down time. Any help greatly appreciated Thanks
I am looking for a best practice or any suugestion on the best way to install an additional Sql 2005 instance in a cluster environment. We have a production environment that is active/active/passive and need to install an additional instance with a little impact to the current production instances as possible. Ant suggestions or articles I can review?
I have a SQL 2008 R2 2 node cluster. For DR testing, I need to restore an instance on a new server (completely isolated). The existing instance runs on what I would call an alias. The actual cluster host name is SQLPROD (cluster nodes are SQL01 and SQL02). The instance runs on server SQLPROD-APPLE. The instance is called APPLE. In production, I use SQL Management Studio and I connect to SQLPROD-APPLEAPPLE.
I've setup a new VM to run SQL. Not a cluster. Host name is SQLREC. The new Vm has all the IP addresses that were on the cluster and the DNS for all the aliases are correct. I've installed instance APPLE. I created an alias called SQLPROD-APPLE. When I try to open SQL Management Studio and connect, I can't connect to SQLPROD-APPLEAPPLE. I can connect to localhostAPPLE, SQLRECAPPLE, 192.168.168.50APPLE.
When I attempt to connect to the alias I get error 18452. Pinging the alias resolves correctly. I haven't gotten to the database restore yet, so that's not a concern. I'm just trying to validate the connection first with the correct server and instance names.
The situation is like this,in my Requirements table,my fields are requirement_name,req_id and allow_multiple.allow_multiple.The fiels allow_multiple has a value of 0 and 1.In the Staff table,the fields are staff_id,staff_name,req_id.When we add requirement name to the staff table ot should check for the allow_multiple field, if it is 0 i can only add 1 instance of that requirement to the staff and if it is 1 i can add many instances of that requirement to the staff.How can i do that?
I understand most of the concepts for the Active/active setup. I am setting up a 2 node cluster. My question is can I use the default instance name (one default instance name per group) when setting up each instance or do I have to use named instances . I am assuming that since each group is a virtual machine that I can get away with using the default instance, but I cant find any documentation to confirm my frequently wrong perceptions.
I want to set it up like this
Instance1 Group
Group resources Default SQL Instance Name Installation Preferred Owner Node1
Instance2 Group
Group resources Default SQL Instance Name Installation Preferred Owner Node2
I am trying to remotely connect to a SQL 2005 Instance on a cluster. I see the following error:
No retry on exception System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I have enabled TCP/IP , Named Pipes on the node. I have turned off IPSec on the clients as well. I am using the following connection string : "Integrated Security=SSPI;server=servernameinstancename;Pooling=false;database=TrialDB"
I have a system running a sql 2000 instance w/ multiple databases located in a SAN. I would like to cluster my SQL 2000 environment on the same system. Can I do this without reinstalling another database instance? Can I put my current default instance and put it to my virtual server instance? Help is really appreciated. Any tips and links can be helpful to me.
Having problems running the BPA for 2012. We setup using a clustered environment, SQL Server installed using default instance, and a static port not 1433. When I try to run the BPA using the instance name it says it doesn't exist, and won't let me add a port number. However, if I use MSSQLSERVER as the instance name it runs with no port specified and returns results. I assume that it doesn't require a port because the default instance would pull from the Browser Service and the using MSSQLSERVER is the same as running the default on a standalone server. Are those assumptions correct?
I have a 3 node cluster running 6 instances of SQL Server, I want to install Analysis Services along side of one of the SQL 2005 instances. Thus one of the cluster instances would host SQL Server DB, Analysis Services and SQL Agent. Is this possible or does Analysis Services need it's own Cluster Instance.
I've a fresh installation of SQL Server 2014 Enterprise on Windows Server 2012R2. I've setup de Windows Server Failover Cluster and the validation test has been successfully passed. I use mountpoint so I've disk M: that is the host drive for mounted volume m:Isql2014A that is the base folder for mounted volume
into these 5 mountpoint I've placed the SQL Server files.
After the installation of the first FCI I've re-run the cluster validation wizard and again it has passed successfully. When I try to failover the instance from one node to the other I have 2 problem:
1) every time I do failover, some disks fail to come online for a while and then succeed :
Cluster resource 'CLD - IstA - TempDB Data' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
2) sometimes the SQL Server service fails to start, in the error log I see that the master database is not accessible. The master database in into the m:isql2014abinbackup.
I have a SQL 2000 clustered environment with 4 SQL instances and i need to remove a specific instance from the cluster the resources(physical drive,virtual IP,instance name) being used by it
Is there a way for multiple SQL 2005 instances in a cluster to share drives for user databases.
Once we install our instances in the cluster using seperate disk resources. Can we then have multiple instances share the same physical disk for user databases only. This is for a test environment.
I'm getting an error adding Replica to SQL AlwaysOn failover cluster in the new availability group wizard. When I enter the name of the target node (secondary replica) server and press connect, I get the following:
A network-related or instance-specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2) The system cannot fine the file specified
The SQL Browser service is up and running on the target. I am using an Azure VM for my SQL instance. This cluster spans geographies from our on-premise site to Azure via a VPN. This is a multi-subnet cluster. I'm attempting to create a new AG from the primary replica node and the target is a node on Azure called SSASNodeAz03.
[URL]
Full error:
Connect to Server Cannot connect to ssasnodeaz03
Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2) The system cannot fine the file specified
We have a SQL 2008 Instance existing on active/passive cluster with 2 nodes running on Windows server 2008 R2 Ent. Edn.
Now we need to install another SQL instance on this cluster. So what are the prerequisites apart from new IP address? Do we need shared disks or can the existing disks can be utilized?
Hi all. I have ran into a annoying situatin on sql cluster. Config is: w2k3 EE x64 r2 - two nodes sql 2005 x64 standart v2153 2instances, active-active cluster. While changing tcp port configuration of one instance (using configuration manager) I have acidentaly created that setting: - All IP dynamic port and All IP port was set to same number while separate IPs have enabled dynamic ports and does not have static port set. This situation leads to unability of starting the instance anymore. There is no need wide explanation, its quite clear - while starting instace, it was configured with static port and with dynamic port with the same number, so port conflict error takes place. Problem was how to escape from this situation. On non clustered sql is quite easy, because these settings are stored in registry and also can be changed thorough Configuration manager, easy solution. Nor on the cluster.. Modifying the registry even on both nodes was unefective, every try to start instance fails with port conflict error and bad config was saved to registry again. I wasnt able to find where this config resides and change it to corect values. I have revealed only that it is not stored in instance master DB (restoring it from backup). Looks like its held somehow by cluster service itself, but I didnt find where it should be and how to edit it. So the last possible option take place (time was against me) - reinstalation of whole clustered instance. Nice example of how one click can create you a 2 days of work... Iam still interested if there is a smooth and easy way out of this situatin:-) So if anyone knows..... If there is not, I realy warn everybody.
