Todd McDermid's Blog: PASS Summit 2009: MVP Birds of a Feather Lunch

The PASS Summit next week has a very compelling event on Tuesday at lunch. They asked the SQL Server MVPs attending the summit to host a lunch table on the topic of their choice. This isn't a one-way presentation - it's a round table - an opportunity for you to talk to an MVP and other attendees about a topic they (and you) are passionate about, want to find out more, or that you simply have a question or two about. The topics are varied and the hosts are very prominent MVPs (your truly excepted).
I took advantage of the opportunity - and I'm glad I did so quickly, because the tables were swiftly picked up, to the point of a significant waiting list. For me, it's bittersweet - I won't get to go sit down at the other tables. But you can jump around as much as you want!
Why I Chose "SSIS Scripting and Custom Objects"
Simple answer - I like to do this stuff, and it's my table. I mean, seriously - if you've read my blog at all, this is a no-brainer.
Long answer - First, I think that the scripting capabilities and custom extensibility in Integration Services set it apart from other solutions in the market, and give Microsoft a distinct advantage in the ETL game. Some say that it simply exposes what holes there are in an immature product. There is truth to that, definitely - it gets used as duct tape frequently. However, it certainly provides a way to get anything done in SSIS. And I mean anything.
Second, I believe that for some package designers, it's become an overused crutch. If you've comfortable using C#/VB.Net, you can begin to solve every problem with a Script - even when you could use standard parts. If you do that, I think you risk short term gain for long term benefit. Microsoft can't make your Script run any differently in SQL 11, 12, or 13. But they can (and will) improve the standard parts. Using Scripts can lock you out of that benefit. Anyone tried to upgrade a DTS ActiveX script to SSIS?
And third, for those that tend to overuse scripting and have gotten themselves into a cut-and-paste maintenance nightmare - I say "go big or go home". Convert your scripts into custom objects, for pete's sake. You already know how to code in C#/VB.Net - take the next step to build a reusable and easily configurable custom object - it's really not that much further, honest!
What I Plan To Talk About
They asked the "hosts" to prep a little something to talk about to get people in the spirit of the table. I say "asked" because it's really about the discussion, not another presentation - and it's perfectly acceptable for everyone (except the hosts) to bounce around tables and participate in more than one group.
If those people that happen to sit down at my table at the opening bell want to hear something (and please, let there be somebody!), I'll tell them about all the different parts of Integration Services that you can mould, automate, and customize to your will - and why that can be a very useful thing indeed.
What I'd Like You To Talk About
It would be great to hear from fellow SQL pros (yes - that's you!) about:

The times you have "had to" use a Script to get something done. Why did you do it? Is it something you think (reasonably) should have been an out-of-the-box capability of SSIS?
Your experiences using Scripting in SSIS. Was it hard or easy? If it was hard or confusing, what made it that way?
How repetitive are your Scripts? Do you have the same ones in every package?
Have you made any custom objects? Have you used any third party ones? Why did you chose to do that? Did it work out? Do you want to share your custom-built object or relate the usability and value of the third party one with other DB pros?

Resources I'll Talk About
If you drop by and join the discussion, you'll probably want to know more about how to use Scripts and how to build Custom Objects for use in SSIS. Here are some of the resources I'm sure to mention. I'll likely be adding more over time as I stumble across them again, or if you ask a specific question at the table!