Comments
Sort by recent activity
link is broken / comments
link is broken
I've just come across this issue again, and the salient part of this problem (that may not be clear from the above) is that this issue occurs in the BUILD task (rather than the release task) - So the pre-deploy script has to be valid for an empty database (ie a database with no objects in it) / comments
I've just come across this issue again, and the salient part of this problem (that may not be clear from the above) is that this issue occurs in the BUILD task (rather than the release task) - So ...
pre-deployment script? insert into dbo.x values ('y') The above statement fails during the build phase - because the db has no objects in it when the pre-deploy is execute. Why use the pre-deployment script for this? There is nothing explicit in your documentation (that I've found) that states what should not be included in the pre-deploy I personally don't think I would the pre-deploy for this - but I can imagine use-cases that might require it, I'm just trying to find the explanation why this pattern failed for one of my developers (who has updated to use the post-deploy) - and if it is required - the work around (ie - test for existence)
/ comments
pre-deployment script? insert into dbo.x values ('y')The above statement fails during the build phase - because the db has no objects in it when the pre-deploy is execute.Why use the pre-deploymen...
OK - it seems your explanation is what actually happens (and my original hypothesis was wrong) - but the logic still causes issues. if the temp db is created first - it will be empty The pre-deploy script will run - if it references any object in the database, it will fail the schema will be updated to the latest version post-deploy... Which I think now answers my question, and raises other issues - please confirm if the pre-deploy references any object, you have to check for existence of that object before using it in the pre-deploy, whether it be a table, proc, view etc, just so the build step will work... is that in the documentation anywhere you can point to? / comments
OK - it seems your explanation is what actually happens (and my original hypothesis was wrong) - but the logic still causes issues.if the temp db is created first - it will be emptyThe pre-deploy ...
a little bit more information. I only had a pre-deploy script when I came across this problem. I moved the script to the post deploy and the build was successful. I can see the temporary database was dropped after the post deploy ran. Could it be a bug in Redgate SQL Change Automation: Build that occurs only when there is a pre-deploy script? / comments
a little bit more information. I only had a pre-deploy script when I came across this problem. I moved the script to the post deploy and the build was successful. I can see the temporary data...
raised suggestions https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/40509724-ignore-failing-jobs-using-regex / comments
raised suggestions https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/40509724-ignore-failing-jobs-using-regex
raised suggestions https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/40509724-ignore-failing-jobs-using-regex / comments
raised suggestions https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/40509724-ignore-failing-jobs-using-regex
Hi Robyn, I cant locate the Disks by Projected increase table (or specifically a table with that title)? I assume this is the table on the page i mentioned originally, which is useful, but disjointed when trying to investigate the alert... (I have raised a suggestion here) I have found that if you're mainly concerned about database size, the table at the bottom of the server detail page does show the growth (size) of each database for the time window selected. If you click the "navigate the graph to this alert" button, and are scrolled to the bottom of the screen, you can see which database(s) caused the alert to fire. you can see in the image below the growth of one specific database as the time of the alert obviously this only works if the disk in question houses database files (no good for non-db growth) [image] / comments
Hi Robyn, I cant locate the Disks by Projected increase table (or specifically a table with that title)? I assume this is the table on the page i mentioned originally, which is useful, but disjo...
This is obviously required. / comments
This is obviously required.
I agree, this is a much needed feature and would complete the package.
I'd rather run scripts for my deployments (or when generating test data for integration tests) rather than running the app as part of the build process.
strange that redgate should chose to omit this facility? / comments
I agree, this is a much needed feature and would complete the package.
I'd rather run scripts for my deployments (or when generating test data for integration tests) rather than running the app as ...