Re: data update suggestions
- From: "Rafael Lenartowicz" <rafaell@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Apr 2007 22:05:53 -0400
I guess you should start with estimating amount of data being transfered, it
frequency and concurrency requirement.
the more data and more frequent and how fast you have to be "in sync"-
replication is most likely scenario you should go with. Less data and less
frequent - a custom app or SSIS package might do the trick...
"Sas" <Sas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0F14BBEA-A720-40FF-88A3-8C7B126DBC46@xxxxxxxxxxxxxxxx
We have production database (1TB, sql server 2005) and we will receive
daily
updates from a vendor. All the updates will be imported in another
database
first (source db). What would be the best way to apply the updated
information to the from the source DB to the production DB (example of
updates are: new products or just price changes on existing products
etc....). I was thinking about unidirectional merge database (src db to
prod
db) but if someone can give some suggestions it would be greatly
appreciated!
Thank you all
--
--
System Engineer
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
.
- Follow-Ups:
- Re: data update suggestions
- From: Hilary Cotter
- Re: data update suggestions
- Prev by Date: Merge Replication Status
- Next by Date: Re: Turn OFF Automated Conflict Resolver in Merge Replication
- Previous by thread: Merge Replication Status
- Next by thread: Re: data update suggestions
- Index(es):
Relevant Pages
|