Click here to Skip to main content
13,191,638 members (64,026 online)
Rate this:
Please Sign up or sign in to vote.
See more:
Is it a good idea to use SSIS to make 200,000 calls to WCF?
My requirement is to get data from SQL Server, pass that to WCF(row by row) to get related data from another DB server, get back data and Update Original DB, call again one more WCF(row by row) to send status to another server.

What would be the best way to implement it. Performance will be key concern here.

Posted 7-Jan-13 1:33am
Updated 7-Jan-13 2:30am
Keith Barrow159.1K
Keith Barrow 7-Jan-13 8:35am
Why do you think this is a good idea? You must have reasons. Personally I'd have thought updating one database from the other directly through SQL would have been quickest, next quickest would be an app that connects to two databases, pretty much the slowest way to do this would be via a web service such as WCF, even on named pipes. I'm also unsure why you need to do this row by row, this will be slower than updating many records at once.

It might be better to explain what you are trying to do, and what constraints you have (e.g. the DBs can't communicate directly).
ryanb31 7-Jan-13 8:41am
Best way is always relative. You have to look at what servers you have, including hardware and what it will take to install and maintain. SSIS is fine and likely a good idea. If it needs a lot more fine tuning then you could use BizTalk.
Shameel 7-Jan-13 9:37am
What makes it necessary to use WCF instead of a direct DB-to-DB approach? And why update it row by row instead of as a batch?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web03 | 2.8.171017.2 | Last Updated 7 Jan 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100