- [Instructor] In general when we speak…of relational databases scaling out reads…is a lot easier than scaling out writes,…we can really only write to one server.…But we can read from many.…One of the more common traditional approaches…from SQL Server is to use transactional replication,…transactional replication as a feature…has a large number of overheads,…and has in general a poor administration experience.…Availability groups offer a less cumbersome approach.…It's simply creating those replicates which are just…a restored copy of your original production database…and transactional replication has another challenge.…
It does not offer a native way to route application traffic…to your replicated copies of the data.…One thing I'll mention here before I show a code demo,…is that your client software needs to be on SQL Server 2012…or higher as I record this in 2018 I hope you're there.…But if you're not you need to get there.…So in order to configure your availability group…to support read-only routing, you're going to use those TSQLs,…
Released
11/12/2018- Designing for high-write and high-read workloads
- Designing an archiving model
- Leveraging SQL features such as portioning and compression
- Building a tenancy model
- Using Azure design patterns for scaling
Share this video
Embed this video
Video: Always On availability groups: Read-only routing