Problem with database-authenticated user to create a Trace Network within an Enterprise geodatabase

[clc]

I am trying to run "Create Trace Network" in an Enterprise geodatabase. The ArcPro documentation on the tool states that: "The input feature dataset must be from a database connection established as a database-authenticated user and owner of the input feature dataset.".
So I ran "Create Database User" with "Create Operating System Authenticated User" unchecked and the Role entry empty. I then opened Microsoft SQL Server Management (SSMS) and verified that within my database, Security, User, the new user was listed. I right clicked and opened its properties. In the Membership page, I checked db_datareader and db_datawriter.
But when I came back to Pro and tried "New Database Connection" with "Database authentication" and my new User and password, I got "Database Connection: unknown error". When I clicked Validate I got a cryptic hexa number and the word "Failure".
What am I missing?

[MarceloMarques · Accepted solution]

It is probably how the Enterprise Geodatabase in SQL Server was created and configured.

Follow the best practices on my database guide books and database template scripts in the community.esri.com blog below.

Mapping and Charting Solutions (MCS) Enterprise Da... - Esri Community

• Guide Books ArcGIS Pro

• Database Connections Best Practices

• Database Template Scripts

Notes:
- avoid the DBO ArcSDE Repository setup.

- always use the SDE user ArcSDE Repository setup, it has better security and permissions management.

- do not use the sde user to load gis data.

- always create a data owner user with the proper permissions to load the gis data.

- read the database connection best practices, see link above.

- you can follow the production mapping database guidebook, the best practices can be applied to any industry.

- If you still continue to experience issues then open a ticket with Esri Technical Support to follow up and investigate further.

I hope this helps.

[clc]

I'll try to use your recommendations before reaching to Esri support. I had never look deeper on how my Enterprise geodatabase was created and only used dbo, so lots to catch up! Thanks for your detailed answer.