Q-Eye is a third-party QlikView data file editor built by DB Software Laboratory. It’s an interesting product that allows a QlikView designer or developer to view or edit the QVD and QVX files that are produced during the QlikView development and build process.
DB made a bleg for someone to test the 64-bit version and produce some memory consumption statistics. I downloaded the software and tested it and also reviewed it for my own use.
Q-Eye definitely has a place in the toolbox of every QlikView developer and designer. In my development lifecycle, I use it to:
- Inspect the contents of QVD files that I am about to use.
- During the execution of a load script, I store the contents of intermediate memory tables into QVDs and can then inspect them using Q-Eye. This is very helpful for troubleshooting and debugging.
You should download it while it is still free!
Room for improvement
Q-Eye certainly has a few rough edges and I understand that the development team is looking for feedback for improvement. Here is mine:
1) Q-Eye is slow at opening very large files (see the Performance Statistics below). It needs to become faster.
2) Need to be able to drag and drop QVD files from Windows Explorer into the Q-Eye window.
3) Windows Explorer’s right-click Open With shortcut needs to have Q-Eye registered as a target for QVD files.
4) When you first open a QVD with Q-Eye, it loads only the first thousand rows. This is not intuitively done, particularly for a new user, who eventually figures out that he must click on the Load All button. It would nice to make this more obvious somehow, perhaps with a popup that appears over the Load All button once the initial load is complete.
5) The user needs the ability to tell Q-Eye that certain columns are dates or timestamps. Otherwise, they display the raw number. Even better would be to examine the content and if it is a floating point number in the date range, display it as a date.
6) The search feature should have the option to search for Null values in a field, as well as any non-Null value.
7) Like most Windows apps, double-clicking on the border of a column should auto-size it.
8) When loading very large files, the progress bar shows the % complete as white letters on a light green background which is hard to see.
Bug fixes requested
1) After a file is open in a tab, Clicking on the Close X button for a tab does not close it. It seems to close only tabs without files in them. I had to exit Q-Eye altogether to close an open QVD
2) The auto format Grid feature greatly oversizes text fields. It looks like it is not actually sampling the content.
3) The menu item Help > Contactl Support has a typo (Contactl)
Version tested: Q-Eye 126.96.36.199 64-bit
Environment: MacBook Pro booted into Windows 7. This laptop is a high performance system with 4 cores and 16 GB of RAM with an internal flash drive.
Since a picture is worth a thousand words, here are charts of the QVD Load time and Memory Consumption for Q-Eye and QlikView vs. the QVD file size.
As you can see, the load speed and memory consumption of Q-Eye got progressively worse as the file size increased. However, Q-Eye still loaded even the largest file fully and was able to display its contents.
Conclusion: Q-Eye is definitely useful for inspecting small QVD files and is still usable for opening very large QVD files.
The raw statistics are here:
|Test||QVD size (MB)||Rows (M)||Columns||Q-Eye Load Time (mins:secs)||Memory Commit Size (GB)||QlikView load time (mins:secs)||Memory Commit Size (GB)|
Thank you very much for this blog post.
This will help us to make our software much better.