SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Vs Linked Server with SQL Agent Jobs


SSIS Vs Linked Server with SQL Agent Jobs

Author
Message
pawana.paul
pawana.paul
Old Hand
Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)

Group: General Forum Members
Points: 322 Visits: 367
Dear Experts,

Need advice in planning.

There are tables which needs to be exported to / imported from databases on different SQL instances DAILY and also want to have exception handlers or notifications of the daily run and the status (especially on failure of perticular table). Please let me know whether to go with SSIS or create a linked server and schedule Job also let me know the advantages and disadvantages over both. At the max the below steps will be involved:

1. Drop the existing tables at destination
2. Create Tables at destination
3. Insert Data at destination.
John Mitchell-245523
John Mitchell-245523
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32723 Visits: 16637
I would nearly always advise the SSIS route. It's more flexible and it enables you to do transformations that you can't (easily) do with T-SQL. It's also easy to handle errors and send notifications.

Using a linked server is less secure since it increases the surface area of your server, giving another possible avenue of attack.

John
Andy Hyslop
Andy Hyslop
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2043 Visits: 3043
Personally I would go with SSIS as it was created for this kind of work.

There are many advantages of using SSIS to name but a few:

- Good error handling possibilities
- Bulk Inserts
- Visibility of what is happening in the pipeline
- Configurations

I'm sure there are more that will be added to the thread!

A disadvantage of using SSIS is the appalling error messages and it can at times be a pig to work with (my personal opinion not a statement of fact!)

Question why steps 1 & 2 what are your reasons for dropping and recreating the tables already in place?

Andy

==========================================================================================================================
A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe
pawana.paul
pawana.paul
Old Hand
Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)

Group: General Forum Members
Points: 322 Visits: 367
Good Question. This is required as there will be changes made to the columns at Source (adding or dropping columns). If we go with SSIS, we need to do mapping too.

Please advice that SSIS is the better choice.
Andy Hyslop
Andy Hyslop
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2043 Visits: 3043
pawana.paul (5/11/2012)
Good Question. This is required as there will be changes made to the columns at Source (adding or dropping columns). If we go with SSIS, we need to do mapping too.

Please advice that SSIS is the better choice.


Now that is a much more complicated process...

I have had colleagues who have done this in the past successfully using SSIS but not
without some pretty complicated dynamic SQL and a combination of #Temp tables, agent jobs.

Without this SSIS will pick up that column names have changed or no longer exist and fail as a consiquence without you manually amending the ETL's

Sorry that may not be much help but as I've personally never had to overcome this challenge (yet) its all I can offer.

Andy

==========================================================================================================================
A computer lets you make more mistakes faster than any invention in human history - with the possible exceptions of handguns and tequila. Mitch Ratcliffe
pawana.paul
pawana.paul
Old Hand
Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)Old Hand (322 reputation)

Group: General Forum Members
Points: 322 Visits: 367
Thanks Andy. Appreciate your help.

Others,

Request you to advice if you have any inputs on this.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search