View Complete Post
How can I create a batch file and run it in command prompt to deploy SSIS packages ? Is there any examples to do that ?
I went through other threads and links on this subject. Still one thing which concerns me is the config files.My current folder path is C:\Karunakaran\folder1\folder2\Under folder2 I have the following files4 dtsx files1 .database file1 .dtproj file1 .dtproj.user file1 .sln file1 .suo fileConfig folder ( C:\Karunakaran\folder1\folder2\Config\)common.dtsConfigoracle.dtsConfigBased on some of the threads, when I enabled package configuration, I changed the path fromC:\Karunakaran\folder1\folder2\Config\common.dtsconfig ->ÃÂ common.dtsconfigOnce I did this, when I open the project I get a dozen of warning similar to the one belowWarning loading <package1>.dtsx: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed.What am I doing wrong here? If I have to deploy this to another box, what should I do to ensure that nothing breaks once its copied / installed?Thanks
Do we need to install Integration Services in order to run SSIS packages in file system?
Our production machine doesn't have SSIS installed. Today, I created an SSIS package in our Development Server. Now I want to be able to deploy the package into file system and run the package from SQL Job. Please advice.
SSIS After deployment of package
After the deployment of ssis package in filesystem or in sql server.........how the clients can extract the package?
I had a strange issue in testing my package, after it was deployed to a Test server.
The details of the server
Sql 2005 is installed, in the D:\ drive
I have used a package, where i use a custom DLL to read values. Hence, i added that DLL to the GAC. I was in the assumption that this should complete my proceess of deploying this package.
However once i executed the package, i got an error - Could not load the Helper object.
Unable to CAST "system.object" to namaspace.class.Helper.
I reviewed the setting on my macihine, since as part of development inorder to reference the dll i added this to the C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies location so that i can reference this from BIDS. I checked that location in my test
server, i was not present. This location was present in the D: drive ( i assume this was present since i installed my complete SQL Server in the D:\ ). I copied the dLL in that location and added it to GAC from that location. My package still failed with the
To resolve this issue, i created the same path in the C:\ folder as C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
assemblies was newly created in C: and i added the dll to GAC from there. Now my package worked.
I'm finished with a part of my ASHX handler and need to test it against the software that'll be calling it using HTTP POST. The software required an https url so I created an internally hosted site in IIS and published the project there.
Question now is how do I do any debugging on the script to see what data is coming out of it before the data goes back into the software that's calling it? Do I set something on the project itself to be able to step into the published DLL?