Simple Database concepts

System Databases

1. Master: composed of system tables that keep track of server installation as a whole and all other databases that are eventually created. Master DB has system catalogs that keep info about disk space, file allocations and usage, configuration settings, endpoints, logins, etc.
2. Model: template database. Gets cloned when a new database is created. Any changes that one would like be applied by default to a new database should be made here
3. Tempdb: re-created every time SQL Server instance is restarted. Holds intermediate results created internally by SQL Server during query processing and sorting, maintaining row versions, etc. Recreated from the model database. Sizing and configuration of tempdb is critical for SQL Server performance.
4. Resource [hidden database]: stores executable system objects such as stored system procedures and functions. Allows for very fast and safe upgrades.
5. MSDB: used by the SQL Server Agent service and other companion services. Used for backups, replication tasks, Service Broker, supports jobs, alerts, log shipping, policies, database mail and recovery of damaged pages.

Database Files

1. Primary data files: every database must have at least one primary data file that keeps track of all the rest of the files in the database. Has the extension .mdf.
2. Secondary data files: a database may have zero or more secondary data files. Has the extension .ndf.
3. Log files: every database has at least one log file that contains information necessary to recover all transactions in a database. Has the extension .ldf.

Creating a Database

1. New user database files must be at least 3 MB or larger including the transaction log
2. The default size of the data file is the size of the primary data file of the model database (2 MB) and the default size of the log file is 0.5 MB
3. If LOG ON is not specified but data files are specified during a create database, the size of the log file is 25% of the sum of the sizes of all the data files.

Expanding or Shrinking a Database

1. Automatic File Expansion:

1. The file property FILEGROWTH determines how automatic expansion happens
2. File property MAXSIZE sets the upper limit on the size

Manual File Expansion: use the ALTER DATABASE command with the MODIFY FILE option to change the SIZE property to increase the database file size

Fast File Initialization: adds space to the data file without filling the newly added space with zeros. New disk content is overwritten as new data is written to the files. Security is managed through Windows security setting SE_MANAGE_VOLUME_NAME

Automatic Shrinkage:

1. Same as doing DBCC SHRINKDATABASE (dbname, 25). Leave 25 % free space in the database after the shrink
2. Thread performs autoshrink as often as 30 minutes, very resource intensive

Manual Shrinkage: use DBCC SHRINKDATABASE if you want to shrink.

I highly recommend not to shrink the database.

Filegroups

1. Can group data files for a database into filegroups for allocation and administration purposes.
2. Improves performance by controlling the placement of data and indexes into specific filegroups on specific drives or volumes.
3. Filegroup containing the primary data file is called the primary filegroup, there is only one primary filegroup.
4. Default filegroup: there is at least one filegroup with the property of DEFAULT, can be changed by DBA.
5. Use cases when -not- to use filegroups:

1. DBA might decide to spread out the I/O for a database: easiest way is to create a database file on a RAID device.
2. DBA might want multiple files, perhaps to create a database that uses more space than is available on a single drive: can be accomplished by doing CREATE DATABASE with a list of files on separate drives

Use cases when you want to use filegroups:

1. DBA might want to have different tables assigned to different drives or to use the table and index partitioning feature in SQL Server.

Benefits:

1. Allows backup of parts of the database.
2. Table is created on a single filegroup, allows for backup of critical tables by backing up selected filegroups.
3. Same for restoration. Database can be online as soon as primary filegroup is restored, but only objects on the restored filegroups will be available.