Beyond Relational SQL Server 2008

Vinod Kumar
Technology Evangelist | Microsoft

www.ExtremeExperts.com http://blogs.sqlxml.org/vinodkumar
Connect with life

www.connectwithlife.co.in
www.ExtremeExperts.com
Session Objectives And Takeaways

SQL Server 2008 has added improved support for a variety of non-relational data management scenarios You will understand what SQL Server 2008 will offer in addition to SQL Server 2005s functionality to
Store and manage unstructured data Store and manage semistructured data
You will better understand when to use which of the presented technologies
Beyond Relational Data

Pain Points
Dealing with relational and non-relational data platforms Growth in application complexity & duplicated functionality Compensating for unavailable services
Goals
Reduce the cost of managing all types of data Simplify the development of applications which use relational and non-relational data Extend services currently available for relational data to non-relational data
SQL Server 2005

Documents & Multimedia Full Text Indexing
SQL Server 2008

Remote BLOB Store API FILESTREAM Integrated FTS Fully supported Geometry and Geography data types and Functions
Spatial
XML Data Type and Functions XML
XML Upgrades
User Defined Types

Relational Data
Large UDTs Sparse Columns Wide Tables Filtered Indices HierarchyID
Documents & Multimedia
Use File Servers

Application
BLOBs
Dedicated BLOB Store

Application
BLOBs
Store BLOBs in Database

Application
BLOBs
DB Low cost per GB Streaming Performance Complex application development & deployment Integration with structured data Windows File Servers NetApp NetFiler
DB
DB Integrated management Data-level consistency Poor data streaming support File size limitations Highest cost per GB SQL Server VARBINARY(MAX)
Advantages
Lower cost per GB at scale Scalability & Expandability Complex application development & deployment Separate data management Enterprise-scales only EMC Centera Fujitsu Nearline
Challenges
Example
Dedicated BLOB Store Store BLOBs in Database

Application
BLOB
Store BLOBs in DB + File System

Application
Application
BLOB BLOB
DB
DB
DB
Remote BLOB Storage
SQL BLOB
FILESTREAM Storage
Storage Attribute on VARBINARY(MAX)

Store BLOBs in DB + File System
Application
BLOB
Works with integrated FTS
Unstructured data stored directly in the file system (requires NTFS) Dual Programming Model
TSQL (Same as SQL BLOB) Win32 Streaming APIs with T-SQL transactional semantics
DB
Data Consistency Integrated Manageability

Back Up / Restore Administration
Size limit is the file system volume size SQL Server Security Stack
Applications can transparently support different BLOB stores Each BLOB Store vendor responsible for delivering their own providers
Applications
Remote BLOB Store API Client Provider Library Provider Library Provider Library
Provider API
Services Create Enumerate Fetch GC Delete
SQL Server
BLOB Store 1
BLOB Store 2
BLOB Store 3
Indexes stored outside SQL Server lead to manageability challenges Mixed query performance suffers from having to pull over complete full-text result set Scaling issues on big boxes
Full-Text Engine and Indexes fully integrated

Catalog, index and stopword lists now inside the database
Better performance in many common scenarios

Make mixed queries perform and scale Optimizer has knowledge about FT index SELECT * FROM candidates WHERE CONTAINS(resume,SQL Server) AND ZipCode = 98052
Exposing the FT Index content and any given WB behaviours New word breakers (WB)
Better supportability tools From 23 to over 40 word breakers/locales
Large UDTs
In SQL Server 2005, UDTs are limited to 8000 bytes
Fine for most objects, but some objects (like spatial objects) could be quite large
CLR
In SQL Server 2008, UDTs can be up to 2GB. Conceptually identical to varbinary(max)

The size of a UDT is defined on the type Large UDTs can have a size of -1, meaning they are limited to our max LOB size This size will be reflected as -1 in type metadata Will be converted to varbinary(max) or image for downlevel clients
Spatial
Storage and retrieval of spatial data using standard SQL syntax

New Spatial Data Types (geometry, geography) New Spatial Methods (intersects, buffer, etc.) New Spatial Indexes
Offers full set of Open Geospatial Consortium components (OGC/SQL MM, ISO 19125) Integration with Virtual Earth
XML
Improved XML Schema Validation

Support for storing & validating Office 12 Document formats Support for lax validation Full xs:dateTime support
Support for values without timezone timezone preservation
Improved support for lists and union types
Added support for let-clause in XQuery Added fn:upper-case()/fn:lower-case() Added support insert sql:variable(@xml) into /a/b
Semi-structured Data
Scenarios Property Bag Scenarios:
Distinct Customized property sets associated with data Large number of unique properties, user annotations Examples Document Management systems (Sharepoint) Media stores
Relational Data
Databases with Heterogeneous Record types in a table

Type specific properties, Inherited properties in a type hierarchy Examples Product Catalogs (Commerce Server), Location/business specific properties(VE), etc..
Characteristics
Relational Data
Large number of sparsely populated properties Distinct Property Sets Heterogeneous structures Sets, nested structures
Requirements
Relational Data
Efficient storage for sparse properties Efficient relational access to metadata properties: Query, DML, Indexing Ability to get/set metadata property sets generically Index subsets of relevant properties for a property set Retrieve and Analyze Hierarchical data
SQL Server 2008 Features
Relational Data
Sparse Columns: Optimized storage for sparse columns Column Sets/Wide Tables: Support thousands of sparse columns, Filtered Indexes: Ability to index a subset of rows in a table Hierarchy ID: System CLR type for hierarchical organization of data XML: for fast dynamic evolution, lists and tree objects
Sparse Columns
Relational Data
Sparse as a storage attribute on a column

Storage Optimization: 0 bytes stored for a NULL value Co-location of data: performance benefits NULL Compression in the TDS layer No change in Query/DML behavior
// Sparse as a storage attibute in Create/Alter table statements Create Table Products(Id int, Type nvarchar(16), Resolution int SPARSE, ZoomLength int SPARSE);
// No Change in Query/DML Behavior Select Id, Type, Resolution, ZoomLength from Products; Update Products set Resolution=3, ZoomLength = 105 where Id = 101;
Sparse Columns
Wide Tables/Column Sets
Relational Data
Large number of sparse columns allowed in a table (30,000 Columns, 1000 indexes, 30,000 statistics) Requires defining a Sparse Column Set
An un-typed XML column, with a published format Logical grouping for all sparse columns in a table Select * returns all non-sparse-columns, sparse column set (XML)
Allows generic retrieval/update of all sparse columns as a set

// Create a sparse column set Create Table Products(Id int, Type nvarchar(16), Resolution int SPARSE, ZoomLength int SPARSE, Properties XML COLUMN_SET FOR ALL_SPARSE_COLUMNS); // Generic relational access to sparse column set. // Returns an aggregated XML fragment for all non-null sparse columns Select Id, Type, Properties from Products; <Resolution>4</Resolution> <ZoomLength>70</ZoomLength> // Generic updates through sparse column set. Similar to an XML update Update Products set Type = Camera, Properties = @xml www.ExtremeExperts.com
Sparse Column Storage

0 Bytes stored for NULL Values
Relational Data
~20% CPU overhead for non-null value access Additional 2- 4 bytes for non-null values
Sparse columns are beneficial when space savings >40%

Non-sparse storage
PK 1 2 3 4 5 6 7 8 9 c1 A B C D E F G H I 2 3 6 3 5 7 8 1 4 5 8 9 sc1 1 2 4 6 7 sc2 sc3 sc4 sc5 sc6 sc7 sc8 sc9 9
Sparse storage
PK
sc C1 1 sc2 sc3 sc4 sc5 sc6 sc7 sc8 sc9
1 2 3 4 5 6 7 8 9
A B C D E F G H I
(sc1,sc9)(1,9) (sc2,sc4)(2,4) (sc6,sc7)(6.7) (sc1,sc5)(1,5) (sc4,sc8)(4,8) (sc3,sc9)(3,9) (sc5,sc7)(5,7) (sc2,sc8)(2,8) (sc3,sc6)(3,6)
Filtered Indexes
Filtered Indexes and Statistics
Indexing a portion of the data in a table Filtered/co-related statistics creation and usage Query/DML Optimization to use Filtered indexes & Statistics
Relational Data
Restrictions
Simple limited grammar for the predicate Only on non-clustered indexes
Benefits
Lower storage and maintenance costs for large number of indexes Query/DML Performance Benefits: IO only for qualifying rows
Filtered Indexes
ID 1 2 3 4 5 6 7 Type Camera Pant Camera Camera Pant Pant .. // Create a Filtered Indexes Create Index ZoomIdx on Products(ZoomLength) where Type = Camera; Create Index PlusSizeIdx on Products(WaistSize) where Type = Pant and WaistSize > 36 // Optimizer will pick the filtered index when query predicates match Select ProductId, Type, Resolution, ZoomLength where Type = Camera Select ProductId, Type, WaistLength, Inseam where Type = Pant and WaistLength > 38 // DML operations need to maintain indexes only when needed. Insert into Products(ProductId, Type, waistLength, inseam) values (201, Pant, 30, 32); Brand Canon Dockers Nikon Pentax Polo Dockers 5x 3x 10mb 3mb 30 40 32 32 Zoom 3x Resolution 5 Mb 38 34 WaistSize Inseam Price 300 45 600 195 65 45 ..
Relational Data
Sparse Columns & Filtered Indexes
Hierarchical Data
Scenarios
Relational Data
Forum and mailing list threads Business organization charts Content management categories Product categories Files/folders management SQL Server 2005: Parent/Child column XML datatype New in SQL Server 2008: HierarchyID type
HierarchyID
Key properties
A system data type with variable length
CLR UDT Microsoft.SqlServer.Types Varbinary encoding ( < 900 bytes)
Relational Data
/ /1/ /1/1/ /1/1/1/ /1/2/ /2/ /3/1/ /3/ /3/2/
To represent position in a hierarchy Logically encodes the path from the root of the tree to a node Rich built-in methods for manipulating hierarchies Simplifies storage and querying of hierarchical data Comparison a<b is in depth-first order Support for arbitrary insertions and deletions
/1/1/2/
Relational Data
static HierarchyId GetRoot() SqlInt16 GetLevel() HierarchyId reparent(HierarchyId oldroot, HierarchyId newroot) SqlBoolean IsDescendant(HierarchyId child) string ToString() HierarchyId Parse ( SqlString input ) HierarchyID Read ( BinaryReader r ) HierarchyID Write ( BinaryWriter r ) HierarchyId GetDescendant(HierarchyId child1, HierarchyId child2) HierarchyId GetAncestor(SqlInt16 AncesterLevel)
HierarchyID
Summary
SQL Server 2008 will make it easier to create information-centric applications that require:
Unstructured documents XML Semi-structured information combine the above with relational data
by Reducing the cost of managing all types of data Simplifying the development of applications which use relational and non-relational data Extending services currently available for relational www.ExtremeExperts.com data to non-relational data
Feedback / QnA
Your Feedback is Important!
Please take a few moments to fill out our online feedback form at:
<< Feedback URL Ask your organizer for this in advance>>
For detailed feedback, use the form at http://www.connectwithlife.co.in/vtd/helpdesk.aspx Or email us at vtd@microsoft.com
Use the Question Manager on LiveMeeting to ask your questions now!

2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

Beyond Relational SQL Server 2008

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Beyond Relational SQL Server 2008

Загружено:

Авторское право:

Доступные форматы

Vinod Kumar

Technology Evangelist | Microsoft

Connect with life

Session Objectives And Takeaways

Beyond Relational Data

SQL Server 2005

SQL Server 2008

XML Data Type and Functions XML

User Defined Types

Large UDTs Sparse Columns Wide Tables Filtered Indices HierarchyID

Documents & Multimedia

Use File Servers

Dedicated BLOB Store

Store BLOBs in Database

Documents & Multimedia

Dedicated BLOB Store Store BLOBs in Database

Store BLOBs in DB + File System

Remote BLOB Storage

Documents & Multimedia

Storage Attribute on VARBINARY(MAX)

Works with integrated FTS

Data Consistency Integrated Manageability

Documents & Multimedia

Documents & Multimedia

Documents & Multimedia

Full-Text Engine and Indexes fully integrated

Better performance in many common scenarios

In SQL Server 2008, UDTs can be up to 2GB. Conceptually identical to varbinary(max)

Storage and retrieval of spatial data using standard SQL syntax

Improved XML Schema Validation

Improved support for lists and union types

Databases with Heterogeneous Record types in a table

Sparse as a storage attribute on a column

Allows generic retrieval/update of all sparse columns as a set

Sparse Column Storage

Sparse columns are beneficial when space savings >40%

(sc1,sc9)(1,9) (sc2,sc4)(2,4) (sc6,sc7)(6.7) (sc1,sc5)(1,5) (sc4,sc8)(4,8) (sc3,sc9)(3,9) (sc5,sc7)(5,7) (sc2,sc8)(2,8) (sc3,sc6)(3,6)

Sparse Columns & Filtered Indexes

/ /1/ /1/1/ /1/1/1/ /1/2/ /2/ /3/1/ /3/ /3/2/

Use the Question Manager on LiveMeeting to ask your questions now!

Вам также может понравиться