Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Reusing package configuration file across all packages in a solution?

I have 5 packages in a solution.

For 1st package, I add a package configuration file (xml) named common.dtsConfig containing only Database Connection configurations.
For the same package, I add another package configuration file names first.dtsConfig containing configurations specific to 1st package.

Now for 2nd package, when I reuse from existing package configuration (common.dtsConfg) with same name, it allows me to do that. I also create a package specific configuration file for 2nd package.

And so on for all 5 packages.

This works fine for development. If my database user/password changes, I edit onyl one file i.e. common.dtsConfig.

But, when I want to create the deployment utility, it fails by throwing error that "cannot copy common.dtsConfig from <src_directory> to .\bin\Deployment because it already exists". Due to this failure, I do not get the DTSInstall.EXE.

Surprisingly, this was working with June CTP and has failed with September CTP.

What should I do to reuse the package configuration file across all packages for deployment with September CTP?

thanks,
Nitesh

This is a known problem.

We fail to create a deployment manifest if 2 packages in the project share the same config file

Problem Description:

Build of a SSIS project with duplicate package config files reports the following –

Error 1 System.ApplicationException: Could not copy file "C:\VITAL\Prosjekter\Test\SmallProject\connectionLOG.dtsConfig" to the deployment utility output directory "C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment". > System.IO.IOException: The file 'C:\VITAL\Prosjekter\Test\SmallProject\bin\Deployment\connectionLOG.dtsConfig' already exists.

and as a consequence the deployment manifest file is not created and some of the package config files may not be copied to the deployment folder.

Workaround:

Create Proj.SSISDeploymentManifest manually using below template. Additionally verify that all config files and miscellaneous files (if you have it in your project) are present in deployment folder and copy in those that are missing.

<?xml version="1.0" ?>

- <DTSDeploymentManifest GeneratedBy="REDMOND\usr" GeneratedFromProjectName="Integration Services Project15" GeneratedDate="2005-09-20T16:17:42.4195337-07:00" AllowConfigurationChanges="true">

<Package>Package1.dtsx</Package>

<Package>Package.dtsx</Package>

<ConfigurationFile>cp.xml</ConfigurationFile>

<ConfigurationFile>cc.xml</ConfigurationFile>

</DTSDeploymentManifest>

Resolution:
We will fix the problem in SP1.

For meantime we consider releasing a QFE

|||

I have 2 packages within a project that each have their own config file. When I build them and have the deployment package created, it doesn't put a DTSInstall.exe file in the directory.

I haven't created a deployment package since the June CTP, so I'm wondering if this has changed? I see some posts out there referring to DTUtil, should I be using that instead, or can I just copy the packages, change the config file settings and I'll be set?

Thanks in advance for your help.

-Chris

|||Just downloaded SP1. I dont see this fixed.|||

I am experiencing the same problem even after the installation of the Cumulative Hotfix 2153.

Regards,
Yitzhak Khabinsky

|||

Jamie, what is your word on the subject?

I know that you are using shared config files quite extensively.

Microsoft’s article (Article ID: 910419) mistakenly claims that it is fixed:

http://support.microsoft.com/?kbid=910419.

FIX: You receive an error message when you try to build a project for deployment and the project contains multiple packages that are configured to use a shared configuration file in SQL Server 2005 Integration Services

Regards,

Yitzhak

|||

Yitzhak,

Up to now I have never used the deployment wizard so have not come across the problem.

-Jamie

|||

The error actually is happening during the Build process

It is very easy to reproduce.

BIDS project should have a couple of SSIS packages. Shared *.dtsConfig file should be explicitly added to the project. After that the config file shows up under the Miscellaneous node on the project tree. Right click on the SSIS project node and select Build option. The error shows up in the Output window.

Regards,

Yitzhak

|||Hi has anyone checked out the hotfix to see if the issue is resolved?|||I'm still having this issue as well. I installed service pack 1 a while ago. Is MS going to fix this soon? I use SSIS a lot and have found source control options VERY lacking. My company paid a lot of money to get TFS, and I'm not seeing a lot of value where SSIS is concerned.|||

I checked it out today. It did NOT work for me. I still get the same error.

|||

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

|||

Rafael Salas wrote:

I don't know if this would help; but until know I always have used .dtsx package files and never got to use the deployment wizard; and hat is because copying the .dtx and config files to the target destination is just that easy that I have not bothered to learn about wizard. I guess my suggestion here is not to use the deployment wizard.

I concur with Rafael. We're a *little* bit more scientific than that because we use WiX to build our deployment MSIs. I never go near the deployment wizard.

The beauty of WiX is that it is MSBuild compliant which means it can run in conjunction with TFS so all our MSIs are getting built using continuous integration (that's in answer to the guy that mentioned TFS).

Sorry, I know that's not much use to the people on this thread that are experiencing grief. It may be worth posing on another thread the question "is this fixed in SP2". The guy on this thread that replied from Microsoft (Nick Berezansky) no longer works on the SSIS team.

-Jamie

|||

Not fixed in SP2 - just tested it.

I realize this may not be an optimal solution, but have you tried removing the *.dtsconfig from the project (that is, don't include it in the misc. files). When I do this, the project builds with no errors, and the deployment utility is created with the *.dtsconfig file in the Deployment folder. The file can still be under source control, through the source code explorer with TFS, or VSS, or whatever tool you are using.

In general, though, I'd agree with Jamie and Rafael on this. I haven't used the deployment wizard since the first iteration of my first SSIS project.

Re-use data from SqlDataSource

I have a page containing a FormView, which gets its data from a SqlDataSource control and displays details of a job. Two of the fields are location and job title. I want to re-use this data to create a dynamic page title. I know I can do this by setting the Page.Title to what I want to, but do I have access to the data outside of the FormView to which the data source is bound? If so how? Or will I have to perform an additional SELECT statement to get this data again?

Hi

No need to perform additional Select statement. You can access the FormView data in DataBound event. Try the following code:

protected void FormView1_DataBound(object sender, EventArgs e) { Page.Title = ((Label)(FormView1.Row.FindControl("column1Label"))).Text; }

Hope this helps.

|||

Brilliant. I've got that working nicely now, and discovered more events to play with

Thank you.

Returning top 2 results from each different data in a row and inserting into new table

Hi All,

I'd much appreciate any help with the following problem. I need a statement, cursor, anything....

I have a table in MS SQL Server containing the following (simplified version of course :)):

PID DATE OTHER INFO
aaa 31/05/2005 blah blah blah
aaa 06/06/2004 moo moo moo
aaa 17/05/2005 baa baa baa baa
bbb 31/04/2004 niegh neigh neigh
bbb 30/04/2004 bleet bleet
ccc 01/05/2005 oink oink
ccc 03/05/2005 cluck cluck
ccc 02/05/2005 meep meep
...etc etc etc

My challenge:

For each unique PID, sorted by date order descending (NOW first ... END DATE bottom), I need to return the top 2 results for each PID and insert them into a NEW table.

For example, using my simplified data above, the results I would exepect in my NEW tablet would be:

PID DATE OTHER INFO
aaa 31/05/2005 blah blah blah
aaa 17/05/2005 baa baa baa baa
bbb 31/04/2004 niegh neigh neigh
bbb 30/04/2004 bleet bleet
ccc 03/05/2005 cluck cluck
ccc 02/05/2005 meep meep

Note: It has returned the two most recent results for each unique PID.

I'm thinking it may need a cursor of some kind, but I just can't get to grips with what needs to be done, lord knows I've tried for the last two days.

Any help sincerely appeciated!

Rob

Hi
I'll try to help you using a cursor but there is a solution without it I don have it now

create table #result(PID char(3) ,Date datetime , otherinfo varchar(50))
declare @.id char(3)
declare c cursor for
select distinct PID from tblInfo
open c
fetch next from c into @.id
while @.@.fetch_Status = 0
begin
insert into #result(pid,date,otherinfo)
select top 2 pid , Date,otherinfo from tblInfo
Where PID=@.id
order by Date desc
fetch next from c into @.id
end
close c
deallocate c
select * from #result

I assumed that your SQL server is not case-sensetive and your table id tblInfo
|||Perfect - thank you so much!|||

Hi Rob,

there is a solution to solve your problem with a view / select statement, too.

select
top2keys.PID,
top2rows.DATE,
top2rows.OTHER_INFO
from
(
select distinct
PID,
(select top 1 top1.DATE from datatable top1 where base.PID = top1.PID order by top1.DATE desc) as top1date,
(select top 1 top2.DATE from (select top 2 tophelp2.DATE from datatable tophelp2 where base.PID = tophelp2.PID order by tophelp2.DATE desc) top2 order by top2.DATE) as top2date
from
datatable base
) top2keys
left join datatable top2rows
on top2keys.PID = top2rows.PID and (top2keys.top1date = top2rows.DATE or top2keys.top2date = top2rows.DATE)
order by
top2keys.PID,
top2rows.DATE
If you have your PID values in a separate table and pid is a unique key, you can avoid the "select distinct ..." with a "select ..." and "datatable" with the table name where PID is unique to achieve better performance. But this wya should outperform the procedure approach more then 10 times, depending on records in the data table.

Regards,
Tom

|||If you are using SQL Server 2005 you may try the following

WITH T1 as (select RANK() OVER(PARTITION BY PID ORDER BY Date ) AS RNK,* from T)
SELECT PID,Date,otherinfo FROM T1 where RNK<=2