An Overview of Database Objects

Author: James Xavier
An instance of an RDBMS such as SQL Server contains many objects. In SQL Server an object may include such things as:

•           The database itself
•           Indexes
•           The transaction log
•           Views
•           Tables
•           Stored procedures
•           Full-text catalogs
•           User-defined functions
•           Users
•           Filegroups
•           Diagrams
•           Roles
•           Assemblies
•           Reports
•           User-defined data types

The Database Object
The database is effectively the highest-level object that you can refer to within a given SQL Server. The majority of, but not all, different objects in a SQL Server are connected to the database object. If you happen to be already knowledgeable in SQL Server you may now be stating, "What happened to logins or SQL Agent tasks?" SQL Server consists of a number of different objects that can be found in support of the database. Other than linked servers, as well as Integration Services packages, most are mainly the domain of the database administrator and, as a result, we normally don't provide them substantial thought in the course of the design and programming processes. (They are programmable via something called the SQL Management Objects (SMO),
A database is typically a group of constructs that include at least a set of table objects and, more often than not, other objects, such as stored procedures and views that pertain to the particular grouping of data stored in the database's tables.
Types of tables we store in just one database and what should go in another database?
Almost any data that is definitely considered to belong to one particular system, or possibly is substantially related, should be stored in one single database. An RDBMS , equivalent to SQL Server , could possibly have many different databases on one particular server , or it may possess only one .The amount of databases that exist on an individual SQL Server depends on such factors as capacity (CPU power, disk I/O limitations, memory, and so on), autonomy (you want one person to have management rights to the server this system is running on, and someone else to have admin rights to a different server), and just how many databases your company or client has. Some servers have only one production database; others may have many. Also, keep in mind that with any version of SQL Server that you're likely to find in production these days (SQL Server 2000 was already five years old by the time that it was renewed, as a result we'll assume the majority of establishments have that or higher), we have now the capability to have numerous instances of SQL Server that includes a separate logins and management access all on the same actual server.
Article Source: http://www.articlesbase.com/databases-articles/an-overview-of-database-objects-6853920.html
About the Author
This article was brought to you by SQLSteps, the SQL and database training company. We're a leading provider of Microsoft SQL Server courses.