SQL Server System Overview Eric Bortei-Doku

Transcription

1 17-18 March, 2018 Beijing SQL Server System Overview Eric Bortei-Doku

2 Agenda SQL Server High Level Feature Overview Introduction to Open Specifications SQL Server Open Specifications Core Platform Protocol Areas SQL Server Protocol Sample Use Case (MS-TDS)

3 SQL Server High Level Feature Overview DATA SOURCES DATA MANAGEMENT DATA INSIGHTS Structured Operational data Business intelligence OLTP MOBILE ERP An industry leader four years in a row Analytics at a fraction of the cost on any device $480 $2,230 LOB Unstructured Graph Social IoT Media Data virtualization PolyBase Data warehousing Big data processing Scale to petabytes T-SQL query over any data PB 1010 { } 0101 #1 #2 #3 Data integration SSIS Advanced Analytics 1M predictions per second Support for R and Python $120 Microsoft Tableau Oracle R + FLEXIBILITY Any language, any platform, anywhere.net JAVA Azure 3 rd

4 Introduction to Open Specifications

5 Open Specifications These specifications allow us to: Be more open in our business practices, and offer greater interoperability with our products Work better with the industry and continue to improve relationships with customers, students, and partners

6 SQL Server Open Specifications

7 Technical Documents Open specification docs also called technical docs SQL technical docs cover: File formats Data portability Protocols Standards Available in different formats: DOCX PDF HTML

8 Technical Document Structure SQL technical documents have the following structure: Introduction Informative sections Typically sections 2 & 3. Describe the protocol, file format etc. in technical detail Normative sections Remaining sections. Provides explanations, examples and references Productive behavior appendix Lists the Microsoft products (and their versions) that content applies to

9 Technical Document Language & Sections Prescriptive language used to clarify the technical requirements for an implementation. Required behavior: MUST, MUST NOT Optional behavior: MAY, SHOULD, SHOULD NOT Terms used as defined in [RFC 2119] Restricted to normative sections by using the appropriate template:

10 Other Technical Docs Preview Specifications Advance copies of new or modified protocols Typically published with the public BETA previews of a Microsoft product Documents are not complete, and the information is subject to change with the final release of the software

11 Other Technical Docs Errata Occasional updates are made to the documents to clarify information or to correct errors The Support group works with the customer to resolve the issue Microsoft then corrects the document and issues an Errata update in order to inform all implementers

12 Other Technical Docs Overview Document (MS-SSSO) Defines SQL Server protocol families Scenario-Based Walkthroughs and examples for: Instance discovery Client Connection Report management, authoring and reviewing Authentication and authorization Query processing and many m e

13 Other Technical Docs - Data Portability Mechanisms by which user-created data in SQL Server can be extracted for use in other software products These mechanisms include import/export functionality, documented APIs, industry-standard formats, and documented data structures and file formats Data Portability MS-DPSSAS File Format MS-BCP

14 SQL Server Core Platform Areas

15 Core Platform Protocol Areas Database Engine Analysis Services Reporting Services Master Data Services Complex Event Processing Engine Manageability

16 Database Engine Core service for storing, processing, and securing data. Collection of protocols for application runtime purposes and application management purposes

17 Analysis Services Supports online analytical processing (OLAP) Implementers are enabled to design, create, and manage multidimensional and tabular structures.

18 Reporting Services Reporting Services delivers enterprise, Web-enabled reporting functionality Scenarios: Author, Publish & Manage reports

19 Master Data Services Master data management (MDM) capabilities Provide customers with a single authoritative data source to ensure the integrity of the data

20 Complex Event Processing Engine Complex Event Processing (CEP) engine is separate no dependencies on SQL Server and its other components Client App uses Complex Event Processing Manageability (CEPM) protocol to communicate with CEP engine

21 Manageability Part of the database engine, uses Database Publishing Wizard Protocol (MS-SSDPWP) Allows a user to publish an existing database to a remote server via a web service

22 SQL Server Functional Architecture

23 SQL Server Protocol Use Case MS-TDS (Quick intro)

24 MS-TDS High Level Overview Tabular Data Stream (TDS) protocol is an application layer request/response protocol, allows interaction with a database server and provides: Authentication and channel encryption negotiation Transfer of requests & commands (like BULK INSERT) Mechanism for invoking stored procedures, remote procedure calls Data return Transfer of Transaction Manager requests

25 MS-TDS Communication Sequence States Pre-Login state Client initiates communication with initial PRELOGIN packet Server responds ( equen e n nue ) Login state Client sends TDS Login request to server with SPNEGO packet Server responds (sequence continues) Post-Login state Server ready to accept SQL commands from client For example, client sends BULK INSERT command to server See [MS-TDS] section 3.1.5

26 MS-TDS Pre-Login Communication Sequence

27 MS-TDS BULK INSERT Communication Sequence

28 Resources Open Specifications SQL Server Technical Documents [MS-TDS] - Microsoft Tabular Data Stream protocol specification Interop Events website Support Forums Protocols