Closed ghotz closed 5 years ago
Seems like the target server can't keep up with the workload. Have you tried capturing sp_whoIsActive to see whether some queries are being replayed and got stuck?
Yes, queries are regularly stuck waiting for CPUs or PFSs on tempdb, but is expected since the destination system run constantly at 100% with 8 cores (the original workload has 32 cores). Still, the message should output a proper date and the real problem is that it stops sending commands to the Replay Consumer even tough it's collecting them and writing them to the Analysis Consumer.
During the replay sometimes an error similar to the following is logged:
The error is risen periodically and after a while the tool completely stops replaying and just logs this error (as if there's nothing to replay).
More info: