My ASP.Internet host only enables 3 database customers per db apart from the dbo.
I've one for that web application that only runs saved procs and it has limited chooses to tables.
One for ASP.Internet membership/roles.
One for SQL cache dependency/notification.
One for logging - ELMAH / log4net.
How does one consolidate some customers into 3? How can you circumvent limited database user accounts in ASP.Internet hosts?
I am considering mixing the net application and logging accounts.
I'd state that mixing the logging and web application databases will be the best choice - if you wish to try to keep your separation then you may prefix the table names.