This question is locked. New answers and comments are not allowed.
Good evening,
I am using the latest version of OpenAccess, for developing a large scale web application and now I am evaluating some performance strategies, (I would also like to mention that database backend that is used is MySQL):
1. Context separation, right now it is a big context with all the tables and the relationship mapped from that database? I am wondering if splitting the context into smaller ones could mean a difference?
2.Fetch plans, this feature doesn't seem to be an option because a lot of code should be modified, and some parts of it, may need some serious refurbish.
3.ADO.NET- this strategy would be the last resort and it will be used only in the extreme cases only.
4.Using stored procedures and moving a lot of the code towards MySQL, here the problem is shifted towards the database server and I don't know how well OpenAccess is with these.
My question is simple:
Has anyone tried OpenAccess in a scenario with a lot of records inside the database, and if so what strategy was used to improve the performance?
Right now, my instincts are telling me to do a context separation and after that using OpenAcces, only for Data manipulation, let the Ado.net to the selection and calculation job.
Thanks in advance.
I am using the latest version of OpenAccess, for developing a large scale web application and now I am evaluating some performance strategies, (I would also like to mention that database backend that is used is MySQL):
1. Context separation, right now it is a big context with all the tables and the relationship mapped from that database? I am wondering if splitting the context into smaller ones could mean a difference?
2.Fetch plans, this feature doesn't seem to be an option because a lot of code should be modified, and some parts of it, may need some serious refurbish.
3.ADO.NET- this strategy would be the last resort and it will be used only in the extreme cases only.
4.Using stored procedures and moving a lot of the code towards MySQL, here the problem is shifted towards the database server and I don't know how well OpenAccess is with these.
My question is simple:
Has anyone tried OpenAccess in a scenario with a lot of records inside the database, and if so what strategy was used to improve the performance?
Right now, my instincts are telling me to do a context separation and after that using OpenAcces, only for Data manipulation, let the Ado.net to the selection and calculation job.
Thanks in advance.