Data Archival logic for Huge Database size

Hi Vilas,
2GB database size is not huge.

1) You need to identify the problem, in which scenario your application is getting hung?
2) Do you have valid / optimised index in the tables?
3) How many concurrent users are present in the system?
4) If you're using any stored procedures to access the data, the queries / sp are optimised for data retrieval?
5) How many records are present in the primary table? It should be based on question 1.
6) How is your network response time / latency / band width ?
7) Does the sql server / database has good memory and processor?
8) When you have problem during insert / update or read ?
9) If the insert / update have issues, do you have lot of triggers / indices in the tables?
10) If the read has problems, do you have valid indices in the tables?

Please check and let me know, we will fix the issue.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

13y ago
Hi Vilas,
2GB database size is not huge.

1) You need to identify the problem, in which scenario your application is getting hung?
2) Do you have valid / optimised index in the tables?
3) How many concurrent users are present in the system?
4) If you're using any stored procedures to access the data, the queries / sp are optimised for data retrieval?
5) How many records are present in the primary table? It should be based on question 1.
6) How is your network response time / latency / band width ?
7) Does the sql server / database has good memory and processor?
8) When you have problem during insert / update or read ?
9) If the insert / update have issues, do you have lot of triggers / indices in the tables?
10) If the read has problems, do you have valid indices in the tables?

Please check and let me know, we will fix the issue.
0