Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 182 of 212

170 C H A P T E R 8 | Improved Azure SQL Database can no longer see the masked data in the SQL Database tables unless they have the unmask privilege within the database. Developing secure applications The development of secure applications requires many decisions, including how to best manage encryption keys and where to encrypt data in the application. TDE, CLE, and dynamic data masking are all useful features, but you must also consider how encrypting data affects the design of existing implementations in order to provide full protection for your data. To address this need, SQL Database now includes the Always Encrypted feature, which introduces a set of client libraries to allow operations on encrypted data transparently inside an application. This feature makes it easier to protect data by transparently encrypting the data in the client and keeping it encrypted throughout the rest of the application stack. Furthermore, your existing application requires only minimal changes because this level of security is provided by an ADO.NET client library. That way, you configure encryption in the application layer and Always Encrypted ensures your data is encrypted in all layers of the application, whether it is at rest or in motion. Implementation of Always Encrypted for SQL Database is the same as it is for on-premises SQL Server, as described in Chapter 2. Elastic database features Microsoft has introduced elastic database features into SQL Database to simplify the implementation and management of software-as-a-service (SaaS) solutions. To optimize and simplify the management of your application, use one or more of the following features: Elastic scale This feature allows you to grow and shrink the capacity of your database to accommodate different application requirements. One way to manage elasticity is to partition your data across a number of identically structured databases by using a technique called sharding. You use the elastic database tools to easily implement sharding in your database. Elastic database pool Rather than explicitly allocate DTUs to a SQL Database, you can use an elastic database pool to allocate a common pool of DTU resources to share across multiple databases. That way you can support multiple types of workloads on demand without monitoring your databases individually for changes in performance requirements that necessitate intervention. Elastic database jobs You use an elastic database job to execute a T-SQL script against all databases in an elastic database pool to simplify administration for repetitive tasks such as rebuilding indexes. SQL Database automatically scales your script and applies built-in retry logic when necessary. Elastic query When you need to combine data from multiple databases, you can create a single connection string and execute a single query. SQL Database then aggregates the data into one result set. Managing elastic scale Sharding is not a new concept, but it has traditionally been challenging to implement because it often requires custom code and adds complexity to the application layer. Elastic database tools are available to simplify creating and managing sharded applications in SQL Database by using an elastic database client library or the Split-Merge service. These tools are useful whether you distribute your database across multiple shards or implement one shard per end customer, as shown in Figure 8-7.

Articles in this issue

Archives of this issue

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