13. JSON C# Libraries Parsing JSON Files “Deserialize” OR Generating JSON Files “Serialize” JavaScriptSerializer.NET Class JSON.NET Library (available on NUGET) Check https://mva.microsoft.com/en-US/training-courses/introduction-to-json-with-c- 12742https://mva.microsoft.com/en-US/training-courses/introduction-to-json-with-c- 12742

14. JSON integration Primer on JSON JSON in HTML5 & JavaScript JSON in C# - parsing & storing JSON JSON in DocumentDB SQL Server 2016 and JSON

15. Not only SQL vs SQL overview SQL Server Database Engine Azure SQL Database Relational (SQL) Non-relational (NoSQL) Analytical Azure managed data service Operational Microsoft Analytics Platform System

16. SQL and NoSQL fully featured RDBMS transactional processing rich query managed as a service elastic scale internet accessible http/rest schema-free data model arbitrary data formats

17. Fast, predictable performance Tunable consistency Elastic scale DocumentDB overview A NoSQL document database-as-a-service, fully managed by Microsoft Azure. For cloud-designed apps when query over schema-free data; reliable and predictable performance; and rapid development are key. First of its kind database service to offer native support for JavaScript, SQL query and transactions over JSON documents. Perfect for cloud architects and developers who need an enterprise-ready NoSQL document database. Query JSON data with no secondary indices Native JavaScript transactional processing Familiar SQL-based query language Build with familiar tools – REST, JSON, JavaScript Easy to start and fully-managed Enterprise-grade Azure platform

18. DocumentDB at Microsoft over 425 million unique users store 20TB of JSON document data under 15ms writes and single digit ms reads store for 40+ app / device combinations available globally to serve all markets user data store

19. The basics Resource model Entities addressable by logical URI Partitioned for scale out Replicated for high availability Entities represented as JSON Accounts scale out through addition of capacity units Interaction model  RESTful interaction over HTTP  HTTP and TCP connectivity  Standard HTTP verbs and semantics Development .Net, Node, Python, Java and JavaScript clients  SQL for query expression,.Net LINQ  JavaScript for server-side app logic 101 010 DocumentDB account Databases Users Permissions Collections Documents Attachments Stored procedures Triggers User-defined functions your Documents here { } JS

20. DocumentDB A document store Collections Document 1Document 2 Document 3 Document 4 DocumentDB Application { "name": "John", "country": "Canada", "age": 43, "lastUse": "March 4, 2014" } { "name": "Lou", "country": "Australia", "age": 51, "firstUse": "May 8, 2013" } { "docCount": 3, "last": "May 1, 2014" } { "name": "Eva", "country": "Germany", "age": 25 } JSON

24. Storage? SQL Server is not a specialized document store! DocumentDB is!

25. Handling variety of data and model changes Modern services exchange data in JSON format Information are stored in JSON format Store and query both relational and JSON data Combination of relational and JSON data Fast built-in JSON/relational data conversion The power of T-SQL and SQL Server engine Integration with all SQL Server components Benefits Drivers Pillars

26. [ { "Number":"SO43659", "Date":"2011-05-31T00:00:00" "AccountNumber":"AW29825", "Price":59.99, "Quantity":1 }, { "Number":"SO43661", "Date":"2011-06-01T00:00:00“ "AccountNumber":"AW73565“, "Price":24.99, "Quantity":3 } ] SO436592011-05-31T00:00:00MSFT59.991 SO436612011-06-01T00:00:00Nokia24.993 Table 2 JSON Formats result set as JSON text. JSON 2 table Transforms JSON text to table Built-in functions ISJSON JSON_VALUE JSON_MODIFY

29. SELECT* FROM OPENJSON (@json) WITH ( Number varchar(200) N'$.Order.Number', Date datetime N'$.Order.Date', Customer varchar(200) N'$.Account', Quantity int N'$.Item.Quantity' ) SO436592011-05-31T00:00:00Microsoft1 SO436612011-06-01T00:00:00Nokia3

30. SO436592011-05-31T00:00:00MSFT59.991 SO436612011-06-01T00:00:00Nokia24.993 SELECTNumber AS [Order.Number], Date AS [Order.Date], Customer AS Account, Price AS 'Item.UnitPrice', Quantity AS 'Item.Qty' FROM SalesOrder FOR JSON PATH