see below...
[quoted text, click to view] "swetha" wrote:
> Hello All,
>
> I have a list of topics/ questions I require help in understanding.
>
> Can we make an .exe file of the projects?
Yes, however it is called a Deployment Manifest
[quoted text, click to view] > How do we install the project at a customer site?
Go to Project | Properties, under 'Deployment Utility' set the
CreateDeploymentUtility property = True. Then Build project, this will create
the Deployment Manifest in your bin\Deployment folder by default. Copy files
to production server, double click Manifest to install.
[quoted text, click to view] > How to move the projects between different drives( From c: to d: or
> e:)
You referring to BIDS project files? Move all project files to seperate
folder, double click on sln or dtproj file to open in BIDS.
[quoted text, click to view] > How do we move or install SSIS jobs on a production server?
ONce installed, create a new SQL job - create new Step of type SSIS Package
[quoted text, click to view] > How do we launch SSIS jobs from production server?
job schedule
[quoted text, click to view] > Do we need to install BIDS at the production site for doing the SSIS
> jobs?
No - SSIS service does need to be running. Best to use Windows Auth when
connecting to data sources/dest - use a privileged account to run service.
Also, turn on logging - difficult to troubleshoot problems w/out, job history
gives no details...
[quoted text, click to view] > Can we create a web based interface to launch SSIS jobs on production
> server?
Sure - asp.net app, use SMO to launch SQL Job
I suggest reading BOL
Regards,
Chris MCDBA MCSE OCP
www.MSSQLConsulting.com [quoted text, click to view] >
> Kindly mail me your suggestions. Any and all are most welcome.
>
> Thanks in advance.
>