Share via

SQL Server Distributed Replay Trace Error Failed to set proper database for the connection following switch over to contained users

Steve 21 Reputation points
2021-03-03T09:17:18.707+00:00

On SQL Server 2016 Ent Edition and W2016 Standard O/S - I've ran Distributed Replay Traces in the past successfully and recently in production I've made the switch from SQL Server Logins to Contained Users following that during replaying the Dreplay trace the pass rate was < 2% so I captured the output trace and all of the database name fields are set to master and the exception 'Error Failed to set proper database for the connection' so it's led me to believe the issue is a bug with Dreplay and contained users, has anyone else found this issue and is there a fix that can be applied?

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories


Answer accepted by question author

AmeliaGu-MSFT 14,016 Reputation points Microsoft External Staff
2021-03-04T08:24:50.207+00:00

Hi Steve-9960,
For this issue, I recommend you submit it to the Microsoft feedback at this link https://feedback.azure.com/forums/908035-sql-server.
Your feedback is valuable for Microsoft to improve the level of products and service. Appreciate for your understanding.

In addition, please make sure the database name is the same as database name captured in the replay trace file.

Best Regards,
Amelia

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.