Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
I have large volumes of data in my application and need to improve the performance, response time.
In my data model I have a lot of situations like in point 1. attached file. What do you think about duplicating keys and alliasing to achive situation in point 2. Is there a chance to achive a better response time on my app. ?
Hi Sylwester,
it would be easier for us to help you if you can elaborate more or share your app with dummy data.
I think the solution for your problem can be more than one depending on your model, data, etc.
You can start from here, there are some good performance tips:
*** 6 Weeks in to QV Development, 30 Million Records QV Document and Help Needed!!! ****
Let me know if this helps.
Kind regards,
Hi Santiago,
I know that there are more solutions but I would like to know what you think about simple change like below:
I have a big link table:
Link_Table:
LOAD
KEY_A,
KEY_B,
KEY_C,
..
Field1,
Field2,
Field3,
..
RESIDENT Link_Table_Tmp;
And few fact tables like:
Fact_Table1
LOAD
KEY_A,
Field20,
Field21,
..
RESIDENT Fact_Table1_Tmp;
Fact_Table2
LOAD
KEY_A,
Field30,
Field31,
..
RESIDENT Fact_Table2_Tmp;
Fact_Table3
LOAD
KEY_A,
Field40,
Field41,
..
RESIDENT Fact_Table3_Tmp;
And I want to change that into:
Link_Table:
LOAD
KEY_A as KEY_A1,
KEY_A as KEY_A2,
KEY_A as KEY_A3,
KEY_B,
KEY_C,
..
Field1,
Field2,
Field3,
..
RESIDENT Link_Table_Tmp;
Fact_Table1
LOAD
KEY_A as KEY_A1,
Field20,
Field21,
..
RESIDENT Fact_Table1_Tmp;
Fact_Table2
LOAD
KEY_A as KEY_A2,
Field30,
Field31,
..
RESIDENT Fact_Table2_Tmp;
Fact_Table3
LOAD
KEY_A as KEY_A3,
Field40,
Field41,
..
RESIDENT Fact_Table3_Tmp;
This is just a simple example of what I want to do.
Thanks
Sylwester
If you are using a concatenated key in your table, try changing them to numeric keys using autonumber function.
numeric keys work better on large volumes of data
hth
Sasi
Yes, I use autonumber() function.
Sylwester
Any opinion ?