Hi ,
I am beginner in Enterprise, When i deploy tables from Datasource DS to staging .
Working on jet datamanger2016 —–DATA TAB
For example i have customer table in Datasource
but after deploying to staging I ham having 4 tables .
dbo.Customer L
dbo.Customer R
dbo.Customer M
dbo.Customer V
is this normal????.
Date
Votes
1 comment
-
Jet Reports Historic Posts Hi Jouhayna,
When you deploy a staging- or data warehouse table from the Jet Data Manager, a number of physical tables will be created.
The two primary tables are:
_R is the Raw table, that contains the records as they where extracted from the data source, with eventual lookups added.
_V is the Valid table, that contains the records as they are after the data cleansing and data quality process has executed.
It is possible to avoid having the Valid table if the table is not collecting history or is incrementally loaded by de-selecting "Physical Valid Table" in the Table settings screen.
On the Project Level, you can change the setting "Postfix Valid" table to ommit the _V postfix on the Valid table instances.
The reason for having data in a raw and valid instance is primarely to help test and troubleshoot transformations and secondly to avoid having to reload the raw data from the source if the data cleansing process fails for some reason. There is a truncation setting on the tables where you can choose to truncate the raw table after data cleansing. This option will, however not free any space in the database, since the space allocated will still be reserved for the table - and the space will be needed on the next load.
The two other Jet Data Manager table types are the _L and _M tables. Both of these are used for error logs of different types and severity.
Best Regards,
Ryan Paterson
BI Consultant | Jet Reports
ryanp@jetreports.com
Please sign in to leave a comment.