Replication/Admin Help

We run a small business with a LAN of 2 pcs, a laptop pc, and a web server that runs Win2k Server with Exchange on it. My pc is used for most of the development and it also houses SQL Server (Developer) 2k. We have SQL Server (Developer) installed on the other network pc as well.

Here's the problem: We sometimes have to take my pc with us to use at different sites (with no internet connectivity at the time). When this happens, any data access on our web site is 'down' because our web data is in the sql server db on my machine. I want to replicate the db on the other pc so that we can take that machine to the different sites. I am having trouble getting this done.

Can someone give me some direction? Is there a good tutorial or a book or whatever somewhere? I am really in need of some sql server admin knowledgebase.

Thanks!!

MSsql server?

Yes!

It's actually one of the easiest things to do.

I've only used Microsoft SQL Server 2000, but it provides several methods for implementing and administering replication

Enterprise Manager actually includes a graphical organization of replication objects, several wizards, and dialog boxes you can use to simplify the configuration and administration of replication.

The easiest way is to right click on the db itself if i remember quickly and run through the wizard of setting it up... it's really that simple.

You can make it a batch job and set it to do it every so often, or you can do what you're looking for and what it does is makes a script for each table i think, and everytime there's a change it updates the DR box. FYI, I've been running into problems with databases that grow to be over 1gb, all the scripts get jumbled and replication just quits, had to switch over to designing a transfer DTS package and just running it at certain intervals. You'd just need to run the DTS package (you can force them to run, just go to the DTS section) and run it before unplugging then set your websites to point to the DR box which it sounds like you already have set up.

A wiser choice would to just have a dedicated webserver and a dedicated SQL server, but with the way money is i can understand how it's tight these days...