Concurrency testing with SQL server migration

[adhoustonj]

Hello AWF,
Can anyone share a preferred method of concurrency testing? I've migrated Access BE's to sql server and made modifications, optimizations, configured data types, set up views in sql server, etc, and the speed/performance seems great so far. I now need to test multiple users using the db, and wasn't sure if I need to set up a test team, or if there are stress tests/evaluations that can be run before user testing.

 

[Minty]

Generally speaking, a lot of the concurrency issues are dealt with pretty automatically with SQL server, it's much more elegant in its handling of record locks. There are options you can use (With (NoLock)) for views etc. that are read-only that can help.

There are some good tools out there - I haven't used them for a while as most of our SQL work is Azure hosted, but give this one a go

SQLTest Tool - SQL Server Performance, Load, Stress and Unit Test Tool

SQLTest is an easy-to-use tool to generate real-world workload for testing. SQLTest can generate SQL Server database calls very similar to the actual application. SQL Server Performance, Load, Stress and Unit Test Tool. SQL Server Performance Test Tool, SQL Server Stress Test Tool, SQL Server...

www.sqltest.org