Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Experts,
I wanted to know the use of Binary load in a Three Tier architecture in a production environment.
Source Data--> QVD generator(QVW)-->Base QVD file--> QVD Generator(QVW)-->Transformed QVD--> Final QVW.
I am aware of the usage of binary load statement, but where does it fit in this architecture? and
what could be the requirement to use it?
Regards,
Suraj
Well... The binary load is an option.
For instance, once you have your Transformed QVD you may use those qvd's as final sources for the aplication, so in this case you can go without the binary load. However there are some times when may want to create a data model that may serve as source for several apps. In this case, you may create a qvw that will apply some filters to load the transfromed qvd (for instance just load certain the last 3 years althought you have 10 years of information), then the application with the graphics will use this qvw model with a binary load and perhaps drop the tables that are not required for the purpose of that application.
It would be something like this:
Source Data--> QVD generator(QVW)-->Base QVD file--> QVD Generator(QVW)-->Transformed QVD--> SalesModel.QVW --> SalesSpecificApp.QVW
Hi Suraj,
The way we implement it:
Tier1: DataBase > Extract QVW > Extract qvd
Tier2: Extract qvd > Transform QVW > Transform qvd
Tier3: Transform qvd > DataModel
Tier4: DataModel > Binary load > FrontEnd
Edit:
Binary load is nothing but
Thanks
AJ
You can add an extra step before your final QVW: an intermediate QVW
Be aware that:
- The binary load MUST be unique per QVW: because it must be the first line of the script (and you cannot get two times a first line)
- The binary load copies the entire model from the source QVW : data, tables. Not the UI.
- The binary load may depend on restriction access set in the intermediate QVW
So if you have an extra long process to compute the data, you can store the data into QVD(s) but also into QVW.
QVD may contain only ONE table
QVW may contain several tables
Fabrice
Well... The binary load is an option.
For instance, once you have your Transformed QVD you may use those qvd's as final sources for the aplication, so in this case you can go without the binary load. However there are some times when may want to create a data model that may serve as source for several apps. In this case, you may create a qvw that will apply some filters to load the transfromed qvd (for instance just load certain the last 3 years althought you have 10 years of information), then the application with the graphics will use this qvw model with a binary load and perhaps drop the tables that are not required for the purpose of that application.
It would be something like this:
Source Data--> QVD generator(QVW)-->Base QVD file--> QVD Generator(QVW)-->Transformed QVD--> SalesModel.QVW --> SalesSpecificApp.QVW
Hi can any body tell me like how many binary loads can be possible for one Qvw file and.can we use OLEDB connection and binary load to qvw file simultaneously.
regards
Mahesh T
Hi,
Thanks
AJ