You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"version": "[13.0,)", //Applies to SQL Server 2016 and higher
36
36
//Another example: "[12.0,13.0)" reads as "any SQL Server version >= 12.0 and < 13.0"
37
-
"platform": "/^(Windows|Linux)$/", //Applies to SQL Server on Windows and Linux
37
+
"platform": "Windows, Linux", //Applies to SQL Server on Windows and Linux
38
38
"engineEdition": "OnPremises, ManagedInstance", //Applies to SQL on Premises and Azure SQL Managed Instance. Here you can also filter specific editions of SQL Server
39
39
"name": { "not": "/^(master|tempdb|model)$/" } //Applies to any database excluding master, tempdb, and msdb
40
40
},
@@ -67,7 +67,7 @@ Demonstrates how to make a custom ruleset containing two checks. The sample cont
67
67
"target": { //Probes have their own target, usually to separate implementation for different versions, editions, or platforms. Probe targets work the same way as rule targets do.
68
68
"type": "Database",
69
69
"version": "(,12.0)", //This target is for SQL Server of versions prior to 2014
70
-
"platform": "/^(Windows|Linux)$/",
70
+
"platform": "Windows, Linux",
71
71
"engineEdition": "OnPremises, ManagedInstance"
72
72
},
73
73
"implementation": { //Implementation object with a T-SQL query. This probe is used in many rules, that's why the query return so many fields
@@ -79,7 +79,7 @@ Demonstrates how to make a custom ruleset containing two checks. The sample cont
79
79
"target": {
80
80
"type": "Database",
81
81
"version": "[12.0, 13.0)",
82
-
"platform": "/^(Windows|Linux)$/",
82
+
"platform": "Windows, Linux",
83
83
"engineEdition": "OnPremises, ManagedInstance"
84
84
},
85
85
"implementation": {
@@ -91,7 +91,7 @@ Demonstrates how to make a custom ruleset containing two checks. The sample cont
0 commit comments