DataStar Release: 1.5.0.34¶
Release Date: 16 November 2018
Please note DataStar.CmdLine is also available via the Azure Dev Ops Marketplace packaged as a VSIX file. This can be installed into Azure Dev Ops or Team Foundation to provide access to a packaged task or alternatively unzipped to extract the DataStar.CmdLine binaries.
Upgrading¶
To upgrade from the previous release the following table changes can be made to the deployment audit tables, these are recommended but optional amendments (the software will continue to work if these changes are not applied)
Audit Table¶
Add a status column to the deployment history table:
Summary Table¶
Create a new table to hold the data deployment summary:
CREATE TABLE [dbo].[ADS_DEPLOYMENT_SUMMARY] (
[ID] [int] NOT NULL,
[TABLE_NAME] [nvarchar](255) NOT NULL,
[INSERTED] [int] NOT NULL,
[UPDATED] [int] NOT NULL,
[DELETED] [int] NOT NULL
CONSTRAINT [ADS_DEPLOYMENT_SUMMARY_PK] PRIMARY KEY CLUSTERED (
[ID] ASC,
[TABLE_NAME] ASC))
ALTER TABLE [dbo].[ADS_DEPLOYMENT_SUMMARY]
ADD CONSTRAINT ADS_DEPLOYMENT_SUMMARY_FK1
FOREIGN KEY ([ID])
REFERENCES ADS_DEPLOYMENT_HISTORY ([ID])
ON DELETE CASCADE
Enhancements¶
Id | Description |
---|---|
DAT46 | Enhancement so that rollback scripts are generated for new "object" components (i.e. when they don't yet exist in the target environment). |
DAT39 | Enhancement so that manifest files can be checked into version control from the deployment view. |
DAT40 | Merge statements now include a "withholdlock" to avoid the issue documented here, this can be disabled by setting the "UseWithHoldLock" attribute in the template xml files to "false". |
DAT43 | Upgrade of third party libraries and .NET Version to 4.6.1 |
DSCL6 | An option has been added to include a deployment summary table in the auditing feature to capture details of the data inserts, updates and deletes to avoid having to look at the actual log file. |
DSCL4 | Option to include a status column on the deployment audit table to record whether the deployment was successful or not. |
DAT42 | Enhancement so that if a file is extracted after it has been opened in the source code view then it warns you in the open document and asks if you want to reload from the generated script. |
Resolved Issues¶
Id | Description |
---|---|
DAT44 | Fix so that deleted scripts are not picked up when generating a deployment file from version control, deleted items are also excluded when updating to latest. |
DAT47 | Deletes are automatically enabled on templates when generating reversal scripts so that they are able to back-out inserts. |
DSCL3 | Fix error in the command line deployment where a missing template could cause the process to sit and wait rather then error. |