As an author, I find his words challenging and inspiring.
Buck Woody has an interesting post about Windows 2008 Terminal services and SQL SSMS. He includes setup instructions and a list of pros and cons. It’s cool to see this functionality making its way into SQL Server. Great job SQL Server Team!
The more I tinker with SQL Server 2008, the less it looks like SQL Server 2005 R2.
I’ll be presenting Testing the Database to the Roanoke Valley .Net User Group Thursday 3 April 2008. If you read this blog and you’re in the area, stop by and introduce yourself!
The SSIS Debugger with it’s stationary tasks and transformations, just sitting there changing color – where’s the graphic feedback in that?
The new functionality will reportedly include more “real-world feedback” graphics. For instance, when a Data Flow task fails for some reason, the Data Flow task on the Control Flow will appear to explode. Truncation on loading a destination will cause scissors to fade in near the Destination Adapter. The scissors will then slice off a portion of the Adapter proportionate to the amount of truncation occurring (it will slice off half if you’re trying to push a varchar(256) into a varchar(128) column). Unicode-to-nonUnicode errors will cause a brick wall to appear over the data flow pipeline. Success will be denoted by a stick figure jumping up and down with arms raised.
How’s that for feedback?!
In addition, the feature is extensible – you can create you own graphics to represent conditional results. I’m looking forward to working with this new feature!
I’m working on an SSIS package that FTPs files from heterogeneous sources to Windows servers. I currently have three types of servers in the mix: Windows, Unix, and iSeries. When I first started this phase of the project, I tested the SSIS FTP Task and it worked well… on two out of three.
Hope Floats (or at least Ints…)
Due to some external requirements, the solution was to implement a custom FTP class in script.
The Script Task and Script Component are two of the most powerful features of SSIS – and SSIS scripting is about to get even better. SSIS 2005 uses Visual Studio for Applications (VSA), while SQL Server 2008 integrated Visual Studio Tools for Applications (VSTA).
SSIS Giveth and SSIS Taketh Away
Now you can code in C#. I found the ScriptLanguage property dropdown a cruel joke for developers wanting to select something other than the default Microsoft Visual Basic .Net. It’s a dropdown after all. But alas, there was but a single option. That’s changed in SSIS 2008. Yay.
As with everything is life, there’s a trade-off here.
Existing Scripts will need to migrate from VSA to VSTA. The more complicated the script (like say, a custom FTP class, hypothetically…), the more manual conversion will be required.
Being a good consultant who doesn’t want my code to expire when my client upgrades to SQL Server 2008, I’ve been upgrading the class in CTP6 on my own time (also respecting the fact they’re not paying me to fix things that aren’t broken – yet). It’s been fun so far.
Lesson learned: There is no free lunch.
SSIS 2008 Is Cool
Make no mistake: SSIS 2008 has some awesome new features. The discomfort of converting the script is well worth full access to the .Net Framework.
When you begin converting you will want to know about this link: Migrating Scripts to VSTA. It’s a good starting place for some of the issues you’ll encounter. For starters, it explains when the actual script conversion takes place (when you open the package).
All in all, this is turning into a learning experience, and I love learning experiences!
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.