We are developing an APP very strong on DB needs, and we were wondering what benefits our Modules of using the {databaseOwner}{objectQualifier} system proposed by DNN in oposite of using our own definition

Part of the solution is a migration from a previous system where "each module" has its own schema, facilitating maintenance and modularity between projects/modules.

SQL lanscape will be more clear as [ownSchemas].[whatever...] than dbo.dnn_moduleName_whatever ...

Hi Sebastian, thanks for response

About the first, we are running on own servers (azure) and no plan to migrate to an external hosting company

About the second, DNN use an account with all privileges, and by default, no other objects than those in dbo exist in an DNN installation (times where a single db stores more than a project has already pass)

I uknow if there are plans to "harden DNN security", by using different DB users for installation, module deployment and normal run. Otherwise, the inconveniente of adding schema permission to the single user used by DNN do not seems like a big inconvenient.

Do not misunderstand me, I like the {databaseOwner}{objectQualifier} system, but this will made for us a lot of code rewriting in porting the existing solution and documentation.