In our application of Sitefinity 5.0, we have a SQL user name "ABC" that we want to use the schema "ABC". However we want the tables created as "dbo" schema. The problem occurs when the application boots up, it seems to look for tables under the schema "ABC", and then tries to create them because the schema of the existing tables is "dbo".
Is there a way to tell the Open Access ORM / Sitefinity 5.0 to NOT use the default schema and instead to use an alternate one?
Is there a way to tell Sitefinity to NEVER attempt to create or alter tables (essentially turning off the UpgradeDatabase functionality)?
*** Please note that in our environment, it is unacceptable to allow the ORM to make schema changes. Additionally, we do not want to make "ABC" a db_Owner. Instead, we will allow the updates to occur on a development server and then use a tool like RedGate schema compare to port them to production.
[One other thing] This problem did not seem to exist in Nolics / Sitefinity 3.7 - which is our current environment and which we are trying to port to 5.0.