QlikView Scalability Issue is Urgent

[#1]

Hi Good Afternoon,

Stuck in Middle of Application

we have 2 Sources for Every Month we are getting data in .txt file format

A.txt-(52 filelds),

B.txt-(54-Fields),

8-Excel files with 2 fields in Each excel.

1-country for one month data

4.5+4.5+3=12 GB=12000 MB

Max RAM Consumption(6 users):   7.36*12000/4.96 =17806 MB=18 GB  

All countries after one year => Per Year RAM Consumption=18*12=216 GB  (80*12=960 million rows)

App Size-(countries-1-Month):=2.71 GB

App Size-(countries-1-Month):=3 GB

App Size-(All countries-12-Month):=300 GB data.

My Questions  Is it costly one to load all months data in App and maintain Application Server

or

We need to go for SQL Sever Data Mart creation from which we will connect and get data into App.

Question  is  QVD's are created for every month and working around QVD is good or else storing data in SQL Server directly working around raw data is good

[Peter_Cammaert]

Do the end users need to see the details, or do they just need aggregated data?

[Anonymous]

Use a QVD layer.

Do not create a SQL Sever Data Mart.

[ashfaq_haseeb]

Hi,

If they need to see aggregated data then go with datamarts or else go with qvd's.

Regards

ASHFAQ

[#5]

There is already large datamarts but for qlikview application each country is providing data in .text file format with project related columns removing unnecessary business columns.problem is each month heavy data in app for maintenance scalability proposing SQL server maintenance .we have qv management console also .can i know how all qlikview projects maintaining large volumes of data.explain 3 tier mechanism currently following

[#6]

Can any one help in data scalability issue