views:

36

answers:

2

We're customizing a CMS that has a few hundred tables in it. We are considering moving our custom tables to a separate database on the same server.

Should we expect much of a slow down in SQL Server? There will be many multi-join stored procedures joining data across the CMS database and our custom database.

+5  A: 

should not make an impact......however you can also use a schema instead and place all your tables under that schema in the same database. This way all your stuff will be logically grouped together

SQLMenace
..and wouldn't need triggers if there's referential integrity...
OMG Ponies
...if only we could browse through different schemas in a collapse/expand kinda manner in SSMS...
Denis Valeev
@Denis you can filter by schema in SSMS - I do all the time.
HLGEM
true, but filter <> hierarchical browsing; it would be nice if SSMS did a tree view for database/Tables/Schema ->Tablelist instead of database/Tables ->Schema.Tablelist
SqlACID
+1  A: 

I would say it depends if the filegroups are the different. If they are the different, you might see the queries speed up (see SQLMenace's comment below).

My current place of employment has 3 databases that all communicate with each other on the same server, and there is no noticeable lag.

Martin
if they are on different filegroups and the filegroups are on different drives then that should be faster because you can read from 2 drives at the same time with 2 CPUs...This is why non clustered indexes are placed on different drives than the tables/clustered indexes
SQLMenace
Yep, thanks SQLMenace. I completely over-thought that one, and convinced myself of the opposite. I edited my answer.
Martin