SQL Server Always On Availability Groups

This is a recording of the Microsoft Canada TechDays TV episode I did on 20-Mar-2012. This video walks you thru converting your database mirroring and log shipping configurations to SQL Server Always On Availability Groups, providing database availability and maximizing your investments by allowing read-only access to database replicas

Download the Cluster Preparation Check list from here

[maxmax]

Thank you for the content! Now ready for my MCSE exam

[subhroleo]

Very nice presentation Edwin. Thanks for sharing the knowledge

[EdwinMSarmiento]

This depends on what the status of the primary is after going back online. If the primary was down for a long period of time, for example due to maintenance or hardware failure, you need to re-initialize the database to catch up with the latest version of the database. If the primary immediately got back online, it can resync back with the new primary. The concept is similar with database mirroring.

[swatantrarattan]

Thanks so much for sharing Brilliant video and so much

[EdwinMSarmiento]

Hi Belay,

You can try downloading it from the link provided

Note that you need the .NET Framework 4.0 and the SQL Server 11.0 Native Client on your workstation to use the Application Intent=ReadOnly parameter on your connection string

[EdwinMSarmiento]

If the primary goes down, the replica will act as the new primary since you are now running on top of Windows Failover Cluster: this takes care of the failover. The listener will also move to the new primary. Think of this as database mirroring plus clustering

[DrumCodeLive]

HI,

Just watched your session on high availability, that's a great work put in simple terms, thanks a lot for sharing your knowledge.

I have a question on designing a high availability architecture.

We currently have a set of OLTP databases serving for the application usage and these databases  are being replicated (transactional, every 3 min) to another box for reporting purposes, I'm thinking of replacing replication with High availability groups (asynchronous) (one of the reasons to bring high availability groups in to picture is to have HA during database corruption (ex: page level corruption))

Q: as the indexing on report databases is different to indexing on application dB’s, the failover between app db and reporting db will not provide better performance to application or reports at the time of failover, this makes it a bit hard to design a cost effective, low downtime cluster.

Please let me know if you can suggest a better solution for this situation.

Appreciate your help.

Cheers,
Kiran

[jaspenle]

Nice Job Edwin - I'm sure you're aware of this, but you can have mirrors with snapshots to help maximize resources on the secondary.

question... With HAG, using the listener to redirect after a failover... what happens if the primary goes down and won't come back up - like a true disaster - can you run "fail-over" on the secondary instance and it too will update the listener?

[adha]

Nice presentation. I do have a question. How does the primary instance get back in sync on a fail over to a secondary instance? Does the secondary sync it back up automatically once the primary is back online?

[rowervem]

Hi, Great Video. What if those 2 servers are on 2 separate subnets? Then which IP address of which subnet should we put there ?

[sukumarseetharaman]

It is good One and is it possible to have one listner and one AG group for two different SQl instance on four node cluster.

[olufemisonuga]

Great Video - Can you please send me the scripts you used for disabling please 

[kasperskyns]

If a have webiste that use sql server name to connect to sql and database name. Should I put listener name instead of servername and then the name of the database?

[farel]

hi, for the windows failover cluster did you create a random IP address? thanks

[yahyaibniliyas]

video quality (visibility) is poor, what am i doing wrong. i can see all other videos nicely