Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link: http://hub-nl.insight.com/i/692679

Contents of this Issue

Navigation

Page 89 of 212

77 C H A P T E R 5 | Broader data access 1 = row start 2 = row end generated_always_type_desc Provides a text description for the Generated Always type sys.periods period_type Name of the period period_type_desc Identifies the type of period: 1 = system-time period object_id Identifies the table containing the period_type column start_column_id Identifies the column containing the start date/time end_column_id Identifies the column containing the end date/time You can also identify temporal tables or period columns by using the system functions shown in the following table: Metadata function Property Description OBJECTPROPERTY TableTemporalType Identifies the type of table: 0 = not temporal 1 = history table 2 = current table OBJECTPROPERTYEX TableTemporalType Identifies the type of table: 0 = not temporal 1 = history table 2 = current table COLUMNPROPERTY GeneratedAlwaysType Identifies the column type for period columns: 0 = not applicable 1 = row start 2 = row end JSON JSON is data in text format. JSON is popular because its language independence and simple data structure make it easy to use in modern web and mobile applications. But despite its popularity, the simplicity of JSON means it is not suitable for many business applications that require traditional online transactional processing database design. Instead, organizations are increasingly using NoSQL databases such as Azure DocumentDB for applications characterized by read-heavy workloads and simplified, denormalized data schemas that are not subject to frequent updates. With the addition of JSON support to SQL Server 2016, you can now support both relational and nonrelational data structures in your environment and choose the appropriate model for your data requirements and workloads. Using new T-SQL functions and operators, you can easily export relational data to JSON or parse and import JSON into relational storage, even if you are working with in-memory OLTP, columnstore, or temporal relational tables. You can also write queries that combine results of relational and JSON data. Working with JSON in SQL Server is much like working with XML, except JSON is not a data type.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016