And what would I do when there are changes by Microsoft on the PL-300 materials? The benefit of getting rid of one database would not justify the effort to go through all the materials and check what the consequences of the changes are. I’m using PL-300 lab-materials purely for teaching. With this insight, I stopped my activities. And indeed, there are much more, like it can be seen in the following screenshot: Comparison AdventureWorksDW2020 to AdventureWorksDW2022 But then I looked at potential further changes that were not so obvious. I thought about copying the table from DW2020 to DW2022. Attention, it is renamed to SalespersonRegion: Adventureworks SalespersonRegion It is used to demonstrate advanced relationships, like shown in the following screenshot. The table DimEmployeeSalesTerritory is only available in the DW2020 version. If it is important you rather stick with AdventureWorksDW2019.Ĭompatibility of DW2022 with the labs of PL-300 I just deleted some measures and attributes because the model is not so important for me. While the tabular model is only based on Internet Sales, the multidimensional one is much more comprehensive, so that more database changes apply. Trying to switch to DW2022 shows the same problems like the tabular one, plus additional errors. The datasource is named AdventureWorksDW2019, so it is clear that it is using the respective database. The multidimensional demo model is surprisingly more current than the tabular one. In the model there is another naming convention to uses spaces in between, so the resulting fields in the model should be Freight Amount and Tax Amount.Ĭompatibility of DW2022 with the Analysis Services Multidimensional demo model There are yearly partitions defined, by using the order date.įor example: WHERE (( >= N’ 00:00:00′) AND ( < N’ 00:00:00′))Ĭhanging the queries would not have been a big thing, but I just got rid of the partitions to avoid this work.Īlso this makes sense to follow naming conventions of other fields. The only use was in the partition definitions. In the model, the deletion of the fields was not a problem. The reason seems clear to me: there were already and currently there are foreign key fields (OrderDateKey, DueDateKey and ShipDateKey), so the deleted ones were redundant. Then the switch to DW2022 caused some issues due to changes in the schema of table FactInternetSales. In a first step, for curiosity, I pointed the datasource to DW2019 (I don’t even have an older one) and rebuilt. The compatibility layer is SQL 2016 (1200) and the readme talks about AdventureWorksDW2014. In contrast to the multidimensional model, the tabular demo model seems to be a little bit outdated. The tables that are not listed (of course still the majority), are existing in all three databases: Table Nameĭbo.FactAdditionalInternationalProductDescriptionĬompatibility of DW2022 with the Analysis Services Tabular demo model If there is no number, the table doesn’t exist (so you see that both DW2020 and DW2022 are simplified). Numbers in the tables are number of records. In this current situation, the differences in the schema (existing tables) are as follows. Or am I just seeing chaos where no chaos is and the story is simply:ĪdventureWorksDW2019 -> AdventureWorksDW2020 -> AdventureWorksDW2022 Hmm, the name AdventureWorksDW2022 is already taken…ĪdventureWorksDW2019 -> AdventureWorksDW2020 -> continued for PL-300ĪdventureWorksDW2019 -> AdventureWorksDW2022 -> continued for DP-500ĪdventureWorksDW2019 -> another AdventureWorksDW2022 for SQL 2022 ? -> ? However, AdventureWorksDW2022 is still a simplified version if AdventureWorksDW2019, so it is unclear whether there still will be an additional branch for newer versions of SQL Server like SQL Server 2022. See the versioning information within the databases: Database FactSalesQuota) that were removed in AdventureWorksDW2020, so it is rather a branch from AdventureWorksDW2019 than from AdventureWorksDW2020. The new certification DP-500 “Azure Enterprise Data Analyst Associate” uses another version: AdventureWorksDW2022. It is the basis for the labs of the Power BI certification PL-300 “Power BI Data Analyst Associate”. With the creation of learning content for DAX and Power BI, Microsoft created a somewhat simplified version and named it AdventureWorksDW2020. So the latest version of the datawarehouse (and I’m not interested in OLTP) is AdventureWorksDW2019. They are versioned according to the SQL Server (on premises) version schema, which is basically the year (there used to be a 2008R2, but this naming schema wasn’t used any more). There is a data warehouse version (DW), an OLTP and a light OLTP (LT) version. AdventureWorks is one of the standard demo models from Microsoft for SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |