PoshSSDTBuildDeploy
PoshSSDTBuildDeploy copied to clipboard
RichieBzzzt
Make use of Deploy Report
Deploy report is a useful document that can be generated in isolation of diff script. In order to review potential issues (such as index rebuilds) we should shred the demo document created to find anything we wouldn’t necessarily want to see and perhaps raise a warning and potential fixes (ie use refactoring in ssdt and include the refactor log)
I’m going to write a sample of what I’m thinking as maybe a blog post, perhaps forking this. I think there’s lots of scope for using the deploy report as an alternative to creating the diff script and reading through: could report changes as a table in PowerShell maybe?
Sample idea written here - https://github.com/RichieBzzzt/PoshSSDTBuildDeploy/pull/26
I know I often use the deploy report before generating a script or making changes to production. It's a good high-level overview of what will change.
I’m in two minds as to whether to close this issue or not as it’s sort of done. But at the same time I’m wondering if it people would be interested in being altered of certain operations or alerts (ie raise warning if a tablerebiild operation is included.)
https://bzzzt.io/post/2018-06-15-poshssdrbuilddeploy-warnings-improvement/
Knowing that a table rebuild is going to happen would be of interest to me. Same for any sort of change that would drop/recreate/revoke/grant things along the way. SSDT definitely can get some funny ideas about what needs to be done to get things to match. We had a long-running battle with it wanting to completely rebuild a table central to our database that would have caused all sorts of issues had it "just run".