Making lakhs of calls to WCF from SSIS

Question

0.00/5 (No votes)

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.

Thanks

Posted 7-Jan-13 1:33am

tgurinder

Updated 7-Jan-13 2:30am

Keith Barrow

v2

Add a Solution

Comments

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).

ZurdoDev 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.

[no name] 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?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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