I'm working with a solution where we use SQL server and SSIS as our data warehouse and ETL tool. The data warehouse generates most of the data for our QlikView reports.
Regarding our SSIS packeges we use the Tortoisesvn (http://tortoisesvn.tigris.org/) software for Revision control / version control / source control software, etc.
I'm wondering if anyone knows about software we can use for Revision control / version control / source control software for our ClikView soulution?
And tips and advices for stuff we have to think about when implenting such a solution...?
Our current sollution is not good enough where we store al qvw/qvd files on one server and with noe check-in control or "rules" for deployment and change handeling...
Hope any one can help - all advice is appreciated especially experiences anyone might have considering this issue...
Take a look at the prj functionality in QlikView. Create a folder next to the document, with the same name only without ".qvw" and with added "-prj" - for example; for "Films.qvw", then name the folder "Films-prj". The next time you save the qvw document, the definition of the file with show up in xml files here. Changing the document and saving will update the xml references.
To re-create a document from the prj references, just create a blank document (Ctrl+N in QlikView), save it with the same name as the document, close it and re-open it in QlikView, and the document will be created after the definition.
Hope this helps!
Agreed. We did that in QV10 and now in QV11 we tested TFS and the integration is very good.
Our experience is in the development environment only... No QVDs.
Really helpfull! Just one question, what is the DocBinary.dat file? Do I need to track that as well in my version control?
If I recall correctly, this file contains the encrypted password and username for database connections. I am note sure what else, if anything. But yes, I would include it in your version control. I know it binary, but I have never seen it get large.
I am not sure I understand how this will help versioning, as every change you make, updates the xml files so there is no history.
Am I missing something here?
This will help versioning by tracking changes made to, but not limited to:
- Changes on object properties
- Changes on sheet properties
- Changes on document properties
- Changes in the load script
All changes made to any part of your document will be recorded in the -prj XML-files.
Thus you will be able to diff them in a diff tool.
Thank you Magnus.
so you mean to say that in the xml files changes are recorded so there is history in them. Do you have any diff tool in mind I can use to check that?