Microsoft SQL-Server Integration Services is not a new product.
It goes back to the original DTS packages of years ago.
I wrote DTS packages and felt comfortable in that environment.
So when writing/debugging SSIS packages, I have an understanding of what I'm doing.
However, if you didn't write the package, and asked to debug it, it is not an easy task.
On first glance, the package seems overly complex.
However by breaking each task down to simpler units, it's not difficult to understand.
In the 2008 r2 version, they have some new features.
However looking at the SQL code beneath seems straight forward.
What I did to troubleshoot is to number each task and write a brief description.
Next, copied the SQL to Transact SQL editor to view what's going on.
However, I can not run the package because it updates production tables and such.
Once you have a birds of view, as well as look under the hood, the problem presents itself.
In my opinion, SSIS is another animal when it comes to programming.
It's not your typical Java or .net app where you can step through the code line by line.
It's a bit fragmented.
But not impossible.
I still prefer to troubleshoot production problems of someone else code rather than write the code from scratch.
Guess that makes me a "maintenance" coder.
Kind of a niche.
Oh well, could be worse I suppose.
SSIS is good for doing specific tasks.
I signed up for the Hortonworks Certified Associate exam last Thursday. Figured if I sign up, I'd have to take the test. And if I tak...
Saw a post today on Twitter, " Microsoft releases CNTK, its open source deep learning toolkit, on GitHub " This is big news. Be...
It seems like open source applications are the mainstream today. So many new products delivered through Aache foundation. Some do this. S...