database replication / publication ?

Hi,
I'd like to keep an extra copy for database X on SQL server A to SQL server
B. The database X doesn't update very often during the day (but the computer
does have other jobs to run at tthe work hour). Both server A and B run SQL
server 2000 and on the same network. Currently the size of database X's MDF
and LDF are around 6 GB (3GB each). It would be nice to keep database X
always be in sync with its copy, but it is not a must. If the database
replication/publication takes a lot of CPU or is time comsuing, it is OK to
do it with a nightly job.
What is the good practice in the case? Thanks for sharing your thoughts.
Shawn,
for an extra copy of X on a standby server, and where latency is allowed,
I'd consider using Log Shipping. This article helps explain some of the key
differences: http://www.replicationanswers.com/Standby.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)