|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Parameterizing an SSIS packageI have created an SSIS package, but I need to be able to hand it over
to someone else to run on a server whose name I don't know, and I don't know the database, user, or password either. If this was a command-line SQL script, then I could use command-line parameters for the server/user/password, but I'm not sure what the options are for an SSIS package. Is there any other way than the user opening up the package in Visual Studio, double-clicking on the OLE DB Source component, and adding a new Connection Manager entry with the server/db details in it? I don't want the user to have to select the table from a huge drop-down list in order to get the package working; specifying what table to extract is my job as a developer, and I can't see any way of making the table name persistent when the server details have been re-entered. Phil. Search books online for deployment packages. Although it will be far cheaper
for the client to simply allow you to configure it on his machine. Unless they are quite technical, they are going to have to let you configure it for them. Show quote "PhilHibbs" <sna***@gmail.com> wrote in message news:1193306083.605390.143490@y42g2000hsy.googlegroups.com... >I have created an SSIS package, but I need to be able to hand it over > to someone else to run on a server whose name I don't know, and I > don't know the database, user, or password either. If this was a > command-line SQL script, then I could use command-line parameters for > the server/user/password, but I'm not sure what the options are for an > SSIS package. > > Is there any other way than the user opening up the package in Visual > Studio, double-clicking on the OLE DB Source component, and adding a > new Connection Manager entry with the server/db details in it? I don't > want the user to have to select the table from a huge drop-down list > in order to get the package working; specifying what table to extract > is my job as a developer, and I can't see any way of making the table > name persistent when the server details have been re-entered. > > Phil. > Please read this article, it should answer the questions you have:
http://www.sqlmag.com/Articles/ArticleID/47688/47688.html?Ad=1 Also recommend a book by Kirk Haselden on SSIS. Regards, Maciek Sarnowicz Show quote "NigelA" <discussion@microsoft.newsgroups> wrote in message news:#Soaef#GIHA.4228@TK2MSFTNGP02.phx.gbl... > Search books online for deployment packages. Although it will be far > cheaper for the client to simply allow you to configure it on his machine. > Unless they are quite technical, they are going to have to let you > configure it for them. > > > > "PhilHibbs" <sna***@gmail.com> wrote in message > news:1193306083.605390.143490@y42g2000hsy.googlegroups.com... >>I have created an SSIS package, but I need to be able to hand it over >> to someone else to run on a server whose name I don't know, and I >> don't know the database, user, or password either. If this was a >> command-line SQL script, then I could use command-line parameters for >> the server/user/password, but I'm not sure what the options are for an >> SSIS package. >> >> Is there any other way than the user opening up the package in Visual >> Studio, double-clicking on the OLE DB Source component, and adding a >> new Connection Manager entry with the server/db details in it? I don't >> want the user to have to select the table from a huge drop-down list >> in order to get the package working; specifying what table to extract >> is my job as a developer, and I can't see any way of making the table >> name persistent when the server details have been re-entered. >> >> Phil. >> > >  |
|||||||||||||||||||||||
Other interesting topics