I am creating a web application for a database where a small number of records are recorded simultaneously (about 5000). Each active work record is likely to experience 50-300 changes per 30 users over a 4-hour period ... that amounts to thousands of changes per minute.
Since our test environment is so static, testing is not realistic, and some problems do not arise until we get into the production database.
I had the idea of starting the profiler, compiling the DML instructions, and then playing them on the test server while debugging the application ... Assuming that I can play them at the same time intervals as the original. But even this will not be a valid test, since changes to the tester may lead to the replay of future DML statements.
Does anyone know how to simulate real-time database changes for realistic testing?
Thanks.
BTW. Our problems are not concurrency problems.
source
share