Automatically add a Database to an Availability Group

Dears, I need to know if there any way to configure SQL always on to automatically add new Databases to an Availability Group.
Ayman Saleh

Hi can any one update the TSQL script here:
Requirements:
Every time the newly created or added databases should be full backed up once in the shared location with
automated script.
Newly created database should be added into always on group and should be added to available replica automatically
with the TSQL script

Similar Messages

How can you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

If you use the WCF-SQL adapter it is recommend that you set UseAmbientTransaction to true if you are changing data. I think this requires MSDTC to be enabled on the SQL server that you are changing the data on. (http://msdn.microsoft.com/en-us/library/dd787981.aspx)
I think that Availability groups does not support MSDTC. (http://msdn.microsoft.com/en-us/library/ms366279.aspx).
How can you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

Hi,
Yes, Availability groups doesn't support MSDTC. Please refer to the similar discusison which maybe helpfull:
http://dba.stackexchange.com/questions/47108/alwayson-ag-dtc-with-failover
http://stackoverflow.com/questions/17179221/msdtc-in-always-on-availability-groups

Maintenance plan for SQL Server 2012 Database in AlwaysOn Availability Group

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Thank you very much for your help!
Jake

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Regular maintenance plan would work. Only thing to remember is that when you create log backup plan, there is a checkbox which says whether it should honor backup preference or not.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Availability groups and full-text indexes.

Hello,
I have created an availability group that contains a database. The database is working fine.
I get a request to create a full-text catalog and to add full-text indexes.
Is it possible to create full-text indexes on databases that have a primary replica and a number of secondary replicas?
Best regards,
Erik

Hi hcv,
Microsoft will support full-text search in a clustered environment in SQL Server, so you can create full-text indexes on databases which are in Always on environment. In
the AlwaysOn Availability Groups, two types of availability replicas exist: a single
primary and some secondary replicas. To add a database to an availability group, the corresponding secondary database will exist until backups of the new primary database are restored to the server instance that hosts the secondary replica (using
RESTORE WITH NORECOVERY). You can refer to
back up and restore Full-Text catalogs and indexes.
There is an article about Full-Text Indexing in SQL Server, you can review them.
https://www.simple-talk.com/sql/learn-sql-server/understanding-full-text-indexing-in-sql-server/
http://technet.microsoft.com/zh-cn/library/aa214780(v=sql.80).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Add users to databases in Availability Groups

Hello,
I created a database.
On instance level I selected Security | Logins and added some users.
I granted the users a number of roles on the database I created.
I added the database to an Availability group. Now two replicas of the database are on two servers.
When I look on the server that is running the secondary replica the users have not been added to the users on instance level. Is that going to work fine after a failover?
Should I add the users to the Instance(s) of other cluster members before I restore the database? That would make sense.
I cannot find any documents that tell me about creating users in databases that have been added to an availability group.
Best regards,
Erik

Thanks for you answer.
I used sp_help_revlogin to script out the logins the applications and users need to connect to the database, including their SIDs, and executed it on the secondary replicas servers
so that it is available.
I have done that before I restored the database on the secondary replica servers.
I guess I have to run sp_help_revlogin every time I add a user on the primary server.
Best regards,
Erik
If it is a windows login, it will have the same SID across the domain so no need to run sp_help_rev_login, you can directly create the login in the secondary and the mapping is taken care itself with the database user. If you are creating SQL Logins
you need to script it out using sp_help_rev_login for the secondary server.
If you are willing to automate this activity, Please explore " ssis package to transfer logins" and try to customize it to your need and schedule it as a job.
http://technet.microsoft.com/en-us/library/ms137870.aspx
Thanks

Sql always on full sync when creating availability group

hi,
i am creating AOAG in SQL 2012 and i am a little confused as to how the sync is created. when you setup the avail group the options you have are full, join and something else. We are doing the full.
i have a database that's 700gb in size so i did a backup to meet the pre reqs of creating the aoag. i then started the process and it shows a list of tasks its performing. once of the tasks is backing up the db before it syncs.
if i look at the backup it shows a size of 217GB. why do i have a difference in the size. does it do something different while creating the AOAG?
Thanks
phill

Hi phillbl,
According to your description, the backup operation copies the data in the database to the backup file. The backup contains only the actual data in the database and not any unused space. Therefore, the backup is usually smaller than the database itself.
Usually, in SQL Server AlwaysOn Availabity Group Wizards, you can use
Select Initial Data Synchronization page to specify a network share in order to create and access backups, then synchronize full initial data with secondary database.
If you are unable to use the wizard to perform full initial data synchronization ,you need to manually prepare a Secondary database for an Availability Group , as other post, you should manually restore a recent database backup of the primary
database using RESTORE WITH NORECOVERY, and then restore each subsequent log backup using RESTORE WITH NORECOVERY.
For more information, see:
http://msdn.microsoft.com/en-us/library/hh403415.aspx
Back Up and Restore of SQL Server Databases:
http://msdn.microsoft.com/en-us/library/ms187048.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

How do i add a database?

My add a database + is not available.
I set up a site, document type and testing server with every combination I can think of. And I reinstalled dreamweaver numerous times?
Any suggestion?

I know this is possible, I have used mssql and oracle with php using pdo.
But to use the MySQL db with asp.net & DW you require the driver to do so.
Have you installed the ODBC driver for MySQL?
Link to download:-
http://dev.mysql.com/downloads/connector/net/5.0.html
Documentation at - http://dev.mysql.com/doc/refman/5.0/en/connector-net.html
Here is example code to connect:
must declare the namespace:
using MySql.Data.MySqlClient; // Add the MySql.Data.dll in the bin folder of the wwwroot folder
conn = new MySqlConnection("server=localhost;user id=root; password=root; database=test;persist security info=True");
        string strSql = "Select id ,name from abc";
        MySqlCommand cmd = new MySqlCommand(strSql, conn);
        conn.Open();
PZ

Initermittent Connection Timeout at Post-Login when connect to AlwaysOn Availability Group listener

Hi,
I'm using SQL 2014 AlwaysOn Availability Group and my ASP .Net application is connected to the database thru the availability group listener (tcp:[myHAGroup],14330).
Things work most of the time, but recently I started to see the following Connection Timeout exception in Event Log. It looks like under heavy traffic the application can't connect to the availability group listener.
Timestamp: 8/17/2014 10:07:28 AM
Message: System.Data.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=2; handshake=0; [Login] initialization=0; authentication=0; [Post-Login] complete=15008; ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---
I've checked SQL Profiler and don't see any memory or CPU peak at that time. Looks like somethings happened during the Post-Login stage, but I couldn't figure out what or why....
I'm using 2 SQL servers (1 primary, 1 secondary): SQL 2014 ENT, 8GB RAM, 8 core 2.67 Xeon X5650.
Application: ASP .Net, framework 4.0.
All servers are VMWare virtualization servers, running on 1 virtual switch, so internal traffic should not be a problem.
Comments/ideas are appreciated.
Eric.

Hi Eric Nguyen,
According to your description and error message, we need to verify if there are some queries/transaction lock your database via SQL trace. If yes,
you have to find out which queries are blocking and rewrite them/run them at other time to avoid blocking other processes.
In addition, you can use performance monitor to track connection pool connections. If you set default connection limit and timeout limit with a small number, the error of “wait operation timed out” will occur. Meanwhile, you also need to monitor disk usage
on SQL Server , and set the auto increment size of your transaction log and database with a fixed size instead of a percentage of the current files due to avoid transaction timeout. For more information, see:
http://stackoverflow.com/questions/7743725/how-to-troubleshoot-intermittent-sql-timeout-errors
There is an similar issue about connection failed from webservers to SQL Server AlwaysOn Listener, you can review it.
http://stackoverflow.com/questions/23416492/connection-timeouts-when-using-multisubnetfailover-true
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Availability group Automatic failover

Hi
setup a simple 2 node AG, sync. (SQL 2014 enterprise on windows 2012R2 standard)
if I set it as manual failover everything works as expected. however when I switch to automatic failover and stop SQL service on the primary node the AG resource in cluster does offline and doesn't failover to secondary node.
both nodes are available to the cluster resourse.
would appreciate your feedback as to what might be the reason
Regards
Shaunt

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Database Availability Group Missing on 2 Exchange Servers

I have a an existing Exchange 2007 setup and installed 2 Exchange 2013 servers that have the Mailbox and CAS role. When I go to the ECP menu and click on databases there is no option available to create the DAG.

I Don't think that the Exchange 2013 installation is successful. If it successful then it might have been a problem with RBAC Roles which were not delegated properly to the account you are using to logon to ECP.
Try below and check if you are able to create DAG.
1. Create a New User and make it a member of Organization Management, Enterprise admins, Domain Admins, Schema Admins,
Built-in Administrators, Group policy Creator Owners and run the command below on the powershell: Set-User NewUser -RemotePowershellEnabled:$True
2. Logoff and Login Back using the Newly create account and check if you are able to see the option to Create DAG.
IF you are not able to then Open Windows Powershell as administrator and run the commands below
Add-Pssnapin *Setup
Install-CannedRBACRoleAssignments -InvocationMode Install
Install-CannedRBACRoles
Install-CannedRBACRoleAssignmentsRAP
Install-CannedAddressLists
Lastly, i would also ask you to get the output of the command below:
Get-ManagementRoleAssignment -Role "Database Availability Groups" -RoleAssignee OriginalUserWhoDontHaveCreateDagOptiononECP
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Cannot re-add SQL database to protection group

Hello,
I have a situation where my BES database was inconsistent in DPM 2012 SP1. I removed the DB from my SQL protect group and deleted the replica data from the server. When I try to re-add it back to the protection group, I am unable to see the DB in the list
of DBs on the instance.
BES DB is mirrored (no FS Witness)
Principal is 2008 R2 SP1 Cluster
Mirror is 2008 R2 SP1 Server (No Cluster)
DPM Server is DPM 2012 SP1, version 4.1.3417.0
Protection Group is Auto-Protection enabled
I have stopped protection on the entire SQL Cluster (keeping data), recreating the Protection Group. I have also disabled and re-enabled Auto-Protection. No dice.
Any ideas?
Shawn

Hi,
What was the original casuse of the inconsistency to begin with - that may hold a clue why we cannot re-protect ?
Please make sure the mirroring role has not been switched.
Any mirrored database will be listed on the principal server only and can be selected there for protection.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

SQL server 2012 - Database Availability Group

We have 2 new Servers ready to be deployed as Database Servers for Sharepoint 2013.
both server have 1TB RAID 5 Hard Disk Space.
We don't have any kind of Shared Storage/SAN etc & we cannot afford to buy this.
I have Configured Windows Server Fail-over Cluster with File Share Quorum.
May i Configure the SQL Database 2012 on Each Server on local disk and then make High Availability Groups?

As well as the youtube video that Edwin has posted for you have a read of my article on SimpleTalk.com.
https://www.simple-talk.com/sql/database-administration/sql-server-2012-alwayson/
This takes you through the step by step process.
HTH
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

OFS add standalone database to group error

I was installing OFS 3.3.3 with Oracle 10g R2 on 2 win2k3sp1 servers. The standalone database instance could be startup at each node respectively without any issue.
The standalone database verification ran successfully. (I failover the data files to the second node, and verify that I can start and connect the same database instance, maybe I missed any configuration in registry or somewhere on node2?)
But when I tried to add the resource to the cluster group, I got following error:
Versions: client = 3.3.3 server = 3.3.3 OS =
Operation: Adding resource "OLTP.WORLD" to group "OLTP"
Starting Time: Dec 10, 2006 22:02:09
Elapsed Time: 0 minutes, 25 seconds
1 22:02:09 Starting clusterwide operation
2 22:02:10 FS-10370: Adding the resource OLTP.WORLD to group OLTP
3 22:02:10 FS-10371: ORAFS01 : Performing initialization processing
4 22:02:11 FS-10371: ORAFS02 : Performing initialization processing
5 22:02:14 FS-10372: ORAFS01 : Gathering resource owner information
6 22:02:14 FS-10372: ORAFS02 : Gathering resource owner information
7 22:02:14 FS-10373: ORAFS01 : Determining owner node of resource OLTP.WORLD
8 22:02:14 FS-10374: ORAFS01 : Gathering cluster information needed to perform the specified operation
9 22:02:14 FS-10374: ORAFS02 : Gathering cluster information needed to perform the specified operation
10 22:02:14 FS-10375: ORAFS01 : Analyzing cluster information needed to perform the specified operation
11 22:02:15 >>> FS-10652: ORAFS01 has Oracle Database version 10.2.0 installed in ORADB10G_HOME1
12 22:02:15 >>> FS-10652: ORAFS02 has Oracle Database version 10.2.0 installed in ORADB10G_HOME1
13 22:02:15 FS-10376: ORAFS01 : Starting configuration of resource OLTP.WORLD
14 22:02:15 FS-10378: ORAFS01 : Preparing for configuration of resource OLTP.WORLD
15 22:02:15 FS-10380: ORAFS01 : Configuring virtual server information for resource OLTP.WORLD
16 22:02:15 > FS-10496: Generating the Oracle Net migration plan for OLTP.WORLD
17 22:02:16 > FS-10490: Configuring the Oracle Net listener for OLTP.WORLD
18 22:02:16 >> FS-10600: Oracle Net configuration file updated: D:\ORACLE\PRODUCT\10.2.0\DB_1\NETWORK\ADMIN\LISTENER.ORA
19 22:02:16 >> FS-10606: Listener configuration updated in database parameter file: m:\spfileoltp.ora
20 22:02:20 >> FS-10605: Oracle Net listener Fsloltpd created
21 22:02:21 >> FS-10602: Oracle Net listener LISTENER restarted
22 22:02:21 > FS-10491: Configuring the Oracle Net service name for OLTP.WORLD
23 22:02:21 >> FS-10600: Oracle Net configuration file updated: D:\ORACLE\PRODUCT\10.2.0\DB_1\NETWORK\ADMIN\TNSNAMES.ORA
24 22:02:21 FS-10381: ORAFS01 : Creating the resource information for resource OLTP.WORLD
25 22:02:21 > FS-10424: Checking whether the database OLTP.WORLD is online
26 22:02:31 ** ERROR : ORA-01506: missing or illegal database name
27 22:02:31 ** ERROR : FS-10778: The Oracle Database resource provider failed to configure the cluster resource OLTP.WORLD
28 22:02:31 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
29 22:02:31 ** ERROR : FS-10497: Starting clusterwide rollback of the operation30 22:02:31 FS-10488: ORAFS01 : Starting rollback of operation31 22:02:31 > FS-10090: Rolling back Oracle Net changes on node ORAFS01
32 22:02:34 FS-10489: ORAFS01 : Completed rollback of operation
33 22:02:34 ** ERROR : FS-10495: Clusterwide rollback of the operation has been completed
34 22:02:34 Please check your Windows Application log using the Event Viewer for any additional errors
35 22:02:34 The clusterwide operation failed !
The DB_NAME is already stated in the spfile, but why still got "ORA-01506: missing or illegal database name" error?
How and where can I find out any other detailed information about the error?
thanks, ezlee

Hi,
Did you manage to get past this error?
Did you set DB_NAME in the init.ora file as per the message for ORA-01506?
Regards,
Ranjit

Move database while in AlwaysOn availability group

Hee Guys I have a question and I try to find answer on the internet but I could find it. I have a database that is in a Availability group. There is constantly data written in the database. I really want to move it to a new disk. I am working with a SQL
2012 enterprise edition. Is there a way to move the database on both servers without losing data?
I was thinking of de-attaching and attaching it but that is not allowed while in the availability group. When I take it out of the group and move it to the new disk on the secondary server, then I cannot put it back in an availability group because the path
is not the same. Can somebody tell me how to do this in the right way.
Any help is appreciated!

I did some testing. What I am missing in the script is to kill transactions and processes. On one database I got the following exception:
--MOVE FILES
xp_cmdshell 'move "F:\Database\DBName1*.*" M:\Database\' -- Change values
go
F:\Database\DBName1.ldf
The process cannot access the file because it is being used by another process.
0 file(s) moved.
NULL
On the another database I got something the same:
GO
ALTER DATABASE [DBName2] SET ONLINE -- Change values
GO
File activation failure. The physical file name "E:\Database\DBName2.ldf" may be incorrect.
The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to
a hardware or environment failure.
Msg 5181, Level 16, State 5, Line 2
Could not restart database "DBName2". Reverting to the previous status.
Msg 5069, Level 16, State 1, Line 2
ALTER DATABASE statement failed.
What is the best way to go around this? I tried to use EXEC sp_who2 and Kill but there are no processes for these database. I also looked in the resource monitor to see if there are files in used but this is also not the case.

Automatically add a Database to an Availability Group

Similar Messages

Maybe you are looking for