Re: Definition: A Catalog vs. a Database?
- From: "John Heitmuller" <john@xxxxxxxx>
- Date: 10 Jan 2007 06:46:38 -0800
Hi Steve,
Thanks for your reply. I think I've got it.
· All SQL server databases contain catalog metadata. Every
database that I have looked at has views called sys.tables,
sys.all_views, sys.triggers, ect. These are views of the catalog
metadata for that specific individual database.
· The catalog metadata is stored in tables, just like user data.
· The catalog tables reside side-by-side with the user tables in
the database .mdf file.
· The "master" database contains a catalog like any other
database. The "data" stored in the master database supports the
management of the SQL Server (for example, information about links to
other SQL servers), but is not a "catalog" for the SQL server.
· The master database contains server level metadata. Some
people speaking informally may use the term "catalog" when
referring to this data. But, in its correct usage "catalog" only
refers to the metadata data stored in each individual database.
"Catalog" is a database level concept, not a server level concept.
My background is in Oracle. I'm preparing to take Microsoft's
70-431 exam. This seemed like a pretty fundamental concept that I
wanted to make sure I have right.
Thanks,
John
.
- Follow-Ups:
- Re: Definition: A Catalog vs. a Database?
- From: Jonathan Roberts
- Re: Definition: A Catalog vs. a Database?
- References:
- Definition: A Catalog vs. a Database?
- From: John Heitmuller
- Re: Definition: A Catalog vs. a Database?
- From: Steve
- Definition: A Catalog vs. a Database?
- Prev by Date: "Audit Object Derived Permission Event" doesnt work as documented
- Next by Date: Error message Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
- Previous by thread: Re: Definition: A Catalog vs. a Database?
- Next by thread: Re: Definition: A Catalog vs. a Database?
- Index(es):
Relevant Pages
|