StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17074143
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-12T19:55:18.567
FavoriteCount
0
LastActivityDate
2013-06-12T19:55:18.567
LastEditDate
LastEditorUserId
0
OwnerUserId
1144035
ParentId
17073676
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If you are new to SQL Server and to databases in general, then the concept of schema probably is confusing. A basic understanding is: <pre><code>A schema is the unit of security (as described [here][1] if you must know). A database is the unit of backup and recovery. </code></pre> If you are new to SQL Server, security may not be top on your mind. You think "users have access to databases, so databases are the unit of security". Not only does that make sense, but that is how many databases implement security. However, it is not particularly flexible. Say we are both working in a database, and I want to give you execute permissions on all my stored procedures -- even ones I create in the future. With a schema, it is easy. I grant you execute permission on the schema, anything new you can use. If I had to do this at the database-level, then I would have a few inferior options: <ol> <li>Grant you access to all stored procedures. Even the one that deletes everything on the server that only special people have access to. And, even the ones developed by someone else in the database.</li> <li>Grant you access to all existing stored procedures. But then I add a new one for the application, and your application stops working.</li> <li>Break everything up into different databases, but then that becomes a management nightmare.</li> </ol> This is only intended as an example of how schemas manage security within a database. SQL Server makes them pretty easy to use by defaulting everything to <code>dbo</code> (which stands for "database owner"). Their power only becomes apparent when you have a situation needing them. In the meantime, just get used to using <code>dbo</code> in certain contexts (such as four-part naming for accessing objects on linked servers and for calling user-defined functions).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POa better understanding of Schema in SQLServer
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGordon Linoff
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.