Prev: Replication - automatic identity range support
Next: The specified pull subscription is not configured with asynchronization agent job
From: SherryH on 25 Mar 2010 17:46
I have an application that is storing a lot of data in a SQL 2005 database
(adding around 50 million rows) in a window of about 6 hours each day. We're
managing the load with partitions and bulk operations on that system, but now
we're being asked to replicate the results of the daily processing to an
external database for analysis work. Due to security concerns, the remote
site IT departments won't let us pull anything from their network. The only
mechanism I'm being given to work with is outbound (push) SFTP.

Obviously I'd prefer to use some kind of transactional replication, since
copying a snapshot of the entire database is not an option. However, I'm
limited by the requirement for file-based push only. Are there any built-in
SQL Server mechanisms that might help me with this, or am I going to have to
come up with my own transactional tracking mechanism to generate the file to
update the external system?
 | 
Pages: 1
Prev: Replication - automatic identity range support
Next: The specified pull subscription is not configured with asynchronization agent job