Activant Solutions Inc. SQL Server 2005: Data Storage

Transcription

1 Activant Solutions Inc. SQL Server 2005: Data Storage SQL Server 2005 suite Course 2 of 4

2 This class is designed for Beginner/Intermediate SQL Server 2005 System Administrators

3 Objectives Understand how data is stored in SQL Server Creating Databases in SQL Server 2005 Managing databases in SQL Server 2005 SQL Server Security - Logins

4 This course will NOT cover SQL Server 2005 Installation SQL Server Management Basic T-SQL Language for Query Building

5 How Data is Stored Files for Database Primary Data File (.mdf) Log File(s) (.ldf) Secondary Data File(s) (.ndf) All databases have a Primary Data file and Transaction Log file File placement Place files on different disks for performance and recovery

6 Filegroups Primary Filegroup System tables and user-defined Filegroups use a proportional fill strategy Transaction Logs are NOT part of a filegroup

7 Transaction Log Running record of all transactions to the database Ensures data integrity Necessary for recovery in the event of failure Recovery mode of database needs to be FULL

8 Transaction Log How it works Data modification is sent by application. Data pages are located in or read into, buffer cache and modified. Modification is recorded in transaction log on disk. Checkpoint writes committed transactions to database.

9 SQL Server 2005 Installed Databases Master Model Msdb Temp Adventureworks Controlling database Snapshot image from which all new databases are created Stores info about tasks and alerts Used as a workspace Practice database

10 Database Objects User tables Data types Indexes View Trigger Stored Procedure Structures that contain Prophet 21 data Defines the data values allowed for a column or variable Structures used for the timely retrieval of data View of single table or multiple tables Procedure fired by SQL Server in response to a data change Is a named collection of precompiled SQL statements that execute together

11 What Occurs During Database Creation Create a data file and transaction file Creator must be part of Sysadmin (System Administrator) role to create database Allows you to define: Name of database Properties of database Location of database files

12 Data and Log File Growth Automatic file growth Specify space allocated, maximum size, and growth increment of each file Optimize performance by allocating sufficient space, setting maximum size, and setting growth increments Manually expanding data and transaction log files Automatically vs. manually which is best? Creating secondary data and transaction log files

13 Creating Data and Log Files

14 Creating Data and Log Files

15 Setting Database Options

16 Placing Database Files and Logs Managing disk storage Performance Fault tolerance Spreading data files Creating transaction logs on separate disks Placing the tempdb database

17 Database Recovery The model you choose will have a big effect on the performance of your system There are three options Full full transaction logging offers point-in-time recovery Simple transactions are truncated from the log at checkpoint Bulk Logged Recovery reduces log space consumption and improves performance Limits point in time recovery Helpful for Bulk Inserts Prophet21 does not use

18 SQL Server Security Login authentication Creating Login/User Roles

19 Choosing an Authentication Mode Advantages of Windows Authentication mode Advanced security features Adding groups as one account Fast access Advantages of mixed mode Non-Windows 2000 and Internet clients can use it to connect

20 Creating SQL Server Login NOTE: The password policy is set ON by default.

21 Roles Fixed server roles Fixed server roles are server-wide in their scope Each member of a fixed server role can add other logins to that same role. Fixed database roles Defined at the database level and exist in each database Members of the db_owner and db_securityadmin database roles can manage fixed database role membership; however, only members of the db_owner database role can add members to the db_owner fixed database role. User-defined database roles

22 User-Defined Database Roles Add a role: When a group of people needs to perform the same activities in SQL Server If you do not have permissions to manage Windows accounts

23 Managing Application Security Managing security with views and stored procedures Managing client application security with application roles Activant uses application roles

24 Summary Defined data files and transaction logs Defined common database objects Created a database Created a login and discussed roles for logins

25 For More Information SQL Server Books Online Help Files Visit Activant on the web: View Educational Services course offerings Browse Documentation Search the Solutions database Submit a Support case Professional Services Sales pss@activant.com