Date: Fri, 29 Mar 2024 08:29:18 +0000 (GMT) Message-ID: <225338028.615.1711700958714@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_614_108314800.1711700958710" ------=_Part_614_108314800.1711700958710 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Re-brand the product as Redga= te ReadyRoll (Details)
Script Verification Helper (= span>Details)
Problems often arise at this stage if the script that was generated by R= eadyRoll causes SQL Server to throw an error. These errors often stem from:=
Resolving the above errors may involve a number of different steps, depe= nding on the cause of the issue.
To help you resolve these kinds of errors, we=E2=80=99ve added a new dia= log within the ReadyRoll DbSync tool that appears when you encounter an err= or during the verification process.
This tool is displayed if an error occurs when you attempt to execute yo= ur script against the Shadow database. To resolve the issue, do on= e of the following:
Click Undo import to remove the gene= rated script from your project and allow you to un-check any object(s) that= may have caused the error
Click Open script to open the affect= ed migration script and fix the syntax errors manually
Click Re-verify script to attempt to= execute the script again; useful if you suspect that the underlying issue = was temporal (e.g. a timeout error), or if you have subsequently fixed the = issue through manual script changes
Today=E2=80=99s release focuses on simplifying some key concepts within = ReadyRoll.
In ReadyRoll 1.12, we've changed the terminology used in the produc= t to make it easier to understand.
Old folder name (1.11 and earlier) | New folder name (1.12 and later) |
---|---|
Pre-Deployment | Pre-Deployment |
Deploy-Once Migrations | Migrations |
Deploy-Change Migrations | Programmable Objects & Additional Scripts |
Post-Deployment | Post-Deployment |
These changes don't alter the behavior of script deployment. Existi= ng projects containing the Deploy-Once and Depl= oy-Change folder structures are not affected, and you don't have = to rename them unless you want to.
Projects created before 1.12 will still use the old Deploy-Once= / Deploy-Changes style folder structure. If y= ou want to use the new folder names, you can migrate your existing projects= . To do this:
.sqlproj
file in a text editor.Find the <DeployOnceSubFolder>
element =
and replace it with:
<Depl= oyOnceSubFolder>Migrations</DeployOnceSubFolder> <DeployChangesSubFolder>Programmable Objects</DeployChangesSubFold= er>
.sqlproj
&nbs=
p;file.If you want to carry on using the old folder structur= e for ReadyRoll projects you create after installing 1.12:
Open your .sqlproj
file in a text editor.
Find the <DeployOnceSubFolder>
element =
and replace it with:
<Depl= oyOnceSubFolder>Deploy-Once</DeployOnceSubFolder>
Find the <DeployChangesSubFolder>
eleme=
nt and replace it with:
<Depl= oyChangesSubFolder>Deploy-Changes</DeployChangesSubFolder>
.sqlproj
file.