Solved

Change schema in Data Export

  • 23 February 2023
  • 3 replies
  • 81 views

Hi,

The current Data warehouse has tables with two different DB schema's. There are already PowerBI Dash-boards using these schema's. Now I want to use the Semantic layer to copy the data (Data Export) to a SQL serverless DB. Everything works fine but I want to override the schema name. In the Semantic layer I have not find any options to change this. Is that correct or is there a way like in the Dataware house layer to change the schema?

icon

Best answer by Christian Hauggaard 24 February 2023, 11:55

View original

3 replies

Userlevel 6
Badge +5

Hi @Lorenzo 

Is there a particular reason why you are using the data export SQL feature rather than adding a new SQL data warehouse and bringing the table in there as a simple mode table? This second option will allow you to control schema

I currently do that but the reason for using the semantic layer was:

  • Cost saving: We are processing on the Azure VM server with SQL installed. CPU, disk space is already paid for. The end step is to provide the data to Serverless SQL DB. By this avoiding to use processing power on the Serverless SQL DB and so saving costs. 
    But in this case because all processing is already done in the DW layer, copying the tables as a simple mode table to the serverless DB does not give additional costs.
  • I thought this was the way of working within TimeXtender. Using the data export to provide the data to the “outside” world. When that is not the case, could you explain why this option for SQL data export is in there?

In my case I will continue using the solution I have, that is as last step copy the data as simple mode table to the Serverless DB.

Userlevel 6
Badge +5

We no longer have the SQL data export feature in the latest version (it has been deprecated). At the time we released it, I am not sure if simple mode was available. Furthermore, I believe the permissions required for the data export are less, so that might have been a possible use case

Reply