I'd say that the limit is the computer and network you have. Depending on your server and network hardware, QlikView will manage quicker or slower the same file. For what it's worth, I'm using several 10GB+ QVW files (without compression) and the file behaves (it's over a half billion rows). I've seen some 10Gb QVD files working as well. How quick will depend on your users expectations and requirements.
There are some people around managing really huge data volumes, so let's see what they say.
I'd say that the limit is the computer and network you have. Depending on your server and network hardware, QlikView will manage quicker or slower the same file. For what it's worth, I'm using several 10GB+ QVW files (without compression) and the file behaves (it's over a half billion rows). I've seen some 10Gb QVD files working as well. How quick will depend on your users expectations and requirements.
There are some people around managing really huge data volumes, so let's see what they say.
The biggest actual .qvw file that I've seen was around 35GB on disk, but I'm sure there's other bigger ones out there.
Hardware sizing, as mentioned, is definitely important, but a lot of the performance comes from sensible data modelling and document design. I.e. a document designed for its purpose.
.png "Miguel_Angel_Baeyens"){kind=avatar}
