Critical Status - Database-Oriented Issues Plus

It seems that everything has a critical status, especially when it comes to databases and software development! Here's a place for listing issues and ideas relating to database and development issues. I'll list problems and ideas mainly related to SQL Server 2005. Post your thoughts, advice or complaints! Later this year will be the 25th anniversary of being in the trenches of the IT industry. I specialize in database applications development. I'd like to share my experiences with everyone and learn of those of others. You never stop learning.

Tuesday, May 6, 2008

Global Variables in the new SSIS packages


Got a question about SSIS. There doesn't seem to be a good equivalent to the Global Variables in old DTS in the new SSIS packages. Are you using some solution that you recommend? I know there is Win environment variables and xml config files, but these are not very friendly to move.


Ooooooo interesting question! I'll look but I'm willing to bet with it
being a .NET solution/project, you can probably put them in a bas file or
class file. Also, check the Package properties. Click the ... Button for
expressions. See if that helps. Being that it's a VS project and not a
MSSQL project, I'd assume listing variables like you would in VB.NET. I
recently starting thinking of SSIS in terms of VS instead of SQL. It really
opens the door to a lot of things. I'd written replication apps in VB6 with
the DMO. I know you can do the same in DTS. So that's where I'd start
looking. Its still encapsulated but pushed out of the IDE. I just added a
VB script to a project. I guess it could be called from a task I don't
have regular VS.NET on this server or my machine, but I know I should be able to add a bas or cls to a project. I'll look further and let you know
what I find!


1 comment:

daspeac said...

I have heard about another way of repair ms sql database. Besides, you can visit my blogs at: or where I’m trying to share my experience with regard to data corruption issues