datatable or database table ?
I have a requirement to store almost 50000 rows of data and need to retrieve and filter those values for populating a dropdown. Which method do I need to choose to store the data, datatable or should I go for a database table? Is there any performance issue, if I use datatable for this purpose?
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Cognizant Technology Solution
US
It will not have performance issues. I have handled Data Type with 300000 records. But for ease of maintenance you may split the drop downs into categories and may create more than one table.Just make sure that you are exposing the columns of the Data Type. Also, if you are having criteria you are using in the when clause, create an index for that column. You will get better performance. This is true for External table as well. Load the date using a parameterized node level Data Page(I guess data does not change frequently) and once it's loaded it will not go back to the database until and unless something is changed in the table.It will give you better performance.
Cognizant Technology Solution
US
In Pega 7 Data Table is no longer there. It is called Data Type now. Data Type will ultimately be mapped to a table in PegaData DB. But as you are going to use it for Drop Down, Data Type is more flexible as you may manage it from designer studio and it can be configured by user also if needed.
Pegasystems Inc.
IN
My concern is like, can the data type is capable of handling data of about 50000 rows. Will it cause any performance issues while dealing with such an amount of data?
Accepted Solution
Cognizant Technology Solution
US
It will not have performance issues. I have handled Data Type with 300000 records. But for ease of maintenance you may split the drop downs into categories and may create more than one table.Just make sure that you are exposing the columns of the Data Type. Also, if you are having criteria you are using in the when clause, create an index for that column. You will get better performance. This is true for External table as well. Load the date using a parameterized node level Data Page(I guess data does not change frequently) and once it's loaded it will not go back to the database until and unless something is changed in the table.It will give you better performance.