>In my perfect world though, in a batch situation, with a small update, >the publishing side would fire a DTS that connected to the remote side >and updated the data. This one takes very little time to setup, and >doesn't place the constraints that replication does on the schema. It >also can be done manually or automated, so it's flexible.
Wow, well said; thank you for taking the time to help me understand this. I always thought DTS was used to migrate databases, or transfer data between disparate data sources. I didn't realize it was useful for making small batch updates. I had already run into the schema problem you mentioned with replication since my primary keys are identities. But why don't you recommend FTPing the updated database files? Is that some kind of SQL Server no-no? If so, why? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
