The accoONE-DB has been rewritten to be based on a common data model, where the data lineage flow for the accoONE-DB is located. This means that you can track what happens to e.g. a extModel view throughout the data warehouse flow.

This enables more advanced automations, as it simplifies the way automatic objects are created. Furthermore it enables isolated data warehouse runs for e.g. a fact or dimension with their dependencies, without running the entire data warehouse flow.

The following features has been developed on top of this:

Dimensions are consolidated in the the stage layer in a new schema called stgConsistency. Facts are consilidated in DW views, with autogenerated UNION ALL statements.

To keep a clean structure a dedicated schema for consolidated data sources and persisted stgModel views has been created named - .

This new upgrade introduces a more streamlined data structure, significantly reducing complexity. By optimizing data source and module control, the update ensures that redundant tables are automatically excluded, resulting in enhanced system performance, especially for BIaaS products.

DataSource#Id column is automatically added to all CLEAN views. Using the DataSource table in eConfig. This is useful in multi source solutions.

Added support for Standard Scaling parameters to differentiate triggers

Added support for persisting StgModel views before transfering to DW. This enhances performance on facts which are consolidated from many sources or has many relationships to Dimensions

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 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.

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.

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 packages are also updated to use the new schema naming.

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.