Activity overview
Latest activity by AdamBowler
$customers = Invoke-Sqlcmd -Query $databaseListQuery -ServerInstance $DatabaseServerName -Database $database Write-host "customercont=" + ($customers.length) write-host $customers $i = 1 foreach ($customer in $customers) { Write-Host "Executing script for $($customer.dbname) ($i of $($customers.length))" write-host "dbname=$($customer.dbname)" & { $DatabaseServer=$($customer.hostname); $DatabaseName = $($customer.dbname); $ReleaseVersion = $ReleaseVersion; $UseWindowsAuth = $false; $DatabaseUserName = $($customer.dbusername); $DatabasePassword = $DatabasePassword; $ForceDeployWithoutBaseline = $ForceDeployWithoutBaseline; & $PathToDatabaseScript} $i++ } / comments
$customers = Invoke-Sqlcmd -Query $databaseListQuery -ServerInstance $DatabaseServerName -Database $databaseWrite-host "customercont=" + ($customers.length)write-host $customers$i = 1foreach ($cust...
We have but that then opens up more room for error on partitioning out the database which we'd like to avoid, is there any other deployment alternatives that may decrease the length of the deployment? / comments
We have but that then opens up more room for error on partitioning out the database which we'd like to avoid, is there any other deployment alternatives that may decrease the length of the deployment?
There appears to be 5 to 10 seconds delay between the Beginning Transaction log to it executing the first script which appears to be taking up the majority of the time. / comments
There appears to be 5 to 10 seconds delay between the Beginning Transaction log to it executing the first script which appears to be taking up the majority of the time.
Sorry Mike, it appears we are using the SQL Change Automation PowerShell cmdlets, I got confused. It does only run the undeployed migrations but it is still taking a long time to run. We currently have around 100 scripts, is this too large or would you not expect this to impact performance? / comments
Sorry Mike, it appears we are using the SQL Change Automation PowerShell cmdlets, I got confused. It does only run the undeployed migrations but it is still taking a long time to run. We currently ...
Mike U said:
Whether it's significantly quicker or not depends on the size of your project (in terms of number of migration scripts and programmable objects), and how often you deploy. The patch-based method only deploys updates, so if you keep your target database reasonably up-to-date and you have a large number of scripts it should be significantly quicker.
Thanks Mike, we'll give it a go / comments
Mike U said:
Whether it's significantly quicker or not depends on the size of your project (in terms of number of migration scripts and programmable objects), and how often you deploy. The pa...
We are using the DeployPackage.ps1 that's is in the build output. We haven' tried the SQL Change Automation PowerShell cmdlets I don't believe, is it significantly quicker? / comments
We are using the DeployPackage.ps1 that's is in the build output. We haven' tried the SQL Change Automation PowerShell cmdlets I don't believe, is it significantly quicker?