Brian Alderman | MCT, CEO / Founder of MicroTechPoint Pete Harris | Microsoft Senior Content Publisher

Meet Brian Alderman | Chief Executive Office, Founder MicroTechPoint Industry-recognized consultant Noted author and conference speaker Brian’s expertise and designs range across Microsoft operating systems More than 25 years of industry experience Brian has been focused on helping IT Pros and Database Administrators (DBAs) better understand core Microsoft technologies for over 25 years. A frequent presenter at SharePoint Conferences around the world, he has authored or contributed to several SharePoint, SQL Server, and other technical books, and is a MCSE, MCT, and MCITP: SharePoint and SQL Server Administrator. Brian has a BS and MS in Computer Information Systems where he graduated summa cum laude from Regis University of Colorado Springs and lives in Scottsdale, AZ where he enjoys playing golf year round and traveling around the world. LinkedIn /brianalderman Blog

Meet Pete Harris Content Development Manager in Microsoft’s Learning Experiences team Focuses on SQL Server and Web training With Microsoft since 1995 Part of the first team of developer training folks in the post-Microsoft University era Has built a variety of content and spoken to customers all over the world

Course Modules Database Fundamentals 01 | Introducing core database concepts (50 minutes) Define databases, example of relational database tables, and introduce common database terminology 02 | Relational Concepts (50 minutes) Normalization, referential integrity, and constraints 03 | Creating databases and database objects (50 minutes) Data types, database objects, DDL statements, and creating scripts 04 | Using DML statements (50 minutes) DML statements, using the SELECT statement; using INSERT, UPDATE, and DELETE to manage data; indexes and triggers 05 | SQL Server Administration Fundamentals (50 minutes) SQL Server security; securing database and objects; performing database backups and database restores

05 | SQL Server Administration Fundamentals Brian Alderman | MCT, CEO / Founder of MicroTechPoint Pete Harris | Microsoft Senior Content Publisher

Understanding SQL Server Security Securing SQL Server databases and objects Using SSMS to backup SQL Server databases Using SSMS to restore SQL Server databases Module Overview

SQL Server security

Database security Securing your database content is a critical part of a DBA’s job. The design, testing, and implementation of security is necessary to ensure that confidentiality is not compromised Securables are the server, database, and objects a database contains Principals are the individuals, groups, and processes granted access to SQL Server Permissions are granted to a principal for every SQL Server securable

Logins and accounts Three tiered approach to accessing content 1. SQL Server access - a login is a security principal that can be authenticated by a secure system to provide a user access to SQL Server 2. Database access - a database user is mapped to a SQL login and provides a user or group access to a database 3. Object access – permissions are applied at the object level to provide the appropriate access to the objects within the database

Server-level security Authentication is the act of verifying a user or system identity and allowing them to login using: Windows Authentication Windows user account Windows security group Mixed-Mode (Windows and SQL logins) SQL Server-specific login sa account (built-in SQL administrator) Logins can be populated into the fixed server roles or in user-defined server roles

Fixed server roles SQL Server includes several fixed server roles: Sysadmin – perform any activity on the server Dbcreator – create, alter, drop, restore databases Securityadmin –manage logins and their properties You can also create user-defined server roles that have specific permissions applied to the roles

Securing SQL Server databases and objects

Database-level security A database user is a database level security principal that must be mapped to a login at the server level in order for the user to connect to the database A login can be mapped to different databases as different users but can only be mapped as one user in each database Database users can be populated into the fixed database roles or in a user-defined database role All users are automatically members of the public database role and cannot be removed

Fixed database roles SQL Server includes several fixed database roles db_owner – perform all configuration activities db_datareader – read all data from all user tables db_datawriter – add, delete, or change data You can also create user-defined database roles that have specific permissions applied to the roles

Creating and assigning permissions to a login Demo

Guest logon accounts The guest user account is included in every database and is used by any user who accesses the database but does not have a user account within the database The guest user account cannot be dropped but it can be disabled by revoking it’s connect permission REVOKE connect FROM guest

Managing object permissions Permissions to an object can be managed by using the following commands Grant - provides a level of access to the object Deny - overrides any grant permission Revoke - removes the previously assigned permission, regardless of whether it was a deny or grant permission

Object permissions Object permissions are the permissions that allow a user to perform actions on database objects (such as tables, stored procedures, and views): SELECT INSERT UPDATE DELETE DRI (Data Referential Integrity) EXECUTE (stored procedures)

Databases backups

Database backups A database backup is performed so you can restore data if it is corrupted or lost A user may accidentally delete a table requiring the DBA to restore the table to the point it was when the last backup was performed Database backups can also be used to restore content on another SQL Server so you generate reports from that server

Common types of backups Full backup - contains all the data in a specific database, or set of filegroups or files, and also the portion of the transaction log necessary to recover all the data Differential backup - contains all the data that has changed since the differential base Incremental backup (transaction log) - contains only the data that has changed since the last full or incremental backup Other backup types

Using SSMS to backup a database Demo

Databases restores

Database restore options Restore scenarios include the following: Complete database restore – restore full database backup Differential restore – restore all changes contained in the differential backup Transaction log restore – restores a transaction log backup

Using SSMS to restore a database Demo

Summary Security terminology Securables are the server, database, and objects a database contains Principals are the individuals, groups, and processes granted access to SQL Server Permissions are granted to a principal for every SQL Server securable

Summary Three tiered approach to accessing content 1. Login – provides access to SQL Server access 2. Database user – provides access to a database access 3. Permissions provide access to database objects Grant - provides access to the object Deny - overrides any grant permission Revoke - removes the previously assigned permission Logins can be populated into fixed server roles or in user- defined server roles Database users can be populated into fixed database roles or in user-defined database roles

Summary Full backups contain all the data in a specific database or set of filegroups or files Differential backups only backs-up data since the last full backup Incremental backups only backs-up up data since the last full or incremental backup

Summary Complete database restore – restores full database backup Differential restore – restores all changes contained in the differential backup Transaction log restore – restores a transaction log backup

©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.