question

Steve-9960 avatar image
0 Votes"
Steve-9960 asked ·

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

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-general
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AmeliaGu-msft avatar image
0 Votes"
AmeliaGu-msft answered ·

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

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the reply AmeliaGu, the database names on the target server are correct but unfortunately the database names in the dreplay trace are all pointing to the master database instead of the application database names causing the error, I believe this may be due to us switching to contained users to improve the portability of the databases and move away from SQL Server logins as we've been able to run Dreplay traces successfully in the past without this issue prior to the switchover to contained users.

0 Votes 0 ·