Best Way to Synch 2 Tables?

All,

I have an Access DB. On a nightly basis, I want to look at an Other
DB (not Access, but SQL) and:

+ Add any new records from Other.Clients into Access.Clients

Quote:

Originally Posted by

Update 9 fields from Other.Clients into Access.Clients where changes have occured in Other.Clients.

Is this something I should use a "tool" (SQL Data Compare, SqlSync,
etc.) to do, or could I pull this off reliably every night just using
SQL from the query I could construct to do the job from inside my
Access DB?

And for question Deux, if I can just use the SQL I will write, what's
the best way to kick off the process at 3:00 am every morning?

Thanks,

PatrickPatrick A (parkins@.stradley.com) writes:

Quote:

Originally Posted by

And for question Deux, if I can just use the SQL I will write, what's
the best way to kick off the process at 3:00 am every morning?

A scheduled job in SQL Server Agent.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Best way to replicate huge transactions

We do nightly processing for our warehouse data on Server A and we replicate
the data after all the processing to Server B.
What is the fastest way to push this data across ? Right now it seems like
it takes more than an hour to push all the changes across.i.e an hour
latency. We are using trans replication. Any parameters we can tweak to push
the data faster or are there any other techniques.
Please advice.. Thanks
Hassan,
this article quantifies the effects of using most of the available
parameters:
http://www.microsoft.com/technet/pro.../tranrepl.mspx
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||replicate the execution of stored procedures if
1) your stored procedures modify more than one row at a time
2) the bulk of your batch operations use procs
consider using merge replication if
1) your batch operations modify the same row many times, ie a stock market
application.
2) use download only exchangetype
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com