Rules added to a SQL Server unit test action to judge its outcome, for example Row Count, Scalar Value, Expected Schema or Data Checksum. Freshly created tests include one marked Inconclusive.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Test conditions in context, with comparison tables and the common traps.
Terms in this definition
- SQL Server
The relational database from Microsoft that organisations host and run themselves, in their own data centres or on VMs. Its engine also sits underneath the Azure SQL services and SQL database in Fabric.
- COUNT
A DAX function returning how many non-blank numbers, dates or text values a column contains. Boolean columns need COUNTA instead, and for counting the rows of a table COUNTROWS is the better choice.
- Scalar
A Git tool that began at Microsoft and tunes clones of huge repositories for speed. It replaces VFS for Git, and Microsoft Learn points to it, Git LFS or Azure Artifacts when a repository grows too big.
- Schema
The middle part of a Unity Catalog name (
catalog.schema.table), grouping tables, views, volumes, functions and models inside a catalog. A grant on it covers everything in it now and later, and nothing inside can be reached withoutUSE SCHEMA. - Checksum
Confirms that a check digit in text found by a custom sensitive information type's regex is correct, calculated from weights and a mod value. The advanced version can only be set up in PowerShell XML.
Related terms
- SQL Server unit tests
Visual Studio SSDT tests that execute T-SQL against a test database, with test conditions deciding whether each outcome passes.
- WAF custom rules
WAF rules you define yourself, of match or rate-limit type, that are processed ahead of managed rules and can test conditions like geo-location, IP, headers or URI.