Kirk Haselden

Feature Package for SQL Server 2005

Microsoft has released a Feature Pack for SQL Server 2005 that is a collection of very useful features including a DB2 OLEDB provider, a MOM package for SS2K5, SS2KDTS Designer components so that you can edit legacy packages inside Integration Services, the JDBC driver and the Management Objects collection which includes important object models such as SMO.

You can find the Feature Pack here:

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

__________________________ __________________________ __________________________

Microsoft ADOMD.NET

Microsoft Core XML Services (MSXML) 6.0

Microsoft OLEDB Provider for DB2

Microsoft Operations Manager 2005 Management Pack for Microsoft SQL Server 2005

Microsoft SQL Server 2000 PivotTable Services

Microsoft SQL Server 2000 DTS Designer Components

Microsoft SQL Server Native Client

Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider

Microsoft SQL Server 2005 Backward Compatibility Components

Microsoft SQL Server 2005 Command Line Query Utility

Microsoft SQL Server 2005 Datamining Viewer Controls

Microsoft SQL Server 2005 JDBC Driver

Microsoft SQL Server 2005 Management Objects Collection

Microsoft SQL Server 2005 Mobile Edition

Microsoft SQL Server 2005 Notification Services Client Components

Microsoft SQL Server 2005 Upgrade Advisor

Microsoft .NET Data Provider for mySAP Business Suite, Preview Version

Reporting Add-In for Microsoft Visual Web Developer 2005 Express

Universal configurations

The question came up on the forum if it is possible to have a universal configuration for all packages. A universal configuration would be one configuration that has configuration entries for objects in all or many of the packages on a given machine or environment. The catch is that some configuration entries would apply to objects in specific packages that don't exist in other packages. So, when applying the configuration, you would get a warning for each attempted configuration of non-existant package object. 

This is OK to do. It's possible and the warnings are only warnings, meaning they don't fail the package no matter how many you get. It's also possible to suppress the warnings generated by configuration with the "SuppressConfigurationWarnings" property on the package.

However, why do this when there is a better way. In an article I wrote for the November SQL Server Magazine, I talk about a better approach that is both adaptable and more powerful. I call it two stage configuration or making your packages location independent. If you use this method, you can eliminate a large percentage of the configurations for a given machine and you don't need to suppress configuration warnings.

http://www.windowsitpro.com/Article/ArticleID/47688/47688.html

Hope this helps,

Thanks,

Universe.Earth.Software.Microsoft.SQLServer.IS.KirkHaselden

A chat with Steve Jones...

I had a chat with Steve Jones while I was at PASS. And he asked if I'd do an interview. I've included a link to the interview but there's one thing I want to correct. In the main page it says:

SQL Server Integration Services is one of the most highly anticipated subsystems of SQL Server 2005 and Kirk Haselden is the guy that got it done.

That's both a bit embarrassing and very inaccurate. I was only part of the SSIS development team. It was a team effort and the truth is that they are the ones that made it happen. The development team included:

Ashvini Sharma, Sergei Ivanov, Ted Lee, Mike Blasczcak, Mark Durley, Michael Entin, Mohammed Shatnawi, Bob Bojanic, Brian Hartman, Ovidiu Burlacu, Silviu Guea, Matt David, and Raman Bakshi.

This team along with the test and program management team accomplished some pretty incredible stuff, overcame enormous challenges and pulled together in the end to deliver a great product. They are each talented and passionate about what they do and should be recognized for their efforts.

http://www.sqlservercentral.com/columnists/sjones/sqlserverspotlightonkirkhaselden.asp

Thanks,

Universe.Earth.Software.Microsoft.SQLServer.IS.KirkHaselden

SQL Server, BizTalk and Visual Studio Launch

I'm sitting in the Marriott across from the Moscone Event Center where the launch will be tomorrow. I'm excited to be a small part of this launch. There is a lot of excitement about it. Customers have been telling us for months now to "Just ship it!" We're finally there.

If you're reading this and you'll be attending the launch, come by the BI booth and say hello. I'll be either there or the Ask The Experts the entire day.

The software train keeps rolling, SP1 work is under way, Katmai planning is churning away too. But tomorrow we celebrate shipping!

Thanks,

Universe.Earth.Shipping.Software.SQLServer.IntegrationServices.KirkHaselden