A quick hint to all users out there that have QVWs in QV9SRX format. I have been successful (mostly) at one of my customers in converting older format QVWs as follows.
I moved all my QVWs to a QV10SR2 machine. I embedded a modified version of the DoDir script from the QV Help in a utility QVW that finds all my QVWs and creates a batch execution
command for each QVW using the /rp command line parameter (more on that in a bit). Each command line is a row in a table so a quick copy/paste of the contents of a List Box into a Windows
batch file lets me open, partially reload, and save each of my older QVWs into QV10SR2 format. Now back to that Partial Reload thing -- QV has two relevant command line parameters - /r (open, reload, save, and exit a QVW)
and /rp (open, partially reload but only if the partial reload keywords are part the LOAD statements, save, and exit). QV has no "/s" parameter (open, save and exit) but /rp seems to work OK although several of my QVWs
had specialized scripting that resulted in failures that required manual intervention; I was able to convert about 75%+ of my QVWs "automatically" and the rest manually and then run the MetaData Scanner on them. I'm still evauating the results.
If you have questions (easy, simple ones), ping me and I'll try to respond as time permits.
I've been trying to get this to work...our environment is currently v9SR7, so I have taken copies of some example qvws, opened and saved them in v10SR3 then run the scanner and the monitor apps. The scanner appears to be working to an extent - I can see the qvws etc in there, however the monitor app isn't showing anything in the Datalineage tab such as connection strings etc. There are pleny in the apps so any ideas why they're not coming through? Do I need to reload the apps? (Obviously I would need to reload to regenerate the qvds, but I'm just trying to get the qvws working for the time being).
bpn - This is exciting! I had downloaded the app and it looks brilliant. I haven't got chance to deep dive yet, though it covers everything I can think of. I am building something very similar using .Net (Web App), Our idea is to store the QV & QVD meta data in SQL Server and access the meta data for QC.
I will deep dive and I'll get back to you with more feedback.
Cheers - DV
This is good stuff! I think it will become an invaluable tool when we are speaking to enterprise customers. Especially the naysayers within IT. Data lineage visualization is a perfect example for the organization that splits responsibilities between IT and the business. It shows a great way for IT to visualize upstream effects from changes at the ETL process layer.
We hired Andy Rizutto from Next Generation Consulting to come in and work on the MetaScanner/MetaMonitor data models. He's done quite a bit of work on the data model. And we've developed a dashboard which we are calling the "Dashboard Overview" based on the MetaMonitor. I'd like to take some time to show you (with Andy) what we've done and to find out if we can get you to update your base MetaScanner code to inclue our improvements. My motivation is that it will be less likely to break with upgrades if you are actually incorporating our changes and then testing the functionality.
One of the issues that we have had to work through is the fact that these seem to be configured to run on a single-server environment. We are running on a distributed environment (6 servers: 2 for IIS, 2 for QVS, 2 for Publisher).
I would really like to have the ability to trace the data lineage from ultimate source to ultimate target, i.e. database, stage (ODS like) QVD, base (aggregated) QVD, dashboard or whatever other myriad possibilities there are. This seems like it would be a great functionality to add to the tool. I know that this would make it much easier for our business users to use the tool.
Overall, we really like the tool, as it is giving us a much greater insight into our QlikView deployment.