Your observations regarding QVX vs QVD are correct, though I suspect that as the 2 products become further integrated, QVD support within Expressor would appear as well.
In the meantime, there are several key benefits you could realize from using Expressor:
- Semantic Metadata - allows you to conform heterogenous data sources into a common data model. This can be the model already created within QlikView.
- Built-in source control - dataflows and other artifacts created within Expressor can be checked into a central repository and versioned over time
- Graphical designer for data access and provisioning - minimize the need to develop and maintain scripted solutions
- Logic re-use - reduce or eliminate the need for 1-off solutions by leveraging Expressor's Semantic Metadata layer
- QlikView Connector - ability to seamlessly call Expressor as a data source directly from within QlikView 11 without having to manually launch Expressor. QlikView load script(s) automatically get created. This makes integration into Publisher very seamless as well.
Let us know if you have any additional questions.
Thank you for your answer Hugo.
Is there still a value with Expressor for QlikView develoment if all data goes through SSIS packages (Microsoft)?
Do I unserstand you right, that we could convert star schemas in our QlikView scripts to Expressor and use one connector instead?
Do you have any example Expressor projects that I could use to test QlikView Connector? Does QV Connector work together with Expressor Desktop Edition?
Yes, you could translate QlikView scripts over to Expressor dataflows. However, you may want to evaluate the reason for doing so. Expressor currently only generates QVX files. Further, the value in having a star in QlikView is to take advantage of the associative model. Combining that data into a single QVX would lose much of that. Of course, if the intent is to replace that with a QVX instead of QVD, then sure, that would work.
I'll upload an example project shortly.
See the attached Expressor project. Do not uncompress it. You should be able to import it directly into Expressor via the project import option. Open the project afterwards and have a look - there's simple dataflow that joins a flat file to an Excel file and writes the output to QVX. There's also a Deployment Package created for this dataflow. The Deployment Package is a requirement for using QlikView Connector.
Next, within QlikView, create a new QVW and edit the load script. Choose the QlikView Connector as shown and click Connect:
Next, locate the Deployment Package mentioned above. You'll have to go into the Expressor workspace area as shown below
Select just the top level project that contains the Deployment Package.
Click OK and notice that it inserts the CUSTOM CONNECT statement
Next, click the Select button to pick the data columns to bring in
To select all, just click OK and you should now see the select statement inserted as well.
At this point, you can reload the data and what will happen is that Expressor will be invoked in the background, run the dataflow, and pass the data into QlikView via the QVX file.
QVX_Demo.zip 2.9 MB
Is there any other uses of QVX. I could see your answers can be done directly using normal QV scripts that are present now.
1) Is that expressor supports taking data from BIG Data databases ?
2) To what places or scenarios, current QV doesnt support and Expressor helps in those places ?
In Simple way, why i need to buy expressor ? Justification pls ?
QlikView Expressor supports any ODBC based data sources.
Please see this link for answers to your other questions:
Gald to be of assistance.