At its base, replication enables data and objects to be transferred from one database to another across different platforms and geographic locales. While configuring, administering, and optimizing a replication environment can be a daunting task, the goal of Pro SQL Server 2008 Replication is to break down the information needed accomplish these goals and fill in the gaps with real-world examples.
The primary audience for Pro SQL Server 2008 Replication is the database administrator who must plan and implement a replication environment. It is also for the developer who must deal with replication issues in their code. The book is 936 pages divided into 20 chapters. I am going to break it out into six functional sections and an add-on chapter. The book has no such sections, but that is how the book seems like it could be broken down.
Intro: Chapters 1-3 begins by explaining that there are two methods of distributing data in SQL Server. The focus of this book is on replication, but the author covers the other method - that of distributed transactions, and compares the differences between the two.
Next he goes on to talk about the details the Publisher-Subscriber model of replication, identifies the components of replication, and will give you a grasp of the fundamentals of the physical models of replication. Finally you will explore the three different types of replication and which situations in which you might consider using them.
Snapshot Replication: Chapters 4-7 involves the bulk copying of database objects from the Publisher to the Distributor server through the Snapshot Agent. This means that the data replicated is not done in real-time. Here you will learn to configure Snapshot Replication using the GUI method as well as using the Transact-SQL method.
Then you will examine the snapshots themselves. You will look at a lot of issues including where to put the snapshots, what kind of network you have, when the agent should be scheduled, and security considerations. Finally, you will look under the hood at Snapshot replication so as to better understand and interpret errors when they occur.
Article comments