Review from similar course:
"The trainer has a nice clear voice and the most important is that he does not rush through the subject, which is the problem with many instructors. By speaking slowly and displaying every step, it saves us time by not having to replay every section over and over, thanks for this." - Andres
Welcome to SQL Server Replication in the Real World.
In this course, you’ll learn how to correctly configure the three replication topologies specific to SQL Server.
Replication is a way of distributing data automatically from a source database to one or more destination databases.
In this course, we are going to cover three core topologies.
They are, Snapshot Replication, Transactional Replication and Merge Replication.
It has also been used to for high availability solution but that’s not recommend.
Replication is for continuous data transfer and is not used for simply copying data.
The two most common real world applications for replication are reporting and data warehousing.
I’ve also seen it used for off-loading nightly batch processing tasks.
Replication uses a Magazine Publishing vocabulary. Anything from an article to an entire database can be replicated.
In the course, we are going to cover all the nomenclature, architecture and real world tips and tricks you’ll need to keep replication functioning without issue.
Thanks for your interest in SQL Server Replication in the Real World. We will see you in the course!!!
What are we going to learn in this course?
This video outlines our course goals.
In this lecture let's talk about why you might want to use replication.
There are some very good use cases for SQL Server Replication.
In this lesson let's learn how we decide which topology to use for any given business use case.
In this lecture let's discuss the basics of the replication architecture model.
The replication topology isn't complicated but it does have a lot of new vernacular if you're new to SQL Server.
In this lecture let's look at how the distributor and subscriber work.
In this lecture let's' the discuss the agents used in the replication process.
In this lecture let's install an instance of SQL Server with replication.
We are also going to add replication to an existing instance that doesn't have it installed.
In this lecture let's learn the nomenclature behind replication.
This is where you'll download the code for the course.
There are only three code segments for this course.
Let's go over the key ideas we learned in this section.
There were a lot of new terms so it might be a good idea to watch this section more than once.
In this lecture let's define what snapshot replication is.
It's the least used but the easiest to set up.
In this lecture let's script out the snapshot process.
We can actually script out the entire replication process and save the files in case replication fails.
In this lecture let's walk through the steps to setting up Snapshot replication.
We do encounter two failures that we remedy.
In this lecture let's look at the jobs associated with the snapshot agent.
The distributor plays a crucial role in the replication process.
Let's learn what it does in this lecture.
What is transactional replication?
Let's find out in this video.
In this lecture let's demonstrate how to set up transactional replication.
In this lecture let's define what Merge Replication is.
In this lesson let's learn how to set up Merge Replication.
In this lesson let's go over the jobs created when we set up transactional replication.
In this video let's test our set up to see if we can indeed merge data from two different databases on two separate instances.
It's not one of the prettiest tools in the world but it does give us critical insight into the health of replication.
In this lecture we delete transactional replication.
We do run into a little snag we have to correct.
In this lesson let's filter row by specifying a where clause from within the replication wizard.
In this lecture let's remove two columns from the synchronization of the article.
In this lecture let's fix an out of control distribution database.
Basically the cleanup job internally calls sp_MSdelete_publisherdb_trans to remove records from the MSrepl_commandstable. If a publication has "immediate_sync" set to 1 in the MSpublications table, then the MSrepl_commands records will not be removed until the commands are older than the max retention setting (3 days by default).
Let's fix this issue.
I've been a production SQL Server DBA most of my career.
I've worked with databases for over two decades. I've worked for or consulted with over 50 different companies as a full time employee or consultant. Fortune 500 as well as several small to mid-size companies. Some include: Georgia Pacific, SunTrust, Reed Construction Data, Building Systems Design, NetCertainty, The Home Shopping Network, SwingVote, Atlanta Gas and Light and Northrup Grumman.
Experience, education and passion
I learn something almost every day. I work with insanely smart people. I'm a voracious learner of all things SQL Server and I'm passionate about sharing what I've learned. My area of concentration is performance tuning. SQL Server is like an exotic sports car, it will run just fine in anyone's hands but put it in the hands of skilled tuner and it will perform like a race car.
Certifications are like college degrees, they are a great starting points to begin learning. I'm a Microsoft Certified Database Administrator (MCDBA), Microsoft Certified System Engineer (MCSE) and Microsoft Certified Trainer (MCT).
Born in Ohio, raised and educated in Pennsylvania, I currently reside in Atlanta with my wife and two children.