SQL Server 2000 Replication 101: Terminology, Types, and Configuration
It's wise to make sure you have a clear understanding of replication terminology, types of replication, and exactly what is occurring when you install and configure replication.
by Ron Talmage
November 26, 2003
eplication figures as one of the more prominent features of SQL Server 2000. Replication is a complex application that uses a combination of stored procedures and executables to distribute and copy data between SQL Server databases. If you take care not to get lost in the details and confused by occasionally misleading terms, replication can be an important component in the database architecture of a SQL Server application. In this article, you'll learn about the terminology surrounding replication, the types of replication available in SQL Server, and how to configure (that is, install) replication.
Replication can provide you with some interesting solutions for your data tier architecture because it allows you to use multiple database servers on the back end. You can publish to multiple servers, gather data from multiple servers, provide loosely connected clients with the ability to share data with a centralized database, and scale out database work in a horizontal fashion.
Let's take a look at replication terminology, then the types of replication, and finally with the steps required to configure replication.
Getting clear on terminology is one of the most important hurdles to overcome when diving into SQL Server replication.
Replication Terminology
Getting clear on terminology is one of the most important hurdles to overcome when diving into SQL Server replication, so in this section you'll learn about the basic terms and concepts.
The purpose of SQL Server replication is to copy or distribute a database's data to one or more data sources, usually other SQL Server databases. The destination database(s) could be on the same SQL Server, but most commonly you'll want to get the data from one SQL Server to another SQL Server.
Do the advantages of P2P technology mentioned here strike you as logical next steps in information science? Or are these just theoretical pipe dreams that won't work in practice? Tell us what you think in the talk.editors.devx discussion group.
Forget file sharing. The industry is missing the true value of peer-to-peer technology and developers and consumers are the ones who are paying the price.
by Bradley S. O'Hearne
December 4, 2002
s a big fan of atmosphere and thematic environment, I queued up the "Blade Runner" Soundtrack on my computer. Vangelis' ghostly ambience, like the subject of this editorial, is futuristic in nature, but more importantly, the source of my audio bliss is the MP3 file format (produced from my own purchased copy of the CD, if anyone from the Recording Industry Association of America (RIAA) is reading).
Peer-to-peer (P2P) technologythe advancement which vilified MP3s and the concept of digital file sharinghas created a hubbub over the past couple of years, but the legal thunderstorm that ensued rained on the technology parade. Bring up the phrase "peer-to-peer," and the conversation undoubtedly will turn to copyright law, the Digital Millenium Copyright Act (DMCA), and the demise of Napster. But this isn't the fault of the RIAA, the Motion Picture Association (MPAA), or any specific lawsuit or legislation. The culpability is oursthe tech communityfor not seeing the forest for the trees.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!