Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Web service versus directly sourcing database

Web service versus directly sourcing database

Web service versus directly sourcing database

We have an ongoing debate about the use of webservices as a ETL-source. Our application development engineers propagate using only a webservice as a source for extracting data. They would like to prohibit direct database access.
We have experienced with SSIS and webservices and found it cumbersome and slow. Application development thinks that we are to stupid to correctly access tables, but we fear the overhead of having to go through a webservice to simply transfer data. The debate is as yet inconclusive..  Any thoughts?

Ties Blom

RE: Web service versus directly sourcing database

It sounds like a turf war or something.  I doubt they think you are "too stupid."  Each side should approach this professionally.  

One suggestion would be to request read-only access to their test server for this database.  Write your ETLs against the test server.  When you're finished, review your select queries with the source system owners so they know what's going on and can offer any suggestions if needed.  After that, I bet they would be more comfortable with allowing you to run these queries against production.

RE: Web service versus directly sourcing database

Their main argument is based on the 'fact' that some factors will not be stored in database tables , but can only be reproduced through the application logic, hence a webservice. However these are exceptions, since most data just sits there ready to be extracted. We have experimented with SSIS reading the output of a webservice, but have found it to be cumbersome and decidedly slow. It is also not a good way to extract large facttables, cause it would require a batch oriented type of extraction (webservices do not allow large amounts of data in one go..)

Ties Blom

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close