I like to say "Just because you can do that in SSIS doesn't mean you should."  I don't know how many data flow's I've looked at where I end up saying, "I could've done all of this in SQL."  One example read in 3 tables, all on same server, did about 13 look up's, 3 splits of the data, 4 merges, 4 calls to VBscript before ending up in one SQL table.  I was able to do the exact thing in about 600 lines of SQL(I'm sure i could reduce that if I wanted to).  I did all of that just to prove it could be done.  To me that SQL is a lot easier to understand and it's easier to maintain than that ugly data flow.

I'm not one to jump on the newest of latest and greatest of anything.  I'm not going to stand in a line for some new phone or TV or other gadget or toy.  I'm not going to stand in line just to be one of the first to see a movie.  I guess I've always been that way, not just something I realized as I got older.

I'm also not going to go out and try and learn some new software or language if i'm not going to be using it. I'm one of those I need to be doing it to retain it.  Now I haven't used COBOL in over 15 years, but I think I could still do it, just maybe not very well.  The only reason I think that is because I coded in it for over 10 years.  Now I learned some Java Script back in earl 2000's, but I haven't used it since that one project.  So I doubt I could do much with that.