Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Package deployment through local machines Expand / Collapse
Author
Message
Posted Saturday, January 18, 2014 10:12 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Saturday, April 12, 2014 10:28 AM
Points: 313, Visits: 809
Is there a way to deploy package without logging on server? From local machine or developer machine?
Post #1532389
Posted Monday, January 20, 2014 8:01 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Saturday, April 12, 2014 10:28 AM
Points: 313, Visits: 809
Anybody?
Post #1532662
Posted Monday, January 20, 2014 8:14 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 4:18 AM
Points: 5,075, Visits: 8,914
Not enough information. File system or SQL Server deployment? And what precisely do you want avoid doing - visiting the server physically, using an RDP session, mapping a drive to the server? Is it a single package or a whole project? Does it use Package Configuration and if so where are the configuration settings held?

John
Post #1532671
Posted Monday, January 20, 2014 8:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Saturday, April 12, 2014 10:28 AM
Points: 313, Visits: 809
For new packages and old packages; package will reside in MSDB. I am trying to avoid RDP access to users to logon to server and deploy that way. I haven't tried package configuration yet. Old packages are not deployed using package configurations. To edit and deploy, is there any alternatives for developers without logging onto server?
Post #1532679
Posted Monday, January 20, 2014 8:26 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 4:18 AM
Points: 5,075, Visits: 8,914
I don't use packages in msdb, so I'm not entirely sure. Are you using a deployment manifest? If so, you sholuld be able to just specify the location of the package, in this case msdb on a certain server. If not, you should just be able to save the package to SQL Server. Try it on a test server.

John
Post #1532683
Posted Monday, January 20, 2014 3:01 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 4:13 AM
Points: 12,195, Visits: 9,143
SQL_Surfer (1/20/2014)
For new packages and old packages; package will reside in MSDB. I am trying to avoid RDP access to users to logon to server and deploy that way. I haven't tried package configuration yet. Old packages are not deployed using package configurations. To edit and deploy, is there any alternatives for developers without logging onto server?


Packages should be developed locally using Visual Studio.
When they are ready to be deployed to the server, you can use dtutil to deploy them.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1532797
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse