{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 仙女界的扛把子 的问题《Deploy SSIS Package with SQL Server Authentication》','https://www.manongdao.com/q-1005218.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am working with SSIS 2008. My package has two connections (both are SQL Server Authentication). One is source connection and other is destination. I want to deploy this package in SQL Server and have a SQL job run this package. I need a installer for this as well so that the package can be installed on any machine. I am not sure how to expose the connection strings and what would be the best way to do this.
Thanks.
One solution I have used in the past for easy deployments has been BIDS Helper.
BIDS Helper
May not be exactly what you need, but once your package is deployed, you can setup a SQL Agent Job to execute the package on a regular schedule.