Recovery :: AlwaysOn Database (two Nodes) - Named Instances
May 28, 2015
I have a 2012 AlwaysOn DB Mirroring environment set up with two nodes. Both have 5 installs of SQL named instances.
The issue we are having is when we patch one server and fail everything over, some of the applications will error. Some of the applications had to have their web.config files updated with hostinstance name because it seems to not work with DNS.
I am setting up a 3 node cluster as part of an availability group.Initially I tested failover between nodes using SQL Management Studio and everything failed over successfully when I stopped a node, and I was still able to write queries. I started to test with an application which connects using an SQL user and whenever I would switch nodes, I would get login failed. I believe the cause of this issue is because the server logins SID's which are tied to the database are different than the server logins on the other nodes which resulted in login failed.how can I ensure that the server logins SID's are the same between nodes? Is there a way of copying this over or how is this supposed to be done? I read a little about contained databases where I could just set the login on the database itself vs. creating a server login but I would rather not go down that route.
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.
We have an AG scenario where we are using WFC on a 2 node cluster. We are then using AG for mirroring the databases to both nodes and have a listener.
What I want to do next is to establish another copy of the database at a remote location. But I don't want to add the 3rd system to the WFC. I am not a big fan of WFC and I have seen it causes many more problems. The 3rd system will be in a remote location and the network not 100% reliable. I have seen in the past that it causes the entire cluster to hang and causing my production to crash which I don't want.
I there a way to add a 3rd node to the mirror configuration. I don't know if I can add a 3rd node to the AG unless it is part of the same cluster.
I know I can configure log shipping, I am fine with it but in the source, I have no control of which node the DB will be. I am not sure if a log shipping scenario can be configured using the listener instead of the physical host.
I have a situation where I have two servers in SQL Server 2012 R2 AlwaysOn Availability Group. One is primary and the other one being secondary. I am only running SharePoint Database on it.I have run out of space on the primary server and about to run out of space at the secondary server. I have tried shrinking database transaction log files, but it returns an error that it cannot be shrunk as the database is in the AlwaysOn Availability Group.
Questions: 1. Several forums suggest that databases need to taken out of AlwaysOn Availability Group in order for the shrinking to work properply? 2. Would it have any impact on the database if it is taken out of availability group and then added back?
I would ask if there some precaution on creating stored procedure on a database member of an always on group. I copied the stored procedure on all nodes but I'm not sure if this is enough to make it works in case of failover ?
I have configured replication between Always ON Availability Groups (Listener) (PUBLISHER), remote distributor to XYZ SUBSCRIBER...with above link ...
Now, I want to know how to replicate Data from XYZ SERVER a PUBLISHER to Always ON Availability Groups (Listener) (SUBSCRIBER)? Distributor Database being on XYZEX:
XYZ SQL SERVER as PUBLISHER, and DISTRIBUTOR to Always ON Availability Groups (Listener) SUBSCRIBER...
I had a server with SQL Server 7.0 I installed a named instance of SQL Server 2000 and then i passed all my DB of the 7.0 instance to the 2000 instance. Then i removed the 7.0 instance, that was the default instance. So at the moment there is only the 2000 version, but it isn't the default instance Can the 2000 instance become the default instance? (So that clients can connect to it simply through computer name, and not creating an alias)
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
How many nodes can you have in a cluster with SQL 2012 alwaysOn.
I understand that availability groups are limited to 5 nodes but if you had a 10 node cluster and decided to create multiple availability groups using various nodes within the 10 nodes but never exceeding 5, is that possible?
Or is there a counter or some validation from SQL AlwaysOn that actually hard limits to a grand total of 5 nodes in a cluster?
Two servers are configured with Windows 2008 / SQL server 2012 utililizing Always-On for HA. We need to upgrade both servers to Windows 2012 / SQL Server 2014 with minimum downtime(Time for Always-On failover). The upgrade to SQL 2014 is straight forward with for minimum downtime.The Windows upgrade(2008 -> 2012) is the problem. From what I have observed and read in blogs.The Windows node to be upgraded must be removed from the Windows cluster before the node can be upgraded to Win 2012.A Win 2008 and Win 2012 node can not reside in the same cluster. If this is true then the only option I can think of is to dump the DB on WIN 2008 server and restore on Win 2012. This is an outage(time it takes to dump and restore).Is there any other method to upgrade these two nodes utilizing Always-On of some other method without downtime?
I'm looking at installing 2008R2 and 2014 side by side, then using Mirroring to provide HA for the 2008R2 instance and AoHA for the 2014 instance. I'd be using the same two physical servers for both the Mirroring pair and the AoHA pair.
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 ?
We have an AAG environment. In order for the failover to be transparent we have to ensure that the login that is added in the Primary node is also added to the secondary node. Currently, we are adding the logins to the secondary node manually. Is there a way to automate this process so that a Login added to the Primary node is automatically updated on the Secondary Node.
I'm just starting to work with AlwaysOn Availability and WSFC.
I have in my environment (in Azure) a DC, WSFC and to SQL instances, so I have 3 nodes in my Failover Cluster:
WSFC SQL1 SQL2
If I simulate failure by shutting down one of the SQL boxes my Availability group seamlessly fails over to the other SQL instance - which is great.
However, I'm starting to look into the workings of the Quorum, my envt has the default settings and when I shutdown both of my SQL servers I expected the Cluster itself to go offline as 2 out of the 3 votes will be negative, but the Cluster is still up - Screenshot below when SQL1 and SQL2 are shutdown:
Going through the Wizard (but not changing anything) it shows following config:
Though to setup Alwayson, it is necessary to have both SQl Instances to be in same version, same database file path , etc.But, is this possible to setup the AlwaysOn between a default and a named instance?
We have a vendor product that can only handle up to 18 characters for the server name and the instance name (we did not know this when we created the named instance) and of course our combined name is 19 characters, so it trys to pass the 18 charater name and then fails with the following error:
[LOG] Unable to read local eventlog (reason: The data area passed to a system call is too small)
So, can i rename the instance, or do i have to create a new named instance?
Do you need to enable Always on Availabilty on all the instances or only the instance you need to ?. We have 4 instances on a 5 node cluster and we only need one instance for the Always on to be enabled. Do we need to enable on all 4 instances ?
One of my actual production environments is a Failover two-node cluster, SQL Server 2005 SP3 on Windows Server 2003 R2. Recently, the node 2 was failed, so I formatted a new machine to add the new node, but it failed with the following error: “Adding nodes to the Virtual Server definition using a newer version of Setup is not allowed.”I have searching across the web for a solution but I can’t find it.
The Summary file “Summary.txt” are: Microsoft SQL Server 2005 9.00.1399.06 OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Time : Thu Jun 04 13:04:38 2015
[code]....
One point of my attention, it’s that the Product Version that appears on this summary file corresponding a 9.00.1399.06 that is to say, a RTM version, not SP3 (9.00.4035).Based on this, I went to the path where the files of installation are (ARPWrapper.exe), "C:Program FilesMicrosoft SQL Server90Setup Bootstrap"and I 've found that these files contain a different version of what I have currently installed. For example, in properties of ARPWrapper.exe the version of this is 2005.90.1399.0 The same goes for the rest of the files in that folder:
Is it possible that the solution is to replace these files with the corresponding version, in this case the version 2005.90.4035.0(SP3) and continue with the installation?
Informatica jobs were erroring out with a sql server driver error while connecting to a named instance in SQL Server. The issue was because in sql server named instance, the port was allocated dynamically and Informatica 7.1.4 (provides 4.21 version of Datadirect odbc drivers for SQL server) which dont have support for named instances with dynamic port allocation. This feature is only present from version 5 of the Datadirect odbc drivers for SQL server To fix this issue, I need to allocate the port for the named instance instead of getting it dynamically. My questions 1) Whats the impact of doing a port allocation for the named instance on the existing environment. 2) Is there any issues which we can foresee in the applications 3) Things which i need to be aware of Thanks in advance sreenath
We are using a system that has uses four instances. On each client to the server we used the ODBC settings to connect to the different instances. We have since reinstalled the server, and now we are unable to find or 'see' any of the databases, except for locally.
E.g. The first database we install is named Foo, with database Bar. It is set up on port 1433. The second named instance is Foo2, with database Bar2. It is set up on a dynamic port.
We now try to connect to the database with ODBC. We connect to SERVERFOO, and then select the BAR db. It works fine. We then try to connect to the database SERVERFoo2, it lets us in, and then all we can select is the BAR db. I don't know what is causing this. We never before had to edit the settings in the client config for the odbc settings (e.g. to set manually to TCP port 1433) and I have checked the sql config manager to ensure that tcpip settings are allowed and will "ListenAll".
What more do we need to do? I think the browser should be installed, but my collegue disagrees.
Any ideas as to why we can only see the database referenced to 1433 port, and why no other port works, when we never had to do that before?
Using VS05 SP1 Pro SQL Express In converting a program from VS03/MSDE, long ago I installed SQL 2005 Express with Advanced Services and everything was fine. Windows Update has recently been failing to install SQL 2005 Express with Advanced Services SP2. After no answers from the forums, and logs that were of no help, I decided to uninstall SQL 2005 Express with Advanced Services and reinstall SQL 2005 Express (basic version). As a test run, I did it on a desk top, no problems what so ever. However, on my laptop, it has been a nightmare.
Question 1) in control panel, add/remove programs, all of SQL 2005 Express with Advanced Services uninstalled fine except one item - I am unable to uninstall MS SQL 2005 Backward Compatibility, getting the error message A network error occurred while attempting to read from the file c:windowsinstallersqlserver2005_bc.msi That file is not on the hard disk. After installing SQL 2005 Express (the basic version), this problem persists and I cannot uninstall MS SQL 2005 Backward Compatibility for the same reason. How can I get rid of MS SQL 2005 Backward Compatibility?
Question 2) Windows update still is trying to download and install SQL 2005 Express with Advanced Services SP2, even though I have uninstalled it. How to manually get rid of whatever settings are triggering this?
I have a server computer named 'X' and I would like to install 2 instances of SQL Server 2005
1. SQLTEST
2. SQLDEV
During installation. if I select Default instance then it will name my sql server instance X . I don't want that. I want to have essentially 2 named instances to make it clear to the users that they are using a test and dev sql server. Whats the best way to do this? I am open to suggestions if there is a different way to do this.
Is it required to have a default instance? Can I have 2 named instances XSQLDEV and XSQLTEST?
Also, on the SQLTEST I will be installing reporting services. By not having a default instance will it cause issues for the SSRS installation.
I'm struggling a little with this. I hope someone can help.
Ho do i install SQL Server 2005 Express so i can connect to it with "localhost", not "<MACHINE_NAME>/SQLEXPRESS". I cant seem to find any obvious setting in setup.
We have a client which they have production 2 node cluster environment. On it around 200 databases with single SQL instance.
Now client wants disatster plan for these 200 database. In these 200 database 3 db's are around 80 GB each databases remaing are less than 5 DB.Note: All these 200 db's are having produciton sites (i mean to say each db is having single site)
For this DR paln clinet is going to provide other DR server,they wants to setup DR between exsting produciton cluster instance to this DR server.
So in this case we have suggest SQL server AlwaysOn availability group.
Here my main question is can we keep all these databases in single AG? .If yes, guidlines to move up. if not, do we have any limitations.Also, best method to setup for this DR plan.
Merge replication on AlwayOn is configured, working fine on Original Publisher.When failover to possible publisher data is not being replicated.
Replication Monitor Error:
Message: Validation failed for the publisher 'RIMDNS' with error 21879 severity 16 message 'Unable to query the redirected server 'RIMDNS' for original publisher 'UNITEDKINGDOM' and publisher database 'TD_AO11' to determine the name of the remote server; Error 2, Error message 'Error 2, Level 16, State 1, Message: Named Pipes Provider: Could not open a connection to SQL Server [2]. '. '.
I've set up a SQL server 2014 cluster with AlwaysOn availability groups. Upon creating the AG i opted for full syncronisation to a specific SMB share.Now i want to change that share because it has to move to a new server. How can i do that? I found no settings in the SSMS for that.
I am using robocopy to copy my sql server backups to a fileshare. This is working great except for named instances.I use Ola Hallegren's backups which create a folder called xxxx$xxxx. Robocopy can't seem to handle the $.
We've read about a single installation of SSIS applies to all SQL instances on a server. We've also read how by default SQL Server stores SSIS packages in the MSDB database on the default instance and if you want to have packages stored on a named instance you must modify msdtssrvr.ini.xml. Here are our questions.
1 - If msdtssrvr is modified to reference a named instance, such as <ServerName>SQLTESTINST1<ServerName>, when I connect to Integration Services through Management Studio do I still specify the default instance name in the login window? That's the only way we have been able to connect and despite specifying the default instance name, the packages displayed are those of the named instance.
2 - If I am correct that you must always specify the default instance name when connecting to Integration Services, then in order to eliminate confusion regarding what SQL instance's SSIS packages I am viewing under the folder structure I can create SQL Server folders by modifying msdtssrvr.ini.xml. For example:
I then restart the SSIS service and can now see the following folder structure.
Running Packages Stored Packages
+ File System + MSDB + MSDB-INST1 + MSDB-INST2
If I expand MSDB-INST1 I will only see packages saved on the instance named INST1. The same is true for INST2. If I expand MSDB I will only see packages saved on the default instance.