I would first suggest to make sure you are maintaining your existing database.  Reindexing and compressing can help with size and speed.  That said, 1GB is a small database in SQL terms.  While your new modules will want to use new tables, keeping it in the same database is the best and most convenient option.  SQL Server is quite capable of running far larger databases than you have, or will likely ever generate.

Jeff

Thanks Jeff for your reply.  I run an indexing utility every now and then.  I, also, was able to download a utility that would diplay the size of each table in my DB and that allowed me to clear few tables that brought the DB size from 1.5GB to 1.0GB.  On the other hand, I keep running the Shrink command ( DB & Files) every now and then.  Any thing else you suggest me doing as far as the DB goes?  Is Compress in your post = Shrink?

Also, What I hear you saying & since SQL 2000 is capable of handeling large DBs, I can just make few naming structure changes - I already have one in place to seperate my objects from DNN objects -  to allow me better manage the database - as far as me having multiple projects in the same DB.  I already have hard time finding my DB objects when I have to scroll down handreds of objects before finding the one I'm looking for.

hamdan