SQL Server 2014 Availability Groups

  • how does security works between availability groups.

    ex if i create an object and grant permissions to a user will that be replicated to secondary replica .

  • Yes, DB Users peice of security will be good. But keep in mind, you still have to deal with Logins at the Instance level in secondary replicas.

  • I use these scripts for my SQL users. If you read my post yesterday, Domain users do not need to have the sids matching. Just add the domain user(s) on the secondary and it will sync up. Also here is an article for your reading pleasure.

    http://support.microsoft.com/kb/918992

    I got these nifhty scripts off anothers DBA site and they work really well for me;

    -- Get Sids for all SQL Server logins on the old server instance

    SELECT name, [sid]

    FROM sys.server_principals

    WHERE [type] = 's';

    -- Create new SQL Login on new server instance

    IF EXISTS (SELECT * FROM sys.server_principals WHERE name = N'SQLAppUser')

    DROP LOGIN SQLAppUser;

    GO

    -- Use the sid from the old server instance

    CREATE LOGIN SQLAppUser WITH PASSWORD = N'YourStrongPassword#', sid = 0x2F5B769F543973419BCEF78DE9FC1A64,

    DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF;

    GO

    MCSE SQL Server 2012\2014\2016

  • thanks for your reply.

    How about an index, if i create a index on a large table consider 1 million records, it may take couple of hours to complete. What will happen on replica.

    Does index creation start at the same time?

    If it fails it will rollback on replica since we use sync mode.

    both primary/replica will be unavilable when this kind of operation goes right

  • indexes are sent over to the secondary database auto from the primary in AlwaysOn, replication it takes a little longer

    MCSE SQL Server 2012\2014\2016

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply