How can we help you today? How can we help you today?
PeterDaniels
Activity overview Badges (0) Posts (25) Comments (63)

Comments

Sort by recent activity
Thanks, @way0utwest. I've discovered that my SQL 2014 model database had my domain account as a db user, so it was seeing any "empty" target dbs as not empty, and therefore marking the baseline script as deployed. This made the project error on deployment. Not sure how the user got into the model db - perhaps during instance install, because I definitely didn't put it there. Thus, I used the techniques described above to ensure that the baseline script gets deployed. Other option was to remove that user, and SCA saw the target as empty. Since I don't know exactly how SCA determines l "empty", I'm keeping the skip property in place for now. In other news, I ended up just manually scripting the ddl and dml to get the project delivered to the ops DBAs, including the road in the __migrationLog table. Hoping I can return to SCA based deployment artifacts again. / comments
  1. Community
  2. SQL Change Automation
  3. Best way to introduce SCA deployments to ops DBAs?
Thanks, @way0utwest. I've discovered that my SQL 2014 model database had my domain account as a db user, so it was seeing any "empty" target dbs as not empty, and therefore marking the baseline scr...
0 votes
@way0utwest - would you be willing to respond to my last question por favor? / comments
  1. Community
  2. SQL Change Automation
  3. Best way to introduce SCA deployments to ops DBAs?
@way0utwest - would you be willing to respond to my last question por favor?
0 votes
Thank you, @way0utwest .  To clarify, are you suggesting taking the "1.0.0-Baseline" script and deploying that initially.  Then use the PS cmdlets (New-DatabaseReleaseArtifact) to generate the TargetedDeploymentScript.sql moving forward?  Edit: I've been using a combination of unchecking "mark first folder as baseline" + adding <SkipBaselineCheck>True</SkipBaselineCheck> to get New-DatabaseReleaseArtifact to include the whole set of migrations to deploy correctly to a newly created DB. Otherwise, it errors.  The original "target" db used during project creation to injury the baseline script had a number of initial schema objects. / comments
  1. Community
  2. SQL Change Automation
  3. Best way to introduce SCA deployments to ops DBAs?
Thank you, @way0utwest .  To clarify, are you suggesting taking the "1.0.0-Baseline" script and deploying that initially.  Then use the PS cmdlets (New-DatabaseReleaseArtifact) to generate the Targ...
0 votes
Thanks, @way0utwest.  I like the way you're thinking and agree with the concept.  However, I have a current, real project with a new DB that I've chosen, wisely or otherwise, to manage using SCA.  So, now it's time to promote to the higher environments (above QA), and I'm scrambling to prepare for the handoff to the ops DBAs.  I guess worst case is I just generate DDL and DML and hand that off, losing the benefits of tracking changes with the __MigrationLog, snapshots/drift/change reports, etc. / comments
  1. Community
  2. SQL Change Automation
  3. Best way to introduce SCA deployments to ops DBAs?
Thanks, @way0utwest.  I like the way you're thinking and agree with the concept.  However, I have a current, real project with a new DB that I've chosen, wisely or otherwise, to manage using SCA.  ...
0 votes
Perfect.  Thanks guys.  The online docs were a little funky, so I went about it by: 1) Created a new empty dev DB on localhost 2) Created a new project, connected to the new DB for dev, but did not connect to a "target" DB (where I want to grab the <Prefix>_% tables from.) 3) Started a new SQL compare project and chose source as the "target DB", target as my empty new localhost dev DB. 4) Compared, then under actions, chose "filter setup pane" 5) created a custom filter: object_name like <Prefix>_ 6) Saved the filter.scpf into the root folder of my project 7) closed and reopened the solution 8) Continued with "setup the project" and imported the baseline script.  BINGO! Looks good.  I only have those objects in the project. [image] / comments
  1. Community
  2. SQL Change Automation
  3. Partial project using table name prefix?
Perfect.  Thanks guys.  The online docs were a little funky, so I went about it by:1) Created a new empty dev DB on localhost2) Created a new project, connected to the new DB for dev, but did not c...
0 votes
No, I'm not seeing a warning or error in the deployment log.  Here's the PS code for the inline PS Script task in my Bamboo deployment project: <div>$ErrorActionPreference = "Stop"</div><div><br></div><div>#Will this set the release_version in the __MigrationLog table?</div><div>$ReleaseVersion = "${bamboo.deploy.release}"</div><div><br></div><div>$staging = New-DatabaseConnection -ServerInstance "localhost" -Database "SCAPOC_QA"&nbsp;</div><div><br></div><div># This is where the artifact was saved during build plan:</div><div>#C:\Users\peter\bamboo-home\artifacts\plan-753665\shared\build-00031\DB_Package_Artifact\SCAPOC_Pkg.1.31.nupkg</div><div>#</div><div># Where is it saved after the "Artifact Download" task?</div><div>#C:\Users\peter\bamboo-home\xml-data\build-dir\1998849-2129921\findme</div><div>#bamboo.agentWorkingDirectory The path to the working directory on the agent. This is not the same as the Bamboo working directory.</div><div>#bamboo.build.working.directory The path to the working directory for Bamboo. This is used by both the build plan and the deployment project.</div><div><br></div><div><br></div><div>#$path = Join-Path -Path ${bamboo.agentWorkingDirectory} -ChildPath "findme"</div><div>#Get-ChildItem : Cannot find path 'C:\Users\peter\bamboo-home\xml-data\build-dir\findme' because it does not exist.</div><div># we're missing the # -&nbsp;</div><div><br></div><div>$path = Join-Path -Path ${bamboo.build.working.directory} -ChildPath "findme"</div><div>$path</div><div>$file = Get-ChildItem -Path $path -Filter *.nupkg | Select-Object Name</div><div>$buildArtifact = $file.Name</div><div>$buildArtifact = Join-Path -Path $path -ChildPath $buildArtifact</div><div>"Here is our final path - OY VEY:"</div><div>$buildArtifact</div><div><br></div><div>#$buildArtifact = Join-Path -Path $buildArtifact -ChildPath "*.nupkg"</div><div><br></div><div>$releaseArtifact = New-DatabaseReleaseArtifact -Source $buildArtifact -Target $staging</div><div><br></div><div># Makes sure the directory we're about to create doesn't already exist.</div><div>#TODO: make this look like the UAT release path logic.</div><div>$exportPath = "C:\Export\DatabaseRelease\QA"</div><div>If (Test-Path $exportPath) {</div><div>&nbsp; &nbsp; rmdir $exportPath -Recurse -Force</div><div>}</div><div><br></div><div>$releaseArtifact | Export-DatabaseReleaseArtifact -Path $exportPath</div><div><br></div><div>Use-DatabaseReleaseArtifact $releaseArtifact -DeployTo $staging</div> / comments
  1. Community
  2. SQL Change Automation
  3. How to populate dbo.__MigrationoLog.release_version column via powershell?
No, I'm not seeing a warning or error in the deployment log.  Here's the PS code for the inline PS Script task in my Bamboo deployment project:<div>$ErrorActionPreference = "Stop"</div><div><br></d...
0 votes
Since I have enterprise edition functionality in some of my migrations (e.g. Create index with online = on), I have to use a shadow db on my dev edition local SQL server instance. So I checked "always use default db for shadow" and set the default connection strong to point to "<projectName>_shadow" / comments
  1. Community
  2. SQL Change Automation
  3. How does "Always use default connection string for Shadow database" work?
Since I have enterprise edition functionality in some of my migrations (e.g. Create index with online = on), I have to use a shadow db on my dev edition local SQL server instance. So I checked "alw...
0 votes
If we have "Always use default connection for shadow" set in the project settings, shouldn't it always use that server/DB even if we connect in VS to another target? Also, I do sometimes use the VS IDE and connection to deploy the project - esp when we don't have CI set up yet. / comments
  1. Community
  2. SQL Change Automation
  3. How does "Always use default connection string for Shadow database" work?
If we have "Always use default connection for shadow" set in the project settings, shouldn't it always use that server/DB even if we connect in VS to another target?Also, I do sometimes use the VS ...
0 votes
Thank you, Sergio.  I realize it's a low priority request that may sit in the sprint backlog. / comments
  1. Community
  2. SQL Change Automation
  3. Can we change the output of Changes.html to NOT included previous column with just a comma added?
Thank you, Sergio.  I realize it's a low priority request that may sit in the sprint backlog.
0 votes
Excellent! And thanks for updating the online docs.  I'm really enjoying how responsive the RG team has been.  I think your'e right - File Path ordering might be appropriate for this situation.  As a supporting "Dev DBA", I don't want to impact the dev team's traditional sprint/release naming convention (much) at this point. / comments
  1. Community
  2. SQL Change Automation
  3. Are we restricted to only using alpha characters when using semantic version migration grouping?
Excellent! And thanks for updating the online docs.  I'm really enjoying how responsive the RG team has been.  I think your'e right - File Path ordering might be appropriate for this situation.  As...
0 votes
Total activity
113
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
25