Can any body suggest How to deploy 32 bit operating system developed ssis packages remotely in 64 bit sqlserver ? What are the points taken care while moving packages from one enviornment to other ? forums

for deployment go with this picture tutorial: http://www.protalk.in/sql-server/steps-to-create-and-deploy-ssis-package-as-a-sqlagent-job/ and for issues with 64bit-32bit, read this article from todd: http://toddmcdermid.blogspot.com/2009/10/quick-reference-ssis-in-32-and-64-bits.htmlhttp://www.rad.pasfu.com

in your you say 1- how to deploy and in the scond part you say 2- how to move ------------------------------------------------------------------------------------------------------------------------------------------------ for deployment I had a case that i was hot allowed in the customers Production server and we had to do deployment through someone within the cilents production server that knew nothing about SQL server and most of all we had to make sure that it would work, without running anything what i had to deploy was 1- had to make folders on the production server 2- set the right XML config files for the package 3- I used a file base package, so basically i had to copy the packageon to a folder 4- I has to run few scripts becase it was needed for the ETL andmake sure that they ran 5- I had to make jobs through scripts 6- etc.... what i did is used a batch file you need to know 1- sql server name 2- db name 3- folder root, having the right access and permission and etc... 4 - etc... what i did 1- made my xml config file ready with the right sql server name and db name in it 2- in the batch file use the mentione to make folders MD %FolderName%\LogFolder MD %FolderName%\LogFolder\SQLJob MD %FolderName%\LogFolder\Deployment MD %FolderName%\ToBeProcessed MD %FolderName%\PackageAndConfigFile MD %FolderName%\Sample 3- to copy files and like packages and xml config file use XCOPY "%CurrentFolder%\PackageAndConfigFile" %FolderName%\PackageAndConfigFile /e/y XCOPY "%CurrentFolder%\Sample" %FolderName%\Sample /e/y 4- to run scripts use sqlcmd -E -S %SQLServerName% -i "%MainScriptFolder%\0010_script1.sql" -o %DeploymentFolder%\0010_script1.txt and the 0010_script1.txt will provide a report in text to say that if the script failed 5- one of the scripts had the job script with the right folder name for the package and etc... settings 6 - at the end i'd ask the deployer to copy me back the folder that contained the scripts report (files with *.txt, i.e 0010_script1.txt) --- what you need to do is to have all the files ready , test it as you have everything onthe production desktop and you are running the batch next step will be to be able to do this remotely ------------------------------------------------------------------------------------------------------------------------------------------------ for move it all depends how you have set your package , and the xml config files the SQL job, what type of source data you have ? are they Excel, then still on a 64 bit server you will still have to call the package in a 32bit exec file, it can go on and on for ever i am just going to point few things out not in order 1- edit all config xml files to map the new production settings, like server name db name , SMPT , etc... 2- you may have to install the 32bit exec file to call packages that still have to be in a 32 mode can be in folder like ... chek the x86 SET @JobCommand = '"E:\Program Files\Microsoft SQL Server (x86)\90\DTS\Binn\DTExec.exe" ' SET @JobCommand = '"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" ' 3- if you have step 2 you have to call your packages like ... as scripted in a sql script SET @JobCommand = '"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" ' SET @JobCommand = @JobCommand + N' /FILE ' + @MainFolderPath + '\PkgName.dtsx ' SET @JobCommand = @JobCommand + N' /CONFIGFILE ' + @MainFolderPath + '\SSIS-XmlDestinationDBConfig-pkgName.dtsConfig ' 3- check the other steps that is calling a SP check the db names 4- move the jobs to a new server, your jobs may have a file as a history check folder and path 5 Good luck Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Thank you all.forums