SSIS Package Manager - PacMan

Source code checked in, #69709

Project Collection Service Accounts — Mon, 01 Oct 2012 22:10:56 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69708

Project Collection Service Accounts — Mon, 01 Oct 2012 22:06:45 GMT

Checked in by server upgrade

Source code checked in, #52373

_TFSSERVICE — Wed, 28 Jul 2010 17:08:20 GMT

Checked in by server upgrade

Updated Wiki: Home

MatthewRoche — Thu, 26 Jun 2008 15:19:28 GMT

Project Description
PacMan - The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.

PacMan is a utility that I developed primarily for my own use, and secondarily for use by members of my development team. Although I had always intended to share the PacMan utility with the SSIS community eventually, I kept pushing it back further and further since it wasn't "ready."

But my speaking schedule this month has convinced me that either it's never going to be ready, or else it's already ready. Maybe both. At various presentations this month in Stockholm, Sweden and here at home in Central New York I demonstrated PacMan to illustrate some of the things you can accomplish by using the .NET object model included with SSIS, and the response was an overwhelming "I want that!" from the seminar participants. I explained how this was a personal dev utility that wasn't really ready for prime time, and the interest didn't wane at all with that warning.

So here we are. I've done minimal cleanup, and the code isn't perfect (and there are very few comments, which is something that I would never allow to happen on a "real" project) but I could not find anything similar online, and I thought the best thing to do would be to share the code today instead of waiting to polish it before sharing it.

This is the first CodePlex project (or open source project in general) that I have started, so I honestly do not know how I am going to handle other project participants. The initial public release is online so everyone should be able to download the code to use (and tweak) on their own, but I don't currently know what I'll do when people want to contribute directly to the source code. I guess we'll find out when people ask.

Basic documentation is also available on my blog here: http://bi-polar23.blogspot.com/2008/06/did-you-miss-pacman.html

Source code checked in, #18701

MatthewRoche — Tue, 17 Jun 2008 17:51:45 GMT

Interim working version built against SQL Server 2008 CTP6. (So you may need to update the reference to the Microsoft.SqlServer.* assemblies) Includes new features such as listing variable values across sets of packages and identifying duplicate package IDs.

Source code checked in

MatthewRoche — Sat, 19 Apr 2008 15:53:15 GMT

Interim working version

CREATED ISSUE: Attempt to validate a folder tree fails

tobj — Tue, 01 Apr 2008 12:24:42 GMT

This is, as the comment in code says (in PackageManager.cs line 465), a known problem.
I'm using folder trees for development, validation and also for deployment/runtime (I've found it's the easiest way to do it and also obtain "local independency" at the same time).
I've found a simple solution that seems to work fine (all combinations were not tested).
In the PackageUtil class´constructor I assigned the member variable projectName the value of the filename (packageFile.Name) instead of leaving it "Unknown":
public PackageUtil(FileInfo packageFile)
{
Application a = new Application();
ssisPackage = a.LoadPackage(packageFile.FullName, null);
this.packageFile = packageFile;
this.projectName = packageFile.Name; // This line were added
}
After the change the validationTreeView will be built correct.

Source code checked in

MatthewRoche — Wed, 19 Dec 2007 19:05:29 GMT

Still a work in progress, but largely functional - added code to copy Script tasks from one source package to arbitrary sets of target packages.

Source code checked in

MatthewRoche — Tue, 13 Nov 2007 13:46:30 GMT

Fixed anchor problem with Description text box and label on Add Variable tab

UPDATED WIKI: Home

MatthewRoche — Tue, 13 Nov 2007 13:42:54 GMT

CREATED FEATURE: Targeted Component Updates

MatthewRoche — Wed, 07 Nov 2007 18:16:00 GMT

Currently the batch update features of PacMan are static and focused, and do not provide a generic batch updating solution. PacMan needs a more generic and flexible way to perform batch updates without requiring custom development.

Proposed feature: When a group of packages are selected, PacMan will present (on a new tab in the UI) a drop-down list of all component types (tasks, connection managers, data flow components, etc.) included in that set of packages. When the user selects a component type from the list, PacMan will then display a tree view of all components of that type in all packages. The user can then check or uncheck items in the tree to select only those components to be updated. (It is likely we will also need more targeted selection tools, but it is not yet clear how they should work.) The user can then edit component properties in a PropertyBrowser control, and update all selected components at once.

CREATED ISSUE: Better support for DelayValidation

MatthewRoche — Fri, 02 Nov 2007 23:17:02 GMT

Currently the Validation feature of PacMan may return "false positives" for packages with one or more components that have their DelayValidation property set to true. It is possible that there may be issues with these components, but that because of their DelayValidation property value, that the package will still pass validation.

Proposed feature: If a package passes validation but it contains one or more components with DelayValidation enabled, display a blue question mark icon in the validation tree instead of displaying the green success icon. For all other situations, maintain the current behavior.

UPDATED WIKI: Home

MatthewRoche — Wed, 31 Oct 2007 19:59:22 GMT

Project Description
PacMan - The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.

PacMan is a utility that I developed primarily for my own use, and secondarily for use by members of my development team. Although I had always intended to share the PacMan utility with the SSIS community eventually, I kept pushing it back further and further since it wasn't "ready."

But my speaking schedule this month has convinced me that either it's never going to be ready, or else it's already ready. Maybe both. At various presentations this month in Stockholm, Sweden and here at home in Central New York I demonstrated PacMan to illustrate some of the things you can accomplish by using the .NET object model included with SSIS, and the response was an overwhelming "I want that!" from the seminar participants. I explained how this was a personal dev utility that wasn't really ready for prime time, and the interest didn't wane at all with that warning.

So here we are. I've done minimal cleanup, and the code isn't perfect (and there are very few comments, which is something that I would never allow to happen on a "real" project) but I could not find anything similar online, and I thought the best thing to do would be to share the code today instead of waiting to polish it before sharing it.

This is the first CodePlex project (or open source project in general) that I have started, so I honestly do not know how I am going to handle other project participants. I'll have a public release available for download in the next few days (early November 2007) so everyone should be able to download the code to use (and tweak) on their own, but I don't currently know what I'll do when people want to contribute directly to the source code. I guess we'll find out when people ask.

UPDATED WIKI: Home

MatthewRoche — Wed, 31 Oct 2007 19:57:41 GMT

Project Description
PacMan - The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.

PacMan is a utility that I developed primarily for my own use, and secondarily for use by members of my development team. Although I had always intended to share the PacMan utility with the SSIS community eventually, I kept pushing it back further and further since it wasn't "ready."

But my speaking schedule this month has convinced me that either it's never going to be ready, or else it's already ready. Maybe both. At various presentations this month in Stockholm, Sweden and here at home in Central New York I demonstrated PacMan to illustrate some of the things you can accomplish by using the .NET object model included with SSIS, and the response was an overwhelming "I want that!" from the seminar participants. I explained how this was a personal dev utility that wasn't really ready for prime time, and the interest didn't wane at all with that warning.

So here we are. I've done minimal cleanup, and the code isn't perfect (and there are very few comments, which is something that I would never allow to happen on a "real" project) but I could not find anything similar online, and I thought the best thing to do would be to share the code today instead of waiting to polish it before sharing it.

This is the first CodePlex project (or open source project in general) that I have started, so I honestly do not know how I am going to handle other project participants. I'll have a public release available for download in the next few days (early November 2007) so everyone should be able to download the code to use (and tweak) on their own, but I don't currently know what I'll do when people want to contribute directly to the source code. I guess we'll find out when people ask.

CREATED RELEASE: PacMan Initial Rough Alpha (Oct 31, 2007)

Wed, 31 Oct 2007 19:51:02 GMT

This is (as the title implies) a rough alpha version of the PacMan source code. This is the version that I have been using on my own for several months. There is no real documentation, there are few comments, but for the most part it works, and the UI is largely self-documenting. Enjoy!

UPDATED WIKI: Home

MatthewRoche — Wed, 31 Oct 2007 19:43:39 GMT

Project Description
PacMan - The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.

PacMan is a utility that I developed primarily for my own use, and secondarily for use by members of my development team. Although I had always intended to share the PacMan utility with the SSIS community eventually, I kept pushing it back further and further since it wasn't "ready."

But my speaking schedule this month has convinced me that either it's never going to be ready, or else it's already ready. Maybe both. At various presentations this month in Stockholm, Sweden and here at home in Central New York I demonstrated PacMan to illustrate some of the things you can accomplish by using the .NET object model included with SSIS, and the response was an overwhelming "I want that!" from the seminar participants. I explained how this was a personal dev utility that wasn't really ready for prime time, and the interest didn't wane at all with that warning.

So here we are. I've done minimal cleanup, and the code isn't perfect (and there are very few comments, which is something that I would never allow to happen on a "real" project) but I could not find anything similar online, and I thought the best thing to do would be to share the code today instead of waiting to polish it before sharing it.

This is the first CodePlex project (or open source project in general) that I have started, so I honestly do not know how I am going to handle other project participants. I'll have a public release available for download in the next few days (early November 2007) so everyone should be able to download the code to use (and tweak) on their own, but I don't currently know what I'll do when people want to contribute directly to the source code. I guess we'll find out when people ask.

UPDATED WIKI: Home

MatthewRoche — Wed, 31 Oct 2007 19:43:09 GMT

Project Description
PacMan - The SQL Server Integration Services Package Manager is a utility designed to permit batch operations on arbitrary sets of SSIS packages. Users can select a single package, a Visual Studio project or solution or a file system folder tree and then validate or update all selected packages in one operation.

PacMan - the SQL Server Integration Services Package Manager - is a utility that I developed primarily for my own use, and secondarily for use by members of my development team. Although I had always intended to share the PacMan utility with the SSIS community eventually, I kept pushing it back further and further since it wasn't "ready."

But my speaking schedule this month has convinced me that either it's never going to be ready, or else it's already ready. Maybe both. At various presentations this month in Stockholm, Sweden and here at home in Central New York I demonstrated PacMan to illustrate some of the things you can accomplish by using the .NET object model included with SSIS, and the response was an overwhelming "I want that!" from the seminar participants. I explained how this was a personal dev utility that wasn't really ready for prime time, and the interest didn't wane at all with that warning.

So here we are. I've done minimal cleanup, and the code isn't perfect (and there are very few comments, which is something that I would never allow to happen on a "real" project) but I could not find anything similar online, and I thought the best thing to do would be to share the code today instead of waiting to polish it before sharing it.

This is the first CodePlex project (or open source project in general) that I have started, so I honestly do not know how I am going to handle other project participants. I'll have a public release available for download in the next few days (early November 2007) so everyone should be able to download the code to use (and tweak) on their own, but I don't currently know what I'll do when people want to contribute directly to the source code. I guess we'll find out when people ask.

Source code checked in

MatthewRoche — Wed, 31 Oct 2007 18:42:45 GMT

Initial version uploaded to CodePlex. Think of it as a "bare bones alpha" release.