Re: Many Schemas

Suggest you look on technet for the topics: 'Label Security" and "Fine Grained Security" (Don't let the word Security stop you - I think it's relavent here)

Label security is an option that gives definitive separation within a single table - no views necessary, reasonable performance, etc. Has reasonable Admin support as well.

Fine Grained Security allows you to build (and maintain) your own flavor.

/Hans

Brian Tkatch wrote:

> In a case where one company is providing a service for other companies
> (hundreds, possibly thousands). The same service for each one. Would
> it be better to give each company their own schema or to have one
> schema and use a foreign key to separate the common lists. Obviously
> there are many points to consider, but I do not know where to start.
>
> By separating them, I would assume that aggregate reports are harder
> to maintain, and longer to run. I am just guessing that accessing
> hundreds of small indexed tables would be slower than accessing one
> large one (indexed as well).
>
> The individual queries on the system would probably be faster, for the
> lesser amount of rows. And, updates are less likely to ruin the system
> by a careless mistake, because schemas must be directly referenced.
>
> Any *pointers would be appreceated.
>
> Brian
Received on Mon May 14 2001 - 21:32:54 CDT