SQL SERVER DATABASE ADMINISTRATION. Yoseph K.

Transcription

1 SQL SERVER DATABASE ADMINISTRATION Yoseph K.

2 SQL Server 2008 Backup and Recovery Introduction SQL Server 2008 Files SQL Server 2008 System Databases Creating a Basic Backup Database Recovery Models/Backup Types Using Snapshots in SQL Server 2008 What We Covered

3 Media failure. User errors, for example, dropping a table by mistake. Hardware failures, for example, a damaged disk drive or permanent loss of a server. Natural disasters.

4 Primary data files The primary data file is the starting point of the database and points to the other files in the database. Every database has one primary data file. The recommended file name extension for primary data files is.mdf. Secondary data files Secondary data files make up all the data files, other than the primary data file. Some databases may not have any secondary data files, while others have several secondary data files. The recommended file name extension for secondary data files is.ndf. Log files Log files hold all the log information that is used to recover the database. There must be at least one log file for each database, although there can be more than one. The recommended file name extension for log files is.ldf.

5 master model msdb Resource(RDB) tempdb Configure Distribution The database that records all of the system level information for a SQL Server system. The template for all databases that are created on the instance of SQL Server. The database used by SQL Server Agent for scheduling alerts and jobs, and for recording operators. msdb also contains history tables such as the backup and restore history tables. A read-only database that contains copies of all system objects that ship with SQL Server A workspace for holding temporary or intermediate result sets. This database is re-created every time an instance of SQL Server is started. When the server instance is shut down, any data in tempdb is deleted permanently. A database that exists only if the server is configured as a replication Distributor. This database stores metadata and history data for all types of replication, and transactions for transactional replication.

6 To back up a database Right click on the database Select Tasks Select Backup Select Options and select on OK

7 Use Microsoft SQL Server Management Studioto create a new Maintenance Plan. Right Click Select Maintenance Plan Wizard Click Next Two times Select Backup Database (Full) Follow the steps OR

8 Use Microsoft SQL Server Management Studioto create a new Maintenance Plan. Right Click Select Maintenance Plan Click Next Two times Bring Backup database Backup Test

9 Full Differential Transaction Log

10 Using Snapshots in SQL Server 2008 A database snapshot is a read-only, static view of a SQL Server database (the source database). The database snapshot is transactionallyconsistent with the source database as of the moment of the snapshot's creation. A database snapshot always resides on the same server instance as its source database. As the source database is updated, the database snapshot is updated. Therefore, the longer a database snapshot exists, the more likely it is to use up its available disk space.

11 CREATE DATABASE AdventureWorks2008R2_dbss1800 ON ( NAME = AdventureWorks2008R2_Data, FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Dat a\adventureworks2008r2_data_1800.ss' ) AS SNAPSHOT OF AdventureWorks2008R2; GO

12 Introduction Policy-Based Management Benefits Policy-Based Management Terms and Concepts Setting Up Naming Restrictions Controlling Feature State

13 Condition Policy Manage

14 To create the Finance Tables condition In Object Explorer, expand Management, expand Policy Management, right-click Conditions, and then click New Condition. In the Create New Condition dialog box, in the Name box, type Finance Tables. In the Facet list, select Multipart Name. In the Expression area, in the Field box, in the Operator box, select Like; and in the Value box, type 'fintbl%' to force all table names to start with the letters fintbl. On the Description page, type Finance table names must begin with fintbl, and then click OK to create the condition. Click on OK

15 To create the Finance Name policy In Object Explorer, right-click Policies, and then click New Policy. In the Create New Policy dialog box, in the Name box, type Finance Name. In the Check condition list, select Finance Tables. This is in the Multipart Name area. In the Against area you will see a list of the database objects that could apply this policy. Select the check box for Every Table. In the Every Database area, expand Every, and then click New condition. In the Create New Condition dialog box, in the Name box, type Finance Database. In the Expression box, complete the expression to = 'Finance', and then click OK to close the condition page.

16 In the Evaluation Mode list, select On change: prevent. This will enforce the policy by creating a database trigger on the Finance database. Select the Enabled list. (The Enabled box does not apply to On demand policies.) In the Server restriction list, select None. Click OK.

17 To create the Finance policy category In Object Explorer, expand Management, right-click Policy Management, and then click Manage Categories. In the Manage Policy Categories dialog box, under Name, type Finance in the blank box, and then clear Mandate Database Subscriptions. Mandate Database Subscriptions will force every database in the instance to subscribe to the policies that belong to this policy category. For this lesson, only the Finance database should subscribe to the Finance Name policy. Click OK.

18 microsoft.sqlserver.diadnostics.strace.dllshould be installed under C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE

19 Encryption steps Step 1 -Create a sample SQL Server table Step 2 -SQL Server Service Master Key The Service Master Key is the root of the SQL Server encryption hierarchy. It is created during the instance creation. Confirm it's existence using the query below. If it does not exist we need to manually create it. USE master; SELECT * FROM sys.symmetric_keyswhere name = '##MS_ServiceMasterKey##';

20 Step 3 -SQL Server Database Master Key The next step is to create a database master key. This is accomplished using the CREATE MASTER KEY method. The "encrypt by password" argument is required and defines the password used to encrypt the key. The DMK does not directly encrypt data, but provides the ability to create keys that are used for data encryption. It is important that you keep the encryption password in a safe place and/or keep backups of your SQL Server Database Master Key.

21 Step 3 -SQL Server Database Master Key The next step is to create a database master key. This is accomplished using the CREATE MASTER KEY method. The "encrypt by password" argument is required and defines the password used to encrypt the key. The DMK does not directly encrypt data, but provides the ability to create keys that are used for data encryption. It is important that you keep the encryption password in a safe place and/or keep backups of your SQL Server Database Master Key. USE DatabaseName; CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'Password123';

22 Step 4 -Create a Self Signed SQL Server Certificate: The next step is to create a self-signed certificate that is protected by the database master key. A certificate is a digitally signed security object that contains a public (and optionally a private) key for SQL Server. An optional argument when creating a certificate is ENCRYPTION BY PASSWORD. This argument defines a password protection method of the certificate's private key. In our creation of the certificate we have chosen to not include this argument; by doing so we are specifying that the certificate is to be protected by the database master key. USE DastabaseName; CREATE CERTIFICATE Certificate1 WITH SUBJECT = 'Protect Data';

23 Step 5 -SQL Server Symmetric Key A symmetric key is one key that is used for both encryption and decryption. Encryption and decryption by using a symmetric key is fast, and suitable for routine use with sensitive data in the database. USE DatabaseName; CREATE SYMMETRIC KEY SymmetricKey1 WITH ALGORITHM = AES_128 ENCRYPTION BY CERTIFICATE Certificate1;

24 Step 6 -Schema changes An Encrypted column can only be of datatype varbinaryand since the column we want to encrypt is of datatypevarchar, we have to create a new column and populate it with encrypted values. USE DatabaseName; ALTER TABLE Customer_dataADD Credit_card_number_encryptvarbinary(MAX) NULL

25 Step 7 -Encrypting the newly created column To encrypt the data we will use the encryptbykeycommand. Below is a sample code which can be used to encrypt the data. Please note that symmetric key needs to opened before we can encrypt data and be sure you manually close the key else it will remain open for the current session. OPEN SYMMETRIC KEY SymmetricKey1 DECRYPTION BY CERTIFICATE Certificate1; UPDATE Customer_dataSET Credit_card_number_encrypt= EncryptByKey (Key_GUID('SymmetricKey1'), Credit_card_number) FROM dbo.customer_data; CLOSE Symmetric Key CLOSE SYMMETRIC KEY SymmetricKey1;

26 Encryption and Decryption