Always on Availability on 2 different SQL Server clusters

SQL Server 2012 EE on WIndows 2008 R2.
Is it possible to have Always on Availability on 2 different SQL Server clusters ?. Could 2 SQL Server clusters be on 1 Windows server failover cluster (WSFC) ?. We have a Prod domain and DR01 domain with 3 nodes SQL Server clusters each. How can we setup
Always On Availability groups on these clusters to make replica of Production databases on the Prod to DR01 domain cluster ?. What do we need to do to get this working ?...................Thanks.

DCarlos unfortunately the requirement for AlwaysOn Availability Groups are a Single Domain, A single WSFC. The WSFC in multiple sites is supported with either a stretched VLan or multiple Subnets.
If your environment does require you to have different Domains for Prod and DR then you would have to look at potentially other ways of achieving your data replicated across from prod to DR.
You could look at using Database Mirroring (Yes I know this has been marked for deprecation) to achieve your data transfer. Or depending on your RPO and RTO requirements Logshipping may be an option.
Thanks
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

Similar Messages

SSRS report through data subscription - Connect to 2 different SQL server DB for excel attachment in EMail Deliery

I need to connect to 2 different SQL server without creating linked server for generating report. Is it possible in SSRS 2008 report service?

Yes possible
You would just required created two data sources which points to both your SQL Servers. And inside report you can create datasets based on each of these data sources to retrieve and display the data from them. In cases where you would require merging the
data from both the systems you can use functions like Lookup, LookupSet etc. Reports created in SSRS can be rendered in a variety of formats like Excel, PDF, CSV etc
see
http://www.allaboutmssql.com/2013/08/ssrs-example-for-lookup-lookupset-and.html
http://www.sqlcircuit.com/2012/03/ssrs-2008-r2-lookup-how-to-use-multiple.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Connecting to different SQL Server servers?

I'm very interested in trying out (using) SQL Developer, but have a problem connecting to 2 different SQL Server servers on my laptop. I have both SQL Server 2005 and 2000 installed. I can connect to my default server (2005 - localhost), but how can i connect to my second server - localhost\SQL2000?
Thanks.

In these, there has has to be different ports set up for each server. so default is 1433, but this can be set as administrator and set differnt ports for each server. In the latest builds we have support for native authentication so this should ease issue like this somewhat.
Barry

Choosing VM as high availability for BizTalk's SQL Server databases

Hi,
I'm lloking to choose the architecture of our BizTalk 2013 solution.
The application server will be build on virtual machines, but I still have interrogation about the SQL Server.
Is a SQL Server on a VM supported for BizTalk 2013 ?
Because in case of physical failure, the VM moved to another server can we considered the VM as a solution of High-Availability ?
thanks for your reply.

When the SQL VM fails over what attributes of the server will change? If everything including the server name, the mapped SAN locations (for Databases) and/or the versions of SQL will remain the same then it will behave like a temporary network outage between
the Front-end and the SQL.
If however, the failed over VM has a different set of mapped location for DB then you would need to establish a BizTalk Log Shipping between SQL VM 1 and SQL VM 2. In this scenario, the recovery will require time and cannot be automatic.
A word of caution though. If you have SLA's pertaining to transactions/messages per second with the customer then you might want to evaluate having dedicated boxes of SQL. The SQL Licensing is PER CORE and in a VIRTUAL ENVIRONMENT all the
CORES have to be licensed since the Virtualization does not permit you to BIND the VM to a specific set of CORES. The same would apply for your BizTalk Servers. This just might work out costlier as opposed to the dedicated server environment.
Regards.

Always on Availability groups using static SQL Tcp Port

Hi, I have 2 SQL 2012 servers in my DMZ and I have assigned SQL to run on a static TCP Port. I would like to setup Always On availability groups on the servers but I cannot get the failover to work with the static TCP port. It works fine
with dynamic ports.
When the failover is initiated it attempts to connect to the secondary replica with out using the static port, can someone tell me how to setup the availability group using static tcp ports.
Thanks,

When I setup the secondary replica I added the port number, but it doesn't appear to use it for failover. I add the secondary replica w/o errors.
I am not sure how to add the port number to the primary.
Dave
Hi Dave,
Based on your description, could you please post the error message when getting failover to the secondary replica?
In addition, If you use the default port of 1433 for availability group listener VNNs, you will still need to ensure that no other services on the cluster node are using this port; otherwise this would cause a port conflict.
If one of the instances of SQL Server is already listening on TCP port 1433 via the instance listener and there are no other services (including additional instances of SQL Server) on the computer listening on port 1433, this will not cause a port conflict
with the availability group listener. However multiple instances of SQL Server (side-by-side)should not be configured to listen on the same port.
For more details, please review this article:
Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server).
Thanks,
Lydia Zhang

Uninterrupted availability of data in SQL Server

I'm trying to solve a problem my company has in its data warehouse of data availability. We have dozens of transactional databases in production from which we pull data to create a cache of data that we make available to reports for both internal and external
customers.
The problem I'm trying to solve is I want all of the people using the data to still be able to access the previous version of the data (maybe data from an hour ago) while the new data is being refreshed. I have looked at a lot of ways this is possible. From
the very manual, the built in solutions, or a custom drive cloning solution but I'd like to hear from the community what people think is the best way to go about this. The server version is SQL Server 2008, but we could install 2012 in time for this need.
Right now I'm leaning towards AlwaysOn Availability Groups but if there's something better I'd love to know about it.

Thank you for your response. It took a few days but I finally had time to look at the article you linked. Database snapshots look like they are exactly what I need at first, but I read two lines in the article that make me think they may not be.
Under "Limitations of Database Snapshots"
When a page getting updated on the source database is pushed to a snapshot, if the snapshot runs out of disk space or encounters some other error, the snapshot becomes suspect and must be deleted.
And under the section titled "Disk Space Requirements"
Database snapshots consume disk space. [...] Compared to a full copy of a database, however, snapshots are highly space efficient.
A snapshot requires only enough storage for the pages that change during its lifetime. Generally, snapshots are kept for a limited time, so their size is not a major concern.
These two statements seem to say that the snapshot changes as the underlying database changes. I would like a snapshot that remains unchanged while I refresh the underlying database. After which I can refresh the snapshot so that people querying against
the snapshot get data from a version of the database in a state where the refresh is complete. I don't want people to query against incomplete, partially refreshed data.
Is there a way to tell the snapshot to not respect any updates that occur in the source database? Or maybe at least ignore updates for a period of time?
Snapshot does not get updated.. As you update the data,, the snapshot will store the old data in its file and new data will go the actual database.
so, when you create the database snapshot, the snapshot database FILE does not contain any data. as changes happen - the old data is moved to snapshot file and the new data goes to actual database file. it ineeds to keep the old data, so when you query
your database snapshot, it can give your prior data back.
if you want update lot of datas, i do not think snapshot will br good solution. it is good to test something quick and\or where there are less data changes. if you update all the data, your snapshot would end to similar size as the original database.
if this works, you can quickly generate another snapshot and drop the old one. every new snapshot as said, will start from 0 and grows in size as changes happen.
Also you database snapshots are like new databases, you should change your connection strings to point to the right snapshot.
Hope it Helps!!

Adding Availability Group to Existing SQL Server 2012 Enterprise installation

Looking at an existing SQL Server 2012 Enteprise vm. We'd like to add availability group functionality. It seems that we should be able to create a second VM and install SQL on it in an identical configuration. Then create a windows cluster with
the two nodes. From there we should be able to configure avaialbility groups.
I've set up avaialbility groups before but have not retrofitted one before. It seems possible though since the instances are standalone. Anyone see a problem with doing this?
thanks
Peter

Hello,
What you have is pretty much it. Since AGs require clustering but do not require a clustered install (stand alone install is used) there shouldn't be any changes with the actual install. You will have to enable the HADR option in the configuration manager
once the clustering is setup.
Sean Gallardy | Blog |
Twitter

Is it possible to move to Alwayson Availability groups from existing sql server FCI ?

Is it possible to move to Alwayson Availability groups from? existing sql server FCI ?
If yes, how to move and what are the pre-requisites?

Hi Rahul,
Based on your description, we need to verify if you want to move from Failover Cluster Instances(FCI) and database mirroring to SQL Server Alwayson Availability groups. If so, it is possible.
You can review the following articles to get more detailed information about this kind of migration.
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 1
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 2
Thanks,
Lydia Zhang

Change Tracking internals behave differently, SQL Server 2012 vs SQL Server 2008

<original post by Glenn Estrada>
Reposting an issue from Stack Overflow that a coworker and I are dealing with.
In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
I have been working thru Arshad
Ali's great walk thru example of how to set up a simple example.
I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
In 2008, the following statement returns a 0:
SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
In 2012, it returns a 1.
In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
is required:
IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
Has anyone else experienced this change in behavior? Does anyone have an explanation?

<original post by Glenn Estrada>
Reposting an issue from Stack Overflow that a coworker and I are dealing with.
In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
I have been working thru Arshad Ali's
great walk thru example of how to set up a simple example.
I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
In 2008, the following statement returns a 0:
SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
In 2012, it returns a 1.
In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
is required:
IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
Has anyone else experienced this change in behavior? Does anyone have an explanation?
sql-server sql sql-server-2012

How to Move the Shared Services Registry to a different SQL Server

I have an Essbase installation purely running Essbase and Financial Reporting/Web Analysis.
The Shared Services database is held in SQL Server 2005 on one hardware platform and I need to move it to an alternative hardware platform also running SQL 2005.
I thought it might be as easy as backing up from one server and restoring to the other and then running EPM System Configurator.
Firstly, when running configurator and selecting the Hyperion Foundation Configure Database option, on the 'Shared Services and Registry Database Configuration' screen the details of the original hardware are displayed, clicking 'Next' gets no response.
If I can resolve this first issue, how do I then re-point the database to the new server?
Any help would be appreciated.
Thanks.

Hi John
Took a look at the link thanks.
On point 3 it says to stop the original database. If you take the database offline, in configurator you don't then get the options in option 5!
In the dos command window for configurator I get 'Unknown Source' messages (either using current server or new).
configtool.log lists as follows. Does this point to anything?
Thanks.
(Sep 15, 2011, 03:26:47 PM), com.hyperion.hit.wizard.swing.ComboFieldSwingImpl, DEBUG, In ComboFieldSwingImpl.fieldChanged() method:,fld items: [Oracle, Microsoft SQL Server, IBM DB2], value: 1, selected idx: 1
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState$1, DEBUG, validate
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, connect test
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, driver set
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, server= aeSQL02.xxxxxxx-xxxxxx.com
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, whiteSpace remove
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, begin test cycle
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, define driver
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, make connection
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState, DEBUG, set URL
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.RegistryWizardState$1, DEBUG, connection is NOT null
(Sep 15, 2011, 03:26:50 PM), com.hyperion.config.wizard.impl.DBConnectionForm, DEBUG, DB type string = MSSQLServer
(Sep 15, 2011, 03:26:50 PM), com.hyperion.cis.config.Configurator, DEBUG, Loading DBConfigurator class for product: Foundation_1_9.5.0.0
(Sep 15, 2011, 03:26:51 PM), com.hyperion.cis.config.Configurator, ERROR, Error:
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at com.hyperion.cis.config.Configurator.loadProductDBConfigurators(Configurator.java:210)
     at com.hyperion.config.wizard.impl.RegistryWizardState$1.validate(RegistryWizardState.java:205)
     at com.hyperion.cis.config.wizard.adapter.WizardFormAdapterPanel.queryExit(WizardFormAdapterPanel.java:95)
     at com.installshield.wizard.awt.AWTWizardUI.doNext(Unknown Source)
     at com.installshield.wizard.awt.AWTWizardUI.actionPerformed(Unknown Source)
     at com.installshield.wizard.swing.SwingWizardUI.actionPerformed(SwingWizardUI.java:1693)
     at com.installshield.wizard.swing.SwingWizardUI$SwingNavigationController.notifyListeners(SwingWizardUI.java:1899)
     at com.installshield.wizard.swing.SwingWizardUI$SwingNavigationController.actionPerformed(SwingWizardUI.java:1894)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.NullPointerException
     at com.hyperion.foundation.config.FoundationDbConfigurator.isHubInstalled(FoundationDbConfigurator.java:133)
     at com.hyperion.foundation.config.FoundationDbConfigurator.<init>(FoundationDbConfigurator.java:38)
     ... 36 more

Moving only SP 2010 SSRS integration to a different SQL server

Fairly self-explanatory. I have a SP 2010 farm that is currently set up to use SQL Server 'A' in integrated mode for Reporting Services. I have a new SQL server 'B' (same ver) that is also set up in SP integrated mode for RS. I want to simply stop using
SSRS 'A' and start using SSRS 'B.'
I'm unclear how best to do this. Do I simply go into the Reporting Services Integration in Central Admin and enter the new information? Or do I choose 'add a server to the integration' to add server 'B' and then somehow drop server 'A'? Do I need to physically
migrate any databases?
This has nothing to do with any content or SP databases - I simply want to move the SSRS integration.

What i think, you have to manually migrate the reporting DBs to new server. then update the information into the Central admin.
Migrating SQL Reporting Services to a new server by moving the Reporting Services databases
Configure Report Server Integration in SharePoint Central Administration
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog
Turns out it is even easier than that. As long as the SQL Server has been prepped accordingly by:
Installing RS in SP integrated mode
Installing same version of SP on the SQL Server running RS
Joining the SQL RS Server to the existing SP farm
Then the solution is to simply re-run the Reporting Services Integration at General Application Settings > Reporting Services/Reporting Services Integration.
Make sure you perform the setup in the same authentication mode (Windows or Trusted Account) and it should work seamlessly.

How to move CR 2008 CMS database to a different SQL Server

I am trying to figure out how best to do this..all of the help articles discuss moving from XI to server 2008.. I already have 2008 running with a CMS database.. but I need to move the database to a new SQL box. I have looked at the import wizard and the database migration, but wasn't sure those were the right tools.
If anyone has done this... would appreciate some help. If it is as simple as changing the DSN on CR Server.. already hanging my head in shame..
To clarify.. I know how to restored the SQL database on the new server.. unclear how to make CR Server aware of the change
Edited by: Vicki Texeira on Aug 10, 2011 11:23 PM

Hi,
As i understand you want to change the cms database.
You can do this by going to
CCM>Select SIA>Stop SIA>Properties>Configuration>click the specify tab next toCMS System database configuration>update data sourse settings.
From there you can create a database using any connection.
let me know if this was helpfull.
Regards
Prithvi

Cannot connect to SQL SERVER with Always on availability group listener name

Hi everyone,
I have setup always an availability group listener for sql server on port 1433, have opened the port in firewall , remote connections are enabled in the sql server, but still I am not able to connect to the sqlserver instance with the help
of the availability group listener name.
I get the following error.
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:
TCP Provider, error: 0 - The wait operation timed out.)"} System.Exception {System.Data.SqlClient.SqlException
Have gone through several blogs for the solution but none of them helped.
Please let me know if anyone has fixed the issue.
Regards,
Divya

Prior to making SS connection, can you establish the connection with a networking tool?
SS connectiviy trouble shooting:
http://technet.microsoft.com/en-us/library/ms378845.aspx
http://stackoverflow.com/questions/5919524/not-able-to-telnet-sql-port-1433-locally-or-remotely
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/227f431a-4274-4d95-b605-67541d78ef03/test-sql-connection-with-telnet?forum=sqldataaccess
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server Always On

Hi we are using SQL 2012 Enterprise edition, I tried to click on the always on availability tab from the SQL Server management studio, but it gets an error message "Enable the option from SQL server configuration manager". I checked the instance
properties and found always on high availability option from there. It displays the following message
'This computer is not a node in a failover cluster' and the option was in disabled. Please help me on this how to resolve this issue.
Thanks

Hi Karj,
Please check the following link , sure it will helps to resolve your Issue.
http://msdn.microsoft.com/en-us/library/ff878259.aspx
http://sqlmag.com/sql-server-2012/microsoft-sql-server-2012-alwayson-availability-groups-feature
DBA

Setting Up Alerts for Always on Availability Groups Failover

Hi Folks,
In SQL Server 2008R2 we set up alerts for Mirroring failover using WMI Alerts. As Like this.
Now we need to configure similar alerts for Always on Availability Groups(AAG) in SQL Server 2012, but it seems that there is no such WMI Alerts or any standard way to set up the alerts for getting notified for AAG Failover. Click
Here
Should I manually Create a SQL Agent Job using
these DMVs and schedule it at frequent Interval to get notified about any AAG failover or is there any standard way as for mirroring Failover alerts? Any suggestion or help is appreciated.
Pranshul Gupta

Maybe you wanna have a look at this:
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-1.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-2.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/monitoring-alwayson-health-with-powershell-part-3.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/the-always-on-health-model-part-4.aspx
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Always on Availability on 2 different SQL Server clusters

Similar Messages

Maybe you are looking for