March 27, 2012 at 10:47 am
Anyone running SQL 2012 in production and leveraing AlwaysOn?
I've been using SQL 2008 R2 and using SQL Async mirroring. All knowing how the logins have to be created on each instance (and kept in sync) on each mirrored instance, does AlwaysOn handle the SQL logins?
If anyone has any information, let me know.
April 4, 2012 at 7:46 am
If you are using contained databases, then users in the database are kept in sync including their logins. Logins that do not map to a database user will not be kept in sync (for example, users that have access due to server level permissions like sysadmin members). Even with contained databases, you will need to do some syncing of logins.
I have a script you can use for that: http://www.sqlsoldier.com/wp/sqlserver/transferring-logins-to-a-database-mirror
That script was written specifically for mirroring, but people use it for log shipping, AlwaysOn, and any other situation where they need to sync logins.
April 4, 2012 at 9:00 am
I am just getting up to speed in bits and pieces on SQL 2012. From Introducing SQL Server 2012 AlwaysOn Failover Clustering by Jonathan Kehayias instance-level impacts can be tracked at the database level using sys.dm_db_uncontained_entities.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply