Professional SQL Server™ 2005 Programming

Chapter 20. Replication

Replication is one of those areas of big change for SQL Server 2005. If you're new to it, well...you had some adjusting to do to understand replication anyway, but I want to caution those of you who already know replication from SQL Server 2000 and prior that some fairly core things — particularly in the area of replication security — have changed, so listen up and pay attention!

Okay, okay — enough with the drill sergeant act. I'm going to guess that most of you reading this chapter are actually fairly new to replication. You see, replication is one of those things that everyone loves to ignore — until they need it. Then, it seems, there is a sudden crisis about learning and implementing it instantly (and not necessarily in that order I'm sorry to say).

So, what then, exactly, is replication? I'll shy entirely away from the Webster's definition of it and go to my own definition:

NOTE

Replication is the process of taking one or more databases and systematically providing a rule based copy mechanism for that data to and potentially also from a different database.

Replication is often a topology and administration question. As such, many developers have a habit of ignoring it — bad idea. Replication has importance to software architects in a rather big way, as it can be a solution to many complex load and data distribution issues such as:

• Making data available to clients that are generally not connected to your main network

• Distributing the load associated ...