January 18, 2017 at 10:02 am
I have no problem finding articles and FAQ's on deploying SSIS 2014 projects from your local machine. However, I can't find anything on making it part of the TFS build/deploy process. What gives? Surely, Microsoft doesn't expect large scale projects to be deploying these outside of the mechanism that they've been funneling all of these procedures through for the last 10 years, right?
January 18, 2017 at 1:06 pm
I don't believe this can be done without some sort of scripting effort such as around dtutil.
K. Brian Kelley
@kbriankelley
January 18, 2017 at 1:13 pm
K. Brian Kelley - Wednesday, January 18, 2017 1:06 PMI don't believe this can be done without some sort of scripting effort such as around dtutil.
Probably. but is that the best way? Is that the recommended way? There's next to no documentation on this.
January 18, 2017 at 1:42 pm
TheGreenShepherd - Wednesday, January 18, 2017 1:13 PMK. Brian Kelley - Wednesday, January 18, 2017 1:06 PMI don't believe this can be done without some sort of scripting effort such as around dtutil.Probably. but is that the best way? Is that the recommended way? There's next to no documentation on this.
I use a Powershell script. I don't recall seeing a 'recommended' way anywhere, so suggest you use whatever works best for you.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 20, 2017 at 7:32 am
Andy Leonard (former SQL Server MVP) doesn't frequent these forums much, but I would ask him if he knows a better way as I know he does DevOps with SSIS a lot. He's on Twitter as @andyleonard. You can tweet there, using #SQLHelp and specifically tagging him. Or you can find his blog at sqlblog.com.
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply