Forum Discussion
Indentity and surrogate key
I currently have a Data Warehouse in SQL Server. We have a database for staging and a database for the Data Warehouse containing dimension and facts. We use SSIS to ETL the data from legacy to staging and then to the DW. I am looking to move this into the cloud preferably Fabric.
Just trying to create fact and dimension tables and have already run into a problem :
The IDENTITY Keyword is not supported in the CREATE TABLE statement in this edition of SQL server
Surely this is funamental to how a related DW works whats the solution to work around?
Below link describes the alternatives:
Fabric warehouse is an MPP framework and OLAP (more for analytics purpose)
In case if you want a replicae of SQL server, you can leverage fabric databases rather than fabric warehouse for your use case
Hi Si_7777 you can also use this approach in Fabric Warehouses, which is what I currently use
Generate unique identifiers in a warehouse table - Microsoft Fabric | Microsoft Learn
As NandanHegde said, if you need all the functionality of an RDBMS then Fabric SQL Databases have you covered.
4 Replies
Below link describes the alternatives:
Fabric warehouse is an MPP framework and OLAP (more for analytics purpose)
In case if you want a replicae of SQL server, you can leverage fabric databases rather than fabric warehouse for your use case
Thank you for replying. I wouldnt say we need to replicate SQL server as such. I have been tasked with moving our current solution to the cloud and I asssumed Fabric Data Warehousing was the way forward. We have dimensions and facts currently using SSIS for ETL.
Hi Si_7777 you can also use this approach in Fabric Warehouses, which is what I currently use
Generate unique identifiers in a warehouse table - Microsoft Fabric | Microsoft Learn
As NandanHegde said, if you need all the functionality of an RDBMS then Fabric SQL Databases have you covered.
Hi Si_7777,
Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.
If these also don't help, please share more detailed information and description to help us clarify your scenario to test.
Regards,
Xiaoxin Sheng
