new

improved

fixed

accoONE-DB v2.0

Latest accoONE-DB version is now available for production use at new customers. The significant change in this version is that schema names have been updated to give a more intuitive flow when developing with accoONE-DB
Schema Name Updates
Schema names are upgraded accordingly to our new naming and flow through accoONE-DB v2.0. The old schema names which are migrated are shown in the table below.
2022-11-29 15_36_46-accoONE-DB Schema Naming Upgrade Process - Word
See official documentation for further details on schema usage.
Note. To better reflect naming and usage, [accoDEV].[sp_PostExtract] is now renamed to [accoDEV].[sp_UpdateModel] which is to be run after a developer has made any changes to extModel or stgModel schemas.
Azure Data Factory Execution changes
Our standard Pipelines and datasets in ADF is upgraded to V2.0. Most notable change is that instead of foreach execution of internal accoONE-DB stored procedures, these are now batches based on number of threads. This improved cost and performance on AzureSQL solutions.
The pipelines now support multiple developer databases on the same Azure SQL Server. Uses DB_Name parameter with corresponding Key Vault secrets. Default value is accoDW to allow for an easy upgrade.
SSIS
SSIS packages are also updated to use the new schema naming.
Bugfixes
  • Fixed issue with accoDEV.sp_CleanViews when using @Table_Name and @Schema_Name parameters
Updated Documentation
accoONE-DB documentation is updated with new illustrations and descriptions.
Guidelines for upgrading existing customers is maintained in accoONE-DB Schema Naming Upgrade Process.docx. Contains process description but also documentation on the procedures for automatic upgrade of existing objects to v2.0. Contact your primary consultant if this document is needed.