September 24, 2013 at 8:28 am
I just started as dba at new co. I'm looking over what the previous guy did. He has some
ETL process done using SSIS. I'm looking the ssis over. it's ssis done in sql server 2008, running from sql server 2008 instance however it is pushing all of it's data t sql server 2012. I suppose he didnt want to convert it to 2012 even though the destination db was upgrated. It basically calls a few .exe's to bring down files, it then transofmes the data, loads it into sql server, runs several procs on a handful of db's, then archives the data to history tables. I don't see any parallel processing nor anything that would warrent using ssis, everything is going to one destination instance. It could easily be create within sql server as job w/ steps.
Does anyone have any input on why i should keep this running as an ssis? Just curious.
September 24, 2013 at 12:26 pm
If it is working well - why would you want to change it?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
September 24, 2013 at 1:56 pm
Maybe the integrated logging and event handling was used?
Or the previous guy liked the graphical approach of SSIS?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 25, 2013 at 6:51 am
To me it sounds like a process that should use SSIS since SSIS is an ETL tool. I guess it could use BCP, but you mention that it "transforms" the data before loading it into SQL Server, so those transforms might be the reason for SSIS.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 30, 2013 at 9:43 am
i found this ssis package is a step in a job calling several othe ssis packages. There is actually an ssis package calling a single stored proc. After documenting the process it appears the reason why ssis was used is because the job is running from an ETL box. In this job data is being pulled from two different instances on two different servers and geting stored locally as well as to two other instances and servers.
September 30, 2013 at 5:51 pm
You are right to question the use of SSIS - it's often overused and used incorrectly IMHO.
However, basically, if it is working, don't mess with it unless you can do it transparently.
October 1, 2013 at 1:02 am
nick.mcdermaid (9/30/2013)
You are right to question the use of SSIS - it's often overused and used incorrectly IMHO.
You can say that about almost any tool 😉 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply