SSWUG Expo..I'm up!
I am proud to say that one of the webcasts I taped last year for SSWUG is part of the Free Virtual Expo. My SSIS Enhanced Threading Framework is being shown. Click here to register.
Posted in: SQLServer
I am proud to say that one of the webcasts I taped last year for SSWUG is part of the Free Virtual Expo. My SSIS Enhanced Threading Framework is being shown. Click here to register.
I'll be giving a presentation tomorrow, Tuesday 2/21/2012 at 12PM EST on my Enhanced Threading Framework design. Here is the abstract:
If you are looking to improve the performance of your SSIS packages by taking advantage of SSIS inherent parallelism using advanced techiniques please join us, link.
I built a small ruby program a while back to help with two things:
The problem was simple. I needed to easily identify the problem areas of a complex stored procedure. By problem areas I mean sections with a large logical read count. The statistics IO output was rather large ( a few hundred lines) and was a bear to work with. I thought, "hmm. If I could get a summarized count I could easily pinpoint potential problem areas and spend more time problem solving than problem hunting". The end result is query_io_reader.rb.
For those of you who were unable to attend the SSIS webcast I gave for Quest Software, here is the corrected link to the recorded session : The Experts Perspective - 14 July
Webcast: SSIS Tricks & Tips
Date: Thursday, July 14
Time: 8 a.m. PT / 11 a.m. ET / 4 p.m. UK / 5 p.m. CE
Duration: 45-60 minutes
Cost: Free
Don’t miss this SQL Server Integration Services (SSIS) webcast featuring invaluable guidance from industry-leading expert Josef Richberg. You’ll gain a deeper understanding of SSIS’s quirks, capabilities, and the pitfall of parallel path choicing.
Plus, you’ll learn how to:
While designing a package last week with our consultant, Latha Chathri (twitter), I came across a need to call a stored procedure drom within a Data Flow Task. I have never needed to do this before and while the call is simple there are a few quirks that I found and would like to share with you.
I've created a sample procedure with a single input parameter (@incoming) and a single output parameter (@outgoing).