Re: SQL Server 2005 Security Schema Naming
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 08:25:49 +0000 (UTC)
Matt Sonic (MattSonic@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I don't have any experience working with existing databases and am having
trouble fathoming what SQL Server 2005 Schemas would be named and what
exactly they would represent.
A schema is essentially a name space. Say that you have a large database,
and there are several groups that work independently with different
applications. If each group have their own schema, they can avoid unexpected
name clashes. Since privileges can be assigned schema level, schemas can
also be used to make sure that one group does not fiddle with the tables
or procedures of other groups.
Oh, my database has about 10 - 15 major business objects. It doesn't
make sence to put each into it's own schema. An then what about the
minor ones?
There will be many databases where it will be very reasonable to have
everything in the dbo schema.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Prev by Date: Re: SQL 2005 - Windows integrated authentication
- Next by Date: Re: SQL data and web applications.
- Previous by thread: Re: SQL 2005 - Windows integrated authentication
- Next by thread: Re: SQL data and web applications.
- Index(es):
Relevant Pages
|
