FileSystem Deployment

I am still a little confused on how the file system deployment works. When I deploy my files they end up in {ROOT}/Microsoft SQL Server\90\DTS\Packages\{PKGBUNDLE}, but the connection managers still reference the original dev path. Why does it copy to a seperate directory but still reference the old path, what's the significance? Is using pkg_vars the only way to update conn mgrs to reflect the new path? (outside of using a grep util to search and replace)

I guess I am looking for design patterns, how are others handling the deployment process when deploying on the same server?

P.S. When we port this to the production server, we plan on using the same directories and steps as in staging...What you are probably after is configurations. These are designed such that you store all of the parameters which change between deployments in a configuration, or related store, and just pass the correct configuration into the package each time you use it. The location of the configuration is what may change, but the way you specify this would be chosen such that is common accross all machines.

The package storage location has no bearing on connections and neither should it. Just because my packages move the connection location an still be teh same, teh same SQL server, the same smpt server, and the same file path, if local to a machine or if using a UNC path, they can still all be the same. File system deployment vs any other deployment is just about the storage location really, not the package internals and settings.|||

Yah, I understand your point, I was more so wondering if I could have a seperate custom stored location other then under the default SQl Server\90\DTS....

|||Sorry, I get you. Not sure if it is supported, but playing with MsDtsSrvr.ini.xml may be what you want C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml

Some related links-

SSIS and SQL Server Instances
(http://www.sqlis.com/default.aspx?57)

Modification of MsDTSSrvr.ini.xml does not work in June CTP - Microsoft Technical Forums - It does work, see post.
(http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=61179)

Try a BOL search for that file as well.

Files not creating on Win2003

I have created a package which extracts data from a table and creates several files. This works fine on my PC (WinXP SP2), but when i deploy it to the server it doesn't work. I have also tried to create the package from scratch on the server as the administrator and it still has the same problem. Anyone have any ideas?"it doesn't work" is not much to diagnose the problem. Are you getting any error? Have you enabled SSIS logging - what logging information are you getting?|||You haven't provided a lot of information here, but the first thing to check is permissions on the folder you are writing to.|||Sorry Michael,

"it doesn't work" means that the files are not being created but the rest of it executes successfully. I'm not sure how to enable SSIS logging. Can you please point me to where i can find out how?

Thanks|||Sean,

The package is deployed on a Windows 2003 Standard server, SQL Server 2005 Standard. I am writing the files to a directory on C:\ and have tried giving Everyone full control on the directory and still no files are created.

Is there anywhere else i can check for the correct permissions?

Thanks|||

In the designer, click on the SSIS menu, and then choose Logging...

Check the Event Viewer in Administrative Tools to see if there are any Security exceptions being thrown. Sorry I can't be more specific here. It's tough to know exactly what your problem is. :)

|||Thanks Sean

After turning on the logging i have worked out what the problem was. It was a bug with my package.

Thanks everyone for your help.