I did found the right Forum for posting my workaround.  I think this is the nearest theme.

In the last weeks after upgrating some some DNN Portals on our Windows server with running Plesk for Windows (Hosting Management) we have some Problems find out.

First we must do a workaround on the SqlDataproviders before we can install the update, becource ther was some missing and on some modules wrong {databaseOwner} statements.  After this we think now it is all OK.  But it did not.  After the Update we get high performenance problems.  So the CPU usage goes up to 100% for the SQL-Server thread.

Last night I go to make a workaround of all spocs.  I corrected many Module and core Spocs with the right databaseOwner manually with the SQL Manager.  Now all Spocs are correct, and what is the perfomenace doing?  The Performenance is now in right limit. 

In some Spocs is the databaseowner missing in the line create procedure showthis and some databseowner statemensts are missing to the table connection. This is more relevant on databases that have not dbo as DatabaseOwner running.  But the lost performence i can see on databases with dbo as dabaseOwner too.

So i see all SqlDataProviders need a workaround and have to corrected.  In fact i only found 2 Modules on my DNN Installations without a Spocs issue!  Thease are now the Blog and the Forum Module 4.4.0 (still in release process). 

But not only the missing {databaseOwner} statements are the problems.  Some Sqldataproviders still install the Spocs as this:

create procedure dbo.EventsGetAll

This makes no problems if the Portal database is using dbo as DatabaseOwner, but if not these Spocs will never delete.  Also some old spocs that are renamed are still in the databases (AddEvents).

Also but I am not shure, but i can present to me, that some changes not correctet in the database tables, about there are some wrong DatabaseOwner statements. 

I think the Database need more ressourses if it must search the right database! 

I am gladly ready to make a workaround on the SqlDataProviders with the Teams.  Also I am ready to work as beta tester for comming Modul updates.

I see the DotNetNuke project is a very great PortalSystem, and I will do what i can to help this project.  TeamMebers are free to contact me.

Best Regards

Matthias Schlomann

Hello Joe,

let us talk about how i should do.  I think we have do this by the framework SqlDataProviders and all Core Moduls SqlDataProviders, to create an update.  It will be a hard work about i have to check all SqlDataProviders, and write a new Provider with insert all my changes, so this can run as an upgrade.

Or do you meen, I make the changes in the providers and you write then the scripts for update?

Please contact me. Have send You a E-Mail.

Regard

Matthias

Today I have discus the changes we have do with Sebastian Leupold.  We two will start to make the changes begin on the DataProviders 4.4.0 and higher.  We start here because this is relvant for all new installations.  After finished this wie start with the older SqlDataproviders.  At first we work only an all SqlDataProviders of the Framework.  Then we look on all Modules.

Sebastian and I work on it as Team, so that we did not do double work.  Sebastian send the changes then to the Project.

Regards

Matthias