Question : When to Create a new DB

Hi,
I am doing the DB administration for a very small company's e-comerce web site using SQL Server 2005 and I am a bit new to some admin issues.

I am not quite sure when to create a new DB versus adding more tables to the same DB.  The site will be divided into component/functions such as (typical for a e-comerce site)
-  Account sign up/maintenance
-  Store
-  individual products displayed via the site
-  Blog facility
-  Public pages

Does everything go into one site DB or should they be broken out by "function or product"?

To add a wrinkle to this question - my boss has future plans of selling off the software for each of these "modules" spearately.  In this case a separate DB seems easier to export to someone who buys the software.

Also, his actually has 2 sites (different products) that use the same DB tables and columns for The Account Setup/Maintenance, the Store etc.  They were designed that way intentionally.

Thanks in advance,
hefterr

Answer : When to Create a new DB

Hi

You got
SQL SERVER  -  shared memory and processes for all its DBs and connections
DB  - will be backup/restore with all its contant to the same point in time
    scheamas   - logical devision - you can use it to identify each site
             tables


Generaly - everything you do will work but
for preformance - If you got busy sites put them on diffrens SQL
If you will need to restore a site to a point in time and not all of them - put them on seperate DBs
If you want to be supper orginazie use schemas and dont  put all the tables under dbo schema


Good luck!
Guy H