5.SQL Server 2008 Database

SQL Server 2008 Database
The database is the core of SQL Server 2008, which can be used to store user information for subsequent retrieval operations, or as a temporary storage area for SQL Server operations. The previous chapters describe the installation process for SQL Server and the internal structure of the files that comprise the SQL Server 2008 database. This chapter details the process of creating a database and the various options that you can configure.

5.1 System Database
As described in chapter 1th, when installing SQL Server 2008, 5 system databases were created to store system information and support database operations. In normal database operations, we can see 4 system databases (master, model, msdb, and tempdb), but we don't see the 5th (Resource database, which is described in chapter 4th). If the instance of SQL Server is configured as a Distributor for SQL Server replication, you can create a distribution database.
5.2 User Database
The user database is created by any server login with the appropriate permissions. In previous versions of SQL Server, you could choose to install the ADVENTUREWORKS2008 sample database that was briefly described in chapter 1th, but this functionality has been removed from
Removed in the new version. AdventureWorks2008 sample database can be downloaded from Microsoft SQL Server Community Projects and Samples located on Www.codeplex.com/sqlserversamples and code examples.
5.3 Database Planning
One of the primary responsibilities of the database administrator is to manage the creation of the database. Typically, a company buys from a supplier a
Applications that require a SQL server backend but do not have comprehensive planning for data-tier support. Many times, vendors are also happy to install SQL Server instances on-site and create the necessary databases to support the application. Sometimes, however, an application vendor creates an installation program that automatically installs and supplies the S database. But many of the support for this type of installation
The configuration of the database is either inefficient or fundamentally wrong, with only a few exceptions.
This is not to say that software vendors ' application developers don't know what they're doing. Actually the problem is to

5.SQL Server 2008 Database