SQL Server 2005 RDBMS Technical Overview Matthew Stephen IT Pro Evangelist (SQL Server) Microsoft Ltd.

Agenda Introduction Manageability enhancements Security enhancements Availability enhancements

Secure, reliable, and productive database platform for line-of-business and analytical applications High availability for enterprise applications Security enhancements Focus on manageability; self optimization Enterprise Data Management Developer Productivity Business Intelligence Integration with Visual Studio® and.NET Native XML technology Interoperability: open standards, Web services Comprehensive ETL solution Real-time decision making: reporting, data mining Scalability and availability enhancements Introduction Empowering Productivity

Manageability New Management Tools New: SQL Server Management Studio New rich GUI Integrated management Supports all SQL Server components Replaces: Enterprise Manager Query Analyzer Analysis Services Manager

Manageability Management Studio Object Explorer Create databases and data sources Control privileges and permissions Configure replication Manage SQL Server Agent Ω

Manageability Tuning Tools XML Show Plan Publicly available Schema Programmatic access Portability Database Tuning Advisor Time bound tuning What-if analysis Scalability Ω

Manageability Diagnostic Tools Dynamic Management Views Server transparency “sys.memory_clerks”“sys.schedulers” SQL Profiler Integrated with Performance Monitor Deadlock graph Integrated Event Logs Ω

Security Feature Enhancements Authorization Enhancements User schema separation Module execution context Granular permission control Encryption enhancements Auditing DDL triggers Events Ω

Security User-Schema Separation New DDL for user and schemas CREATE/ALTER/DROP for USER, ROLE, and SCHEMA Dropping user does not require application rewrite

Security DROP USER => Application Rewrite App1 App2 SELECT custID FROM User1.OrdersTable App1 Modified App2 modified OrdersTable InsertOrderProc SELECT custID FROM User2.OrdersTable Exec User1.InsertOrderProc Exec User2.InsertOrderProc Owning user = User1 SCHEMA = User1 Owning user = User2 SCHEMA = User2

Security Solution: User-Schema Separation User Database Object Schema Contained in Owned by Owned By Table View Stored Proc Function User 2 Owned by Drop user does NOT require application change!

Security User-Schema Separation Each schema has an owning principal – user or role Each user has a default schema for name resolution Object creation inside schema requires CREATE permission and ALTER or CONTROL permission on the schema Example: Creation of table in schema requires CREATE TABLE permission and ownership of schema or ALTER or CONTROL on schema Role1User1 Owns Has default schema Owns Approle1 Owns Schema1Schema2 Schema3 SP1 Fn1 Tab1 Database

Security Execution Context User 3 Select Perms checked for User3 Execute Perms checked for User3 User1.Proc1 User1.T1 NO Perms checked for User3 User 3 User2.Proc1 User1.T1 ‘Execute AS ‘X’ ’ Execute Perms checked for User3 Select Perms checked for ‘X’. Not for user3 SQL Server 2005 SQL Server 2000 User2.Proc1User1.T1

Security Module Execution Context Execute AS CALLER Execute AS “UserName” Execute AS SELF Execute AS OWNER

Security Certificates Encryption enhancements Encryption uses symmetric keys, asymmetric keys and certificates SQL Server 2005 can generate certificates for encryption RC4, RSA, Triple-DES and AES encryption supported Encryption can be used with any level of SQL Server 2005 securable objects

Availability Table Partitioning SQL Server 2000 allowed partition views SQL Server 2005 allows partitioned tables and indexes Increases performance on multiprocessor machines Eases management of data – data can be grouped logically Data movement easier Three steps Create the partition function Create the partition scheme Create the partitioned table Ω

Availability Snapshot Isolation Increased data availability for read applications Allows non-blocking consistent reads in an OLTP environment Writers don’t block readers Readers don’t block writers Scenarios Read-mostly database with relatively few writes – Reporting Migration from Oracle to SQL Server

Availability Database Snapshots Snapshot of a database at a point in time Created instantly Read only Does not require a complete copy of the data Shares unchanged pages of the database Requires extra storage only for changed pages Uses a “copy-on-write” mechanism Recover from User, Application or DBA error Rewind database to Database Snapshot

Availability Other Maintenance Features Dedicated Admin Connection Access to Server when regular connections fail Online page and file restore Database remains online Online index maintenance Fast recovery Database is available when undo begins UndoRedo Available

Session Summary New integrated management tools New privileges Secure by design, by deployment, and by default Reduced attack surface Separate service accounts Fine grained access security Expanded and enhanced availability options Partitioning New restoration features New replication features

© 2003 Microsoft Corporation. All rights reserved.

Resources Microsoft SQL Team blogs Microsoft SQL Server community on the web SQL Server Integration Services on the web SQL Server Developer Center Microsoft SQL Server 2005 website SQL Newsgroups SQL Server 2005 Datamining