topic Re: Is linked table a solution for handling huge data?? in QlikView

Is linked table a solution for handling huge data??

Thu, 09 Oct 2014 09:57:29 GMT

Hi,

I have million's of data in my table, to handle this huge data, which approach will be good, storing data in a single table(concatenation)

or linked table, please suggest me on this.

Re: Is linked table a solution for handling huge data??

jyothish8807 — Thu, 09 Oct 2014 09:59:42 GMT

Hi,

The best way to deal with huge data is using "Incremental Load".

Incremental Load

Regards

Re: Is linked table a solution for handling huge data??

manuelreimitz — Thu, 09 Oct 2014 10:03:56 GMT

Hey Savitha,

try to split data by datatype.

For example you have millions of order heads in your table,

orderid (int), orderdate (date), customerid (int), customername (string)

in this case you should extract the customername and the customerid in distinct loaded linked table.

Other splits depends on used datatypes.

Re: Is linked table a solution for handling huge data??

Thu, 09 Oct 2014 10:11:26 GMT

Hi Manuel,

Could you please explain me the advantage of this approach or in detail if possible...

Re: Is linked table a solution for handling huge data??

manuelreimitz — Thu, 09 Oct 2014 11:35:30 GMT

http://community.qlik.com/message/613668#613668

hi savitha, i think you've gut the answer in this thread

Re: Is linked table a solution for handling huge data??

sunilkumarqv — Thu, 09 Oct 2014 12:04:56 GMT

Hi Savitha,

Linkable doesn't work for you scenario .it work only to eliminate syncs,circular loop reference and to make single fact table .

In order to split the data in your data base should have a key fields like primary key ie 100% unique keys else

try to break the data like below exp

table:

ID,customer

1,a

2,f

4,s

5,g

in above tale split like this

Tab1

ID,customer

1,a

2,f

Tab2

ID,Customer

4,s

5,g

and so on..

eliminate unnecessary fields ,tables .

split into year2012 one qvd nad year2013 other and so on..