Is Replication the solution?

We have serveral office of which have there own SQL Databases running in
MSDE and SQL Server Enterprise running at the Corp HQ. At HQ there are
tables for say Office 1 (Ofc1) in a central database. The central database
has a shema for each office in the central database ie ofc1.tbl_contacts,
ofc2.tbl_contacts, etc... Not all of the fields residing on the office
servers will be replacated to the HQ central db. But
updates/additions/deletions need to be synched at least on a daily basis.
I have already writting some of my own jobs to handle this with stored
procedures. I have createdDate, modifiedDate(updated via trigger) fields
that are used to determine what data needs to be transferred. I
I was wondering if SQL Replication Services would be a help in this area?
Is there some other method that would be better suited for this task, or is
coding it by hand (which I already started) pretty much the better solution?
Thanks for the help,
--Micah
Replication is ideal for something like this. You don't really mention is
data is going both ways or only to the branch offices.
If it is one way you should be using transactional replication with filters;
if it is bi-directional you should be using merge replication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Micah Miller" <micah.miller@.privacy.me> wrote in message
news:OQyEUPXtEHA.3884@.TK2MSFTNGP11.phx.gbl...
> We have serveral office of which have there own SQL Databases running in
> MSDE and SQL Server Enterprise running at the Corp HQ. At HQ there are
> tables for say Office 1 (Ofc1) in a central database. The central
database
> has a shema for each office in the central database ie ofc1.tbl_contacts,
> ofc2.tbl_contacts, etc... Not all of the fields residing on the office
> servers will be replacated to the HQ central db. But
> updates/additions/deletions need to be synched at least on a daily basis.
> I have already writting some of my own jobs to handle this with stored
> procedures. I have createdDate, modifiedDate(updated via trigger) fields
> that are used to determine what data needs to be transferred. I
> I was wondering if SQL Replication Services would be a help in this area?
> Is there some other method that would be better suited for this task, or
is
> coding it by hand (which I already started) pretty much the better
solution?
> Thanks for the help,
> --Micah
>
>