I have a little application where every time I set this up, I have to do the following things: Deploy a few SSIS packages and configure some settings Create tables on the SQL Server Upload reports to the Report Server Since this process is very similar every time, I'd like to create a user-friendly wizard kind of thing, that I start an exe/msi or whatever, and in the setup process I provide the details of the server, report server URL etc. The setup process will then execute the above steps automatically. Right now I'm doing this with a separate SSIS package where I set the variables and when I run it, the above steps (except for the upload of the SSRS reports) are executed. It would be nice to have something like a more user-friendly setup process. I'm using SQL 2008 so I was wondering if I could build something like that in VS 2008 using the appropriate namespaces for the connection. Thanks. -

what is have is a little bit more complicated that what you have but it works perfectly this answer is for SSIS packages and Creating tables only ( not for SSRS) ---> story short, i have to deploy the package , set the XML config files , make some folders , run some scripts , make a SQL job and etc.... AND my biggest problem is that i can't loging to the customers production server, so i have to made some kind of a deployment set wizard or something like that , and another problem is that the person deployning it havs no knowledge about SSIS and etc.... WHAT ID DID .... I use a simple *.BAT file to do all of it for me, my deployment time is 9seconds wha the use has to do is to copy the file and folder on the desktop and double click on the BAT file and thats it. ----------------------------------------------------------------------- 1- to make the folders and etc... in the bat file i use REM ----------------------------------------------- REM Making the folder of the destination production REM ----------------------------------------------- MD %FolderName% REM CD %FolderName% MD %FolderName%\LogFolder MD %FolderName%\LogFolder\SQLJob MD %FolderName%\LogFolder\Deployment MD %FolderName%\ToBeProcessed MD %FolderName%\PackageAndConfigFile MD %FolderName%\Sample -------------------------------------------------------------------------- 2- to run scripts i use .... and make a log to see it the fail, in each script i have USE the right DB name (ie USE [MyDB];) so that nothing goes wrong sqlcmd -E -S %SQLServerName% -i "%MainScriptFolder%\0010_tblXYZ.sql" -o %DeploymentFolder%\0010_tblXYZ.txt <--- Log result ------------------------------------------------------------------------- 3- for SSIS package for this cistomer i have a file base package and i rebuild the package on my PC and set the XML config files on my PC, I have to know the HOSTING (production) information like the SQL server name , the backup folder name and etc.... so that i can set my XML conf file XCOPY "%CurrentFolder%\PackageAndConfigFile" %FolderName%\PackageAndConfigFile /e/y and i simply copy my preReady SSIS and xml files to the right location "MD %FolderName%\PackageAndConfigFile" ------------------------------------------------------------------------------- ONE big rule for deployment is HAVE A STANDARD for your self. 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).

Without knowing the details how you deploy (e.g. to a file system) it is hard to come up with a general solution. I normally resort to scripts, a more user friendly version of scripts would HTML enabled HTA applets. Introduction to HTA http://msdn.microsoft.com/en-us/library/ms536496(v=vs.85).aspx Arthur My Blog

Without knowing the details how you deploy (e.g. to a file system) it is hard to come up with a general solution. you have to know the details, like the production SQL server name, and the shared folders, and the ETL folder location and etc, the customer must provide you these information. and it's not hard to come up with a general solution as long as you have a general standard i designing the ETLs and etc... ie. for my XML config i have 4 types of XML config 1- SourceConfig 2- DestinationConfig 3- EmailConfig 4-FileAndFolderConfig yes some cases i have to make a realy realy customer ETL that needs a different *.BAT and settings, anyways i have been doing this for the past 3years and never had a problem with it my last suggestion is to write a step by step deployment documention (which you will have to have in the first place) and hand it over to the person who is deploying everything, in my case it was a 21 page documentaion just for the deployment. good luckSincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

I normally resort to scripts, a more user friendly version of scripts would HTML enabled HTA applets. Introduction to HTA http://msdn.microsoft.com/en-us/library/ms536496(v=vs.85).aspx that is a very good idea i like it a lot. thanks for the linkSincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).