QVD , in qvd file how much max data we can load?

[#1]

hi all,

                in one qvd file how much max data we can load? is there any limit ?

thanks in advance,

Ramana

[Peter_Cammaert]

BTW sizing a QlikView machine is an art in itself. There are some good introductions in the Technical Briefs section of the qlik web site, like the following:

http://www.qlik.com/us//~/media/Files/resource-library/global-us/direct/datasheets/DS-Technical-Brie...

http://www.qlik.com/us//~/media/Files/resource-library/global-us/direct/datasheets/DS-Technical-Brie...

[Anonymous]

The only limit I have of is 2 billion distinct values in a field.

Other than hardware limitations.

[#4]

You may find this thread useful:

http://community.qlik.com/thread/94922

[#5]

is the 2 billion distinct values still the case? I thought it was removed in a prior version

[Anonymous]

Joe,

May well have been.  Anyone know for sure ?

[jagan]

Hi Ramana,

There is no limit on the size of the QVD, you can store TBs of data also.  But the thing is you need to have required Hard disk space and sufficient RAM, during loading the QVD is stored in RAM, so if you have enough RAM then the loading will be faster otherwise it will be very slow, sometimes app will close.

Hope this helps you.

Regards,

Jagan.

[Peter_Cammaert]

Still applies. See the Reference Manual for QV 11.20SR10 - Appendix A.1 Limitations of the Amount of Data to be Loaded:

"The amount of data that can be loaded into a QlikView document is very large. It is primarily limited by the amount of primary memory of the computer. However, there is one inherent limitation in QlikView that you must be aware of when building very large documents: A QlikView document cannot have more than 2,147,483,648 distinct values in one field."

[Peter_Cammaert]

And the same story on a different tune: while QlikView may in theory allow you to load abundant amounts of data, keep in mind that in a typical single platform server environment there are at least two competitors for RAM:

• the QVS-service which mainly services end-users and has its own memory manager, and
• 1 or more QVB processes that do the actual reloading.

Whenever they start fighting for RAM, your entire system may almost slow to a halt and even force a restart of QV services. Good performance under all conditions is guaranteed mainly by an excess of available free memory. Since we don't have a predictor-type tool for this kind of situations, a system performance monitor will be your best friend.

[rbecher]

Just to add my 2 cent, this can easily happen with a numerical field (timestamp, amount, price etc.) if you have a large set of transactions..

- Ralf

[#11]

good to know, I must have been thinking of the time it was increased from 1 to 2 billion