mirror of
https://github.com/Microsoft/sql-server-samples.git
synced 2025-12-08 14:58:54 +00:00
Removed json lang identifier from snippets
This commit is contained in:
@@ -22,10 +22,10 @@ Demonstrates how to make a custom ruleset containing two checks. The sample cont
|
||||
|
||||
```
|
||||
{
|
||||
"target": { /*Target describes a SQL Server object the check is supposed to run against*/
|
||||
"target": { //Target describes a SQL Server object the check is supposed to run against
|
||||
"type": "Database", //This check targets Database object
|
||||
"version": "[13.0,)", //Applies to SQL Server 2016 and higher
|
||||
/*Another example: [12.0,13.0) reads as any SQL Server version >= 12.0 and < 13.0*/
|
||||
//Another example: "[12.0,13.0)" reads as "any SQL Server version >= 12.0 and < 13.0"
|
||||
"platform": "/^(Windows|Linux)$/", //Applies to SQL Server on Windows and Linux
|
||||
"engineEdition": "OnPremises, ManagedInstance", //Applies to SQL on Premises and Azure SQL Managed Instance. Here you can also filter specific editions of SQL Server
|
||||
"name": { "not": "/^(master|tempdb|model)$/" } //Applies to any database excluding master, tempdb, and msdb
|
||||
@@ -50,7 +50,7 @@ Demonstrates how to make a custom ruleset containing two checks. The sample cont
|
||||
|
||||
`Probes` describes how and where to get the required data to check compliance with a rule. You can use T-SQL queries as well as methods from some assemblies. The probe below uses a T-SQL query.
|
||||
|
||||
```json
|
||||
```
|
||||
"Custom_DatabaseConfiguration": [ //Probe name is used to reference the probe from a rule
|
||||
//Probe can have a few implementations that will be used for different targets
|
||||
//This probe has two implementations for different version of SQL Server
|
||||
|
||||
Reference in New Issue
Block a user