I have a QVW that pulls in 100 million rows of data from more than 30 QVD files. Sometimes I just want to query one of those QVD files to extract a small amount of information and optimally send it to Excel so I can analyze it. This is a quality control initiative.
I am currently using the QViewer program which has a limited query function but it does not let me export the data and it has a limit to how much data it can load. Looking for a low cost utility program to accomplish this. I am betting 100's of you would like this too, so if someone out there is savvy enough to create one for all of us, that would be great.
Really hoping to have a query tool that lets me pick values from one of my 30 columns in my qvd's. I don't really want to import the data into a QVW, just so I can filter it off. I also rename a lot of my field names to more friendly names on the load as I get data mostly from SQL tables. Just looking for a quick and easy solution. I do appreciate your suggestion.
Well, it does appear that my version of Qviewer is out of date ( 1.48 ) and they have a new tool called EasyMorph that replaces the query function. I will play with it and let you know if it resolves my reason for posting. Thanks for taking the time to post!
I may be getting very close to being off-topic, but I think those 100s of us would rather verify their big final QVD in a QVW document specially constructed for the situation. It's pretty easy to set-up, supplies relevant information within an hour and uses those discovery qualities that QlikView has for pointing out things that you weren't really looking for.
Take your time to figure out a few business rules for checking on Data Quality, and you will be using QlikView to check out QlikView within minutes.
Thanks for taking a few minutes to reply. I actually have 54 different QVD files that load to my primary QVW. The data comes from multiple sources, including SQL and Excel Files. I agree from a purist standpoint that I can create a QVW file for data integrity verification. Quality however is not my only concern. Sometimes, I only need to look at the source data with certain criteria to troubleshoot an issue. Sometimes I want to review the QVD data before it gets imported to the QVW file ( such as after a new reload where I added columns ). Maybe my date formats need to be fixed before importing to my QVW file. I am an Excel Guru and can pivot table data a lot faster than I can create a new QVW file.
As a follow up, I downloaded the new version of QViewer and it does have a tool that will enable the user to transform and export data sets based on filters to Excel, CSV or a text file. The tool will work great on smaller datasets less than 2.0 GB - QVDS.
You should have a look. Maybe it is a tool you can add to your own resources.
It shows that situations (and their challenges) can differ a whole lot. I do own a QViewer (company) license, but most of my clients do not. Luggaging large QVDs back and forth from server shares or through RDP sessions didn't make me happy (and I'm not an Excel guru, don't trust Excel that much when dealing with raw data) so I quickly reverted to the practice of supplying a (hidden) validation sheet in almost every document I make. They often survive for a long time, as weird situations in input data & systems keep reappearing at regular intervals. In those cases, being able to quickly figure out that QlikView or its surroundings are not the culprit is very important to me. I don't hesitate to call it a life-saver, both for me, my successors in projects and the customers themselves that choose to become self-reliant.
Your development cycle is probably different and your expertise too. I'm glad you've found your best-of-breed solution and told us about it.
