The reverse is also true.
If I install Umbraco with Integrated Security, I can't swap the connection string to a specific sql user without Umbraco requiring a reinstallation.
I have a feeling I am doing something incredibly stupid as the toughest problems always have simple fixes but I can't for the life of me see it.
Looks like your user skautai creates a schema dbo.owner in the database, where as your integrated user uses dbo. Umbraco doesn't know this so it happily tries to find all the dbo.owner.* tables, which don't exist, so it will do a fresh install (if you would continue, you would see that you get 2 sets of umbraco tables in that same database).
So check how your user is setup in SQL as it is a permission/user mapping issue. You probably need to map your sql user to use dbo as it's default schema.
This issue came from a Plesk deployment where the limited SQL Server interface was not creating the correct schema for the users. Thanks for all the answers, I should have seen it myself.
Umbraco connection string - cant swap between integrated security and specifc sql user
In Umbraco 8.12.2, when I install Umbraco with a specific sql user it generates this connection string and eveything works fine
However, when I change the string to use a specific sql user, Umbraco tries to reinstall
The reverse is also true. If I install Umbraco with Integrated Security, I can't swap the connection string to a specific sql user without Umbraco requiring a reinstallation.
I have a feeling I am doing something incredibly stupid as the toughest problems always have simple fixes but I can't for the life of me see it.
Sounds like a similar issue to this https://our.umbraco.com/forum/using-umbraco-and-getting-started/105533-changing-database-table-schema-from-dbo-v88
Looks like your user
skautaicreates a schemadbo.ownerin the database, where as your integrated user usesdbo. Umbraco doesn't know this so it happily tries to find all thedbo.owner.*tables, which don't exist, so it will do a fresh install (if you would continue, you would see that you get 2 sets of umbraco tables in that same database).It is related to your users permission in the database.
I can swap between a user and integrated security without causing umbraco to recreate it's tables.
both these connection strings work quite happily
So check how your user is setup in SQL as it is a permission/user mapping issue. You probably need to map your sql user to use dbo as it's default schema.
Yes, that was it.
This issue came from a Plesk deployment where the limited SQL Server interface was not creating the correct schema for the users. Thanks for all the answers, I should have seen it myself.
is working on a reply...