Articles

External Article

Checking SQL Server with Policy-Based Management

Policy-Based Management, a feature of SQL Server, is a flexible tool that can help DBAs manage one or more SQL Server instances. It's used for monitoring and enforcing a standard set of policies for SQL Server throughout an organization. While there are many built-in conditions from which to choose, Dennes demonstrates how to set up a custom policy as well as a standard one. Viewing the policy status over many servers can be tedious, so he also explains how DBAs can evaluate the states of multiple servers with just one glance.

2017-12-12

2,640 reads

Technical Article

Azure SQL Database Virtual Network Service Endpoints and Rules

One of the most commonly requested Azure SQL Database features has been support for more granular control of server-level firewall settings. A recently announced public preview of Azure SQL Database and Data Warehouse VNET service endpoints and rules promises to address this limitation.

You rated this post out of 5. Change rating

2017-12-11

2,346 reads

Technical Article

How Much Data Has Changed Since Your Last Full Backup

Have you ever wanted to know how many pages in your database have changed since the last full backup? If so, then you will be glad to hear that the SQL Server 2017 version of the DMV, sys.dm_db_file_spavce_usage, has a new column named modified_extent_page_count, which shows the number of pages that have changed since the last full backup.

You rated this post out of 5. Change rating

2017-12-08

3,696 reads

External Article

SQL Server R Services: Working with Multiple Data Sets

Although it is easy to use SQL Server R Services to create R scripts that incorporate SQL Server data by passing in a T-SQL query as an argument when calling the sp_execute_external_script stored procedure, you are limited to that one query, unless you pass additional data directly between R and SQL Server via CSV files. It is simple to do, and opens up many additional opportunities for data analysis. Robert Sheldon explains how.

2017-12-07

3,542 reads

External Article

Importing JSON Data from Web Services and Applications into SQL Server

To support many applications, it makes sense for the database to work with JSON data, because it is the built-in way for a JavaScript or TypeScript application to represent object data. It can mean less network traffic, looser coupling, and less need for the application developer to require full access to the base tables of the database. However, it means that the database must do plenty of checks first before importing. Phil Factor explains how it can be easily done.

2017-12-04

4,513 reads

Blogs

Microsoft Fabric Data Agents: Bringing Structured and Unstructured Data Together

By

Most enterprise questions do not live neatly in one place. The numbers may be...

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

I was updating my session for the Data API Builder (DAB) recently, mostly to...

Read the latest Blogs

Forums

Parameter Sensitive Plan Optimization vs. Parameter Sniffing: What SQL Server Fixes and What It Doesn't

By vgupta

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....

Hyperscale Replicas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas I

The End of Summer

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The End of Summer

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers