SQL Server AlwaysON- Login Sync Utility/Script

Team,
We have a synchronous Always ON AG configured in our environment. I was looking for the best practices to have the logins sync if there are any additions. Also the way the application is configured is they have the ability to perform the db additions and
sync them to AoAG group. However the challenge here is orphaned users.
Can we make these databases contained databases on AlwaysON? If so please do recommend the best practices.
Thanks for your assist.
Best Regards,
Sharath

Hi,
Hope it helps.
http://dba.stackexchange.com/questions/30036/how-to-link-users-and-logins-in-an-availability-group

Similar Messages

SharePoint 2013 and SQL Server AlwaysOn - HA

Hi guys,
Please help!
I need to setup SP13 server on SQL 2012 AlwaysOn (on sql01 and sql02). The HA AlwaysOn group already configured by DB team on these 2 replica with and called SP_AOAG alias
My question is can I use this alias to setup SharePoint or I need to configure the HA AlwaysOn group for SgharePoint as suggested in the article below:
http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx
Any advice greatly appreciated .
BalaiP

You do not want to use a SQL Alias with an AG Listener. Just point SharePoint straight at the AG Listener. You will need to manually add any accounts to non-primary instances. You do not need to add them to individual databases, of course. You will also
need to manually set MAXDOP to 1 on non-primary instances.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL Server AlwaysOn Failover threshold and Lease Timeout

Hi experts,
I found each time when I were building/restoring another log shipping(standby) server. It would cause ERR [RES] SQL Server Availability Group: [hadrag] Failure detected, diagnostics heartbeat is lost(in cluster log) and A connection timeout has occurred on a previously established connection to availability replica 'DL980-4' with id(in errorlog). I google and find a document (http://download.microsoft.com/download/0/F/B/0FBFAA46-2BFD-478F-8E56-7BF3C672DF9D/Troubleshooting%20SQL%20Server%20AlwaysOn.pdf ) indicated that “This may be a performance issue”. I run restore database and AlwaysOn synchronizing on the same 10GbE link at the same time.
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
Please refer to
(http://blogs.msdn.com/b/psssql/archive/2012/09/07/how-it-works-sql-server-alwayson-lease-timeout.aspx )
parag
10-18-2013 3:19 AM
Hi Denzil
we seem to see lease expires very frequently when the server is under very high cpu pressure .. our failure condition level is 1
is it possible to prevent this situation . the problem is when lease expires,all the current connections seem to be dropped . wondering if there is a way to prevent this ..
Also is it possible to affitinize the always on health check process to a particular core
Thanks for your help!

Hi Dennis
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
1. you can increase the timeout parameter, but when the fail-over time slight delay will be there (its a work around solution)
2. You may require to check the Network connections. (Cluster Heartbeat & public network)
3. Have you update the latest patches of OS & DB?
4. If possible raise the ticket to Microsoft. they may give some update for Cluster resource update based on your issue
Regards
Sriram

Alter IP address of SQL Server AlwaysOn Failover clustering Iistener

Hi,
Is there a possibility to change the IP address of SQL Server AlwaysOn Failover clustering Listener IP address without deleting the exiting one and also retaining the same DNS name.
NOTE: Only the IP address needs to be altered rest all (DNS, port) should remain the same.
Regards
Vijay

Hi Karthikkk,
As your description, you want to modify the listener IP address in AlwaysOn availability group without changing other settings including DNS and port. To achieve this, you could modify a listener IP address on primary replica using the following statement:
ALTER AVAILABILITY GROUP group_name
MODIFY LISTENER ‘dns_name’
ADD IP { (‘four_part_ipv4_address’, ‘four_part_ipv4_mask’) | (‘dns_nameipv6_address’) }
For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ff878601.aspx
Regards,
Michelle Li

About SCCM 2012 Primary sites sql server security logins

Hi, guys!
I've got some issue or some misunderstanding....In primary site's sql security logins there were same accounts as on CAS sql.....(We've got about ten primary servers)....two days ago someone (i'm going to find out that guy....damned...) from branch administrators
cleared up security list logins on one of primary server and left only two accounts....one of them it is primary site server installation account, second account - there is SCCM all hierarchy administrators group....
Most of that....that somebody got lower site server installation account role from sysadmin to public....
Am I right thinking in that way - all sql server security logins on all primary sites in one hierarchy must be identical....it explains by SQL replication.......?????
How can i get back sql security logins list on that sccm server to normal way....became after installing primary site server....??? need help......

Hi,
Primary sites do not always have the same security logins.
You need to add NT... accounts, sa etc into security logins. These accounts were added during SQL installation.
All site system computer accounts (such as MP, DP) and primary site computer account also need to be added.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Create a SQL Server authentication login

I am trying to create an SQL Server authentication login. using the documentation given http://azure.microsoft.com/en-gb/documentation/articles/sql-database-get-started/#QueryDBSysData
with the below sql statement
CREATE LOGIN login1 WITH password='Password1';
but gives an error
Msg 5001, Level 16, State 1, Line 1
User must be in the master database.
how do i get around this problem?

Hi roma_victa,
Please make sure that you issue the command in the master database of your logical server, otherwise it will fail.
Thanks,
Jan

Sql Server 2012 Login Failed for user "NT Authority\System"

I have installed SQL Server on a new server. I have been getting the following error on each of the database in it.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ABC'. [CLIENT: xxx.xxx.xxx.xxx]
Here is some information on the instance:
1) Default instance
2) SQL Server, Sql Server Agent, Sql Server Reporting services are running / log on using a domain service account.
3) Sql Server Browser is disabled.
4) SQL Server VSS Writer is running / log on as Local Service.
5) NT AUTHORITY\SYSTEM does exists in Login with just public server roles.
I ran a trace on login failed and I get:
ApplicationName: Microsoft Windows Script Host
and it runs every 15 minutes.
Help please?

Hi,
The error was thrown when the SCOM components connected to the backend SCOM databases.
You can specify a domain account, grant it the sysadmin role and the error should be gone.
Also, see the replies in your previous thread:
http://social.technet.microsoft.com/Forums/en-US/23f6b6cb-ec41-4117-8613-26d24c948827/login-failed-for-user-username-reason-failed-to-open-the-explicitly-specified-database
Thanks.
Tracy Cai
TechNet Community Support

Virtual Lab: Exploring SQL Server 2012 Integration Services - Setup script fails

I am trying to work through a Lab, but cannot get past the Setup script stage.
The lab is "Exploring SQL Server 2012 Integration Services". I have tried this several times (with new lab instances) and the result is always the same.
I double click the Setup command ... Press 2 ... when the popup dialog appears I press Ok ... the progress bar completes and the messages in the text box seem to indicate everything has completed (last line says "Done"). I click Close as per the
instructions and then the script moves to the "Configure SQL Server" stage.
After a short delay a number of error messages appear: "Could not open a connection ... Login / timeout expired" etc - basically it can't find or can't connect to the server.
I expected these labs to work seamlessly :)
Anyone know what's going wrong here?
Thanks,
Larry

I am moving it to SSIS.
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server Alwayson availability groups automation

Hi all,
I had configured SQL Server always on availability groups on windows server 2012 and it was successful.
I’ve installed and successfully configured our SQL Server 2012 AlwaysOn 2-node windows cluster servers. I've gotten AlwaysOn working great, and our
Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. As we know “we must manually find, select, back-up and then
add those new databases individually to get them into AlwaysOn."
But wait; that can be quite a task, constantly checking the SQL Server back-end servers to see what databases were created, then having to add them
into AlwaysOn, 7/24!
Im looking for an automated script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then
add those databases to Always On, all automatically.
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
Regards,
SQL LOVER.

awaiting for responses.
Kindly help the bewlo request.
Newly created database should be added into always on group and should be added to available
replica automatically with the TSQL script and perform restoration.
There is no out of the box solution for this. You may want to created a SQL Job (PowerShell) which can detect database which is newly created and perform steps to add new database to AG.
1. take full backup.
2. Take log backup.
3. restore then on secondary.
4. Add database to AG
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

Adding SQL Server AlwaysOn to existing Failover Clusters

Hello,
We use two seperate ms sql server 2012 clusters. We have two sites. All nodes are in same domain.
In the first site, NOD1 and NOD2 are in SITE A cluster group. (INSTANCE A) They have a shared SAN storage.
In the second site, NOD3 and NOD3 are SITE B cluster group. (INSTANCE B) They have a shared SAN storage too.
Can we use alwayson between two sites? If it is possible , how can we do it? and documents, web site etc.
Thank you.

Hi,
Windows cluster can straddle multi sites. If they are in the
same WSFC cluster, you can.
Please download the “AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups”
Word document from the following link.
http://msdn.microsoft.com/en-us/library/jj215886.aspx
Thanks.
Tracy Cai
TechNet Community Support

SQL Server Log: Login failed for user ''

We've found in SQL Server Log many records:
Date
3/22/2013 11:13:03 AM
Log
Windows NT (Application)
Source
MSSQLSERVER
Category
Logon
Event
3221243928
Computer
SBO05
Message
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
The server autentification is set to "SQL Server and Windows Autentification mode". But when we open SAP, before entering login/password, we see this message in log. But we still could work in SAP.
How could we solve this?
Kind regards,
Anna Shevchenko

Hi Joseph,
It doesn't help. The same things i've already done.
But when I change Mixed Autentification to Windows, i see another error:
Date
3/22/2013 11:04:26 AM
Log
SQL Server (Current - 3/22/2013 12:33:00 PM)
Source
Logon
Message
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.145]
Do you know why?
Kind regards,
Anna Shevchenko

SAP client requires re-connecting to SQL Server every login

Hi Experts
I have one PC where the user always has to enter the SQL server details every time they login.
Is there a reason this would happen? The client PC in question is running Vista.
Thanks
Greig

Hi Greig,
You mat check this thread first:
terminal server connection reset after each login to local server
Thanks,
Gordon

Installing SQL server AlwaysOn in hybrid solution

Hi,
I am trying to build a HA solution with SQL 2014 and AlwaysOn. My setup is 3 servers on prem and 1 server in Windows Azure with site-to-site VPN in between. My idea is to use the Azure replica as an async copy of some databases that resides on prem.
There is currently some guidence on the web how to setup this listener configuration using powershell and probe configuration. This works fine and the database on prem replicates to the secondary copy in Azure and the listener can do
a failover to the Azure replica. All great so far.
My question is now: How can I have a second Availability Group=Secondary listener configured between the same Machines?
Or is it a limitation to this setup, that you can only configure ONE listener to a SQL server within a cloud service in Azure?
I guess the limitation will be the same if both machines are located in Azure?
//Håkan

Yes. Only one availability group listener is supported per cloud service because the listener is configured to use the cloud service IP address.
Check this link:http://msdn.microsoft.com/en-us/library/azure/dn425027.aspx

SQL Server AlwaysOn- Service Restart Sequence

Team,
Most of our SQL databases are configured on AlwaysON Availability group. I was looking at best practices in restarting a SQL service. Ex: If we change any port details/windows patching etc.
I am particularly looking at the right sequence in which we restart the services.
All our databases are configured in Synchronous Failover mode.
Regards,
Sharath

In addition to what Sean has already mentioned, for asynchronous secondaries, you need to convert them to synchronous first and wait for the status to be synchronized before failing over to avoid data loss. Once all of the replicas have
been upgraded, switch it back to asynchronous. The process is outlined
here
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Connection Failed SQL State: 'HYT00' SQL Server Error: 0 [Microsoft] [ODBC SQL Server Driver] Login Timeout expired

I backed up my database   on old Notebook    SQLSTRINGCONNECT worked all day for any database in SQL SERVR I created
have brand new computer Notebook
installed SQL SERVER 2008 THE EXACT SAME WAY
I RESTORED THE DATABASE
However, I cannot connect to it via Visual FoxPro 9.0 with   SQLSTRINGCONNECT
or even Windows 7    ODBC Data Source ADministrator

Hi,
We need more information as Olaf asked, but my first guess is that you have permissions problem since the users are not the same users in different machines (local users, or SQL Server users),
even if they have the same name :-)
[Personal Site] [Blog] [Facebook]

SQL Server AlwaysON- Login Sync Utility/Script

Similar Messages

Maybe you are looking for