How-to: Bring your own data warehouse to Microsoft Dynamics 365 for Operations
Many customers have an existing data warehouse where Microsoft Dynamics AX ERP data constitutes a fraction of the share and non-ERP data constitutes a larger share. In such situations re-architecting the whole data warehouse may be infeasible. Customers would need AX data in their own data warehouse, which is why Dynamics 365 for Operations supports the option to bring your own data warehouse (or BYODw - not yet an industry acronym, but it will be).
When would a D365 for Operations customer opt for BYODw, when the customer can leverage the entity store (AXDW) out of box for all reporting based on AX data? If they have their own data warehouse and need information from D365 Operations, then they need to choose BYODw.
Using D365 for Operations (AX), you can export data to an Azure SQL database and then pull the information from there to your own data warehouse.
Below are high-level steps to achieve this extraction of information from D365O into your own data warehouse.
First we would set up an Azure SQL server with an active subscription:
Then we would create a new Azure SQL Database. Note the connection details:
We can browse data in the in-browser SQL Database Query Editor (now in preview in the Azure Portal), and/or using the SQL Server Object Explorer in Visual Studio.
Next we open a Data management workspace in D365 for Operations:
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here