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

[Ralf-Narfeldt]

There is no fixed limit, it is dependent on your RAM memory size.

[sujeetsingh]

There can be a limit of file size of the QVD.

[#4]

hi,

There is no limit but you existing RAM can load your qvd

Regards

Vimlesh

[Peter_Cammaert]

The only limit is the limit imposed by your file system (which is quite high in 64-bit systems).

Moreover, existing RAM is never a limit to a QVD LOAD, since you can load a QVD in chunks (performance might be bad).

A the time of creation however, a QVD cannot exceed available RAM since the source table has to fit in memory before you can STORE it into a QVD. And a QVD file must be written in one stroke (no append).

[#6]

Thank You for your answers,

qvd size is not a problem for ram size, if 300mb qvd or 1gb qvd also we can load into qlikview right?

we are using qvds as a data source so we can load huge amount of qvds also?

how the qvd size will impact the Ram size ?

Thanks in Advance

[#7]

hi,

At the beginning of an analytic session QlikView will load a QlikView document from persistent disk based storage (i.e. a QVW file from hard disk) and place the entire dataset into RAM. During an analytic session QlikView will not make a call out to the database or access any other disk based data repository: It will only rely on the dataset present in RAM. This is what gives QlikView the unlimited flexibility and near instantaneous response times (all data is aggregated in RAM). But, of course, to take advantage of the benefits QlikView provides, all data to be analyzed must fit in RAM.

[#8]

hii

yes, loading depends on your OS. If you are using a 32-bit Windows(it doesn't depend on the version) the hard limit is 4GB RAM. Because 2**32 is 4GB. Even if you have 32GB in your computer, this is the hard limit using any 32 bit-OS.

This limit even decreases at least to about 3.4 GB because the rest is used for internal purposes.

So if you have to load as much as you have to, try any 64-bit Windows and of course enough physical RAM. How much it will take depends on your data.

Anyway, I would Try to split the data(-files) and store them into several qvds and build them together afterwards.

[Peter_Cammaert]

The QVD size is not necessarily a problem in itself, as you can load a part of a QVD. However, you may not be able to load the entire QVD into memory due to lack of RAM. To use your incomplete example:

Loading an entire 300MB or 1GB QVD is perfectly possible in a server with 16GB of memory and a lot of free memory. However loading that same 1GB QVD may prove to be impossible in that same 16GB server if other processes (like QVS and other Windows applications) ran away with the bulk of RAM. The same applies to QV Desktop on a laptop.

The real question is: how much data do I want to load and keep in memory at the same time, and how many others are fighting for the same unused parts of RAM.

[#10]

Thanks Vimlesh Gupta,

So if qvd file have huge amount of data also it will not impact the ram?

data is accessing from qvw its fine. we are implementing the incremental load after publisher reloads the data will increase the data stores into qvd files right?

If we load that huge amount of qvd into qlikview application it will impact ram and crash application?

inadvace thanks

ramana