PROS and CONS of seperate databases for CACHING...

I have a main database...for this large Web site...and Im wonderingwhat would be the PROS and CONS of using another database (located onthe same, or on another SQL Server). Im just thinking this would begood incase we ever needed to take some load off one of the servers.

Also, we will be integrating Community Server into this Web site. Ofcourse you know CS adds its own database objects which crowd up ourmain database objects.

We were thinking of giving CS its own database also; bad practice, or...it doesn't matter much?

Thank youIf for ASPSTATE, then a separate server (now or in the future) would improve scalability.

If you mean multiple instances of SQL Server on the same server box (SQL Server 2000 and 2005 standard and up), then it is not a good idea as there is an overhead (plus licensing cost).

If you mean multiple databases within the same SQL instance, then that is the way to go.|||multiple databases within the same instance of sql server if its on the same machine...

sort of like this...

BOX1-SQL1 (all in same instance of sql server)
caching db
state db
auditing db

BOX2-SQL2 (all in same instance of sql server)
web site db
forum db

So THATS the way to go? Eh?
|||bumpsql