Is there a performance hit by breaking out tables into different schemas in SQL Server?

The only place you might hit a penalty is if you don't schema qualify your queries and force the system to figure out where you're pulling from. It's an extremely minor hit, but it's there. Just write the queries correctly and you won't even have that issue.

There is no difference between querying tables from one schema or multiple schemas in the same database. I use Schemas more for grouping objects together than for anything else. To gain performance by separation, I would go towards filegroups on separate physical drives.

1 I think, from the title, "is there a performance hit..." that the OP was wondering if there was a penalty rather than a gain for doing this. – Rob Levine Apr 21 '10 at 16:07.

There should be no performance hit at all. The microsoft oslo project is using schemas extensively, and if there were performance problems, I am sure this would not have been the case.

– Andomar Apr 21 '10 at 14:59 It was the modeling project that ended up as SQL Server Modeling.En.wikipedia.Org/wiki/Oslo_%28Microsoft%29 – Oded Apr 21 '10 at 15:02.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.