I've just started building a new site in DNN 4.5.1 (SQL 2005) and have the base DNN product installed with some added modules and configuration. Now I need to create some custom tables and modules. I've seen some people create their custom tables in the DNN database (usually all prefixed with some unique phrase), but I'm wondering if it might be better to place all of the custom tables in a separate database, to keep things organized and to eliminate the need for prefixing table / stored procedure names.

Are there any issues with taking this approach? I've haven't looked into DNN deep enough to see if you can easily add another connection string to the config file and use it in your modules (I think I saw a SQL view module that supports queries from another connection string, but I don't know if modules like Reports support this capability).

One other concern is that once I've completed the site on my computer (local) I might have problems finding a hosting company that will support multiple SQL databases (well, without any extra costs that is).

Opinions?

mkizer:

I would say that if your module(s) only use a few tables and several stored procs, then put them together with the DNN database.  Prefixes for object names are not a bad idea.  Just think about the additional management you will need to deal with to manage a separate database with its own user accounts, backup, etc.  This gets compounded if you are dealing with a hosting facility (is much easier if you do it on your own server).

Carlos