IT:AD:WebDeploy:HowTo:Publish Databases

(UP)

Summary

Process

IMPORTANT: Publish from VS is intended for deployment of the Db only the first time.
IMPORTANT: There is no incremental delivery story src
Would require AD account to have SQL server rights on the db server
Resources:
- MSDN
First Time Deployment:
- In VS > Solution Explorer > Project Node > Properties > SQL Settings
- Select the Build (Debug, Release, etc.)
- Easiest way to fill grid is use Import from Web Config
- IMPORTANT: For redeployment scenarios uncheck the Deploy checkbox to not resend anything you don't want
- Select a Row/Db
  - Enter the ConnectionString to use during deployment
    - This may be different than runtime connection string (imported from web.config) due to needing different admin UserName/Pwd…
      - TODO: Eg. Current deployer's account? But isn't that already being passed through?
    - IMPORTANT: By default imported connection strings are also set to automatically generate a script to create Structure of remote db based on connection string found in local dev connection string.
      
      IMPORTANT: Consider turning it off…
      
      Tip: for ASP.NET Db read MSDN
      
      Tip: for deployment to Azure read MSDN
      
      You can add new custom script.
      
      * Subsequent ReDeployment:
- IMPORTANT: For redeployment scenarios uncheck the Deploy checkbox to not resend anything you don't want
- IMPORTANT: In the Database Scripts grid, clear the Include check boxes (especially any for automatically generated scripts).
- Add a custom script.
  - Cool: if your script is an incremental update, as we did for GTM2 using IT:AD:SQL Server:HowTo:SQL:DDL:Deployment/Log then all updates will be incrementally applied, safely.