Tuning workload to remove update and insert statements (4339778)

I captured the workload from an existing server and want to replay from that workload to load test a new server and database. This workload contains significant number of update and insert statements. If I run the workload with concurrent userload of (let's say 100 users), it creates database locking and deadlocks, producing unrealistic testing results.
Should I clean up this workload to remove all update and insert statements before I run it in BMF?

Is that the right thing to do knowing that by removing a lot of the statements, I will be altering the real workload.

You can also edit the DML commands to use the BFScripting calls to change up the data being inserted/updated/deleted, etc. That way when 10 users are all trying to do an Update it goes against different records.

The script category and function should be used for this purpose:

You ll need to determine the nature of your queries, determine WHAT the inputs should look like, and then proceed.

For example, if you have a query that looks like this 

DELETE FROM TABLE_A WHERE ID = 5;

You could re-write that to be

DELETE FROM TABLE_A WHERE ID = <BFSCRIPT CALL>

You can create a list of account ids in a flat file, and then have BMF read those values in random order for the transactions.