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
Specifies that the computation covers all the table columns. BINARY_CHECKSUM ignores columns of noncomparable data types in its computation. Noncomparable data types include
39
-
***cursor**
40
-
***image**
41
-
***ntext**
42
-
***text**
43
-
***xml**
44
-
45
-
and noncomparable common language runtime (CLR) user-defined types.
46
-
47
-
*expression*
48
-
An [expression](../../t-sql/language-elements/expressions-transact-sql.md) of any type. BINARY_CHECKSUM ignores expressions of noncomparable data types in its computation.
49
-
50
-
## Return Types
51
-
**int**
52
-
53
-
## Remarks
54
-
`BINARY_CHECKSUM(*)`, computed on any row of a table, returns the same value as long the row isn't modified later. `BINARY_CHECKSUM` satisfies the properties of a hash function: when applied over any two lists of expressions, returns the same value if the corresponding elements of the two lists have the same type and are equal when compared using the equals (=) operator. For this definition, we say that null values, of a specified type, compare as equal values. If at least one of the values in the expression list changes, the expression checksum can also change. However, this change isn't guaranteed, and so to detect whether values have changed, we recommend use of `BINARY_CHECKSUM` only if your application can tolerate an occasional missed change. Otherwise, consider using `HASHBYTES` instead. With a specified MD5 hash algorithm, the probability that `HASHBYTES` will return the same result, for two different inputs, is much lower than `BINARY_CHECKSUM`.
55
-
39
+
40
+
#### _*_
41
+
42
+
Specifies that the computation covers all the table columns. `BINARY_CHECKSUM` ignores columns of noncomparable data types in its computation. Noncomparable data types include:
43
+
44
+
-**cursor**
45
+
-**image**
46
+
-**ntext**
47
+
-**text**
48
+
-**xml**
49
+
- noncomparable common language runtime (CLR) user-defined types
50
+
51
+
#### _expression_
52
+
53
+
An [expression](../language-elements/expressions-transact-sql.md) of any type. `BINARY_CHECKSUM` ignores expressions of noncomparable data types in its computation.
54
+
55
+
## Return types
56
+
57
+
**int**
58
+
59
+
## Remarks
60
+
61
+
`BINARY_CHECKSUM(*)`, computed on any row of a table, returns the same value as long the row isn't modified later. `BINARY_CHECKSUM` satisfies the properties of a hash function: when applied over any two lists of expressions, it returns the same value if the corresponding elements of the two lists have the same type and are equal when compared using the equals (`=`) operator.
62
+
63
+
For this definition, we say that null values, of a specified type, compare as equal values. If at least one of the values in the expression list changes, the expression checksum can also change. However, this change isn't guaranteed, and so to detect whether values have changed, you should use `BINARY_CHECKSUM` only if your application can tolerate an occasional missed change. Otherwise, consider using `HASHBYTES` instead. With a specified MD5 hash algorithm, the probability that `HASHBYTES` returns the same result, for two different inputs, is much lower than `BINARY_CHECKSUM`.
64
+
56
65
`BINARY_CHECKSUM` can operate over a list of expressions, and it returns the same value for a specified list. `BINARY_CHECKSUM` applied over any two lists of expressions returns the same value if the corresponding elements of the two lists have the same type and byte representation. For this definition, null values of a specified type are considered to have the same byte representation.
57
-
66
+
58
67
`BINARY_CHECKSUM` and `CHECKSUM` are similar functions. They can be used to compute a checksum value on a list of expressions, and the order of expressions affects the resultant value. The order of columns used for `BINARY_CHECKSUM(*)` is the order of columns specified in the table or view definition. This ordering includes computed columns.
59
-
60
-
`BINARY_CHECKSUM` and `CHECKSUM` return different values for the string data types, where locale can cause strings with different representation to compare as equal. The string data types are
61
-
62
-
***char**
63
-
***nchar**
64
-
***nvarchar**
65
-
***varchar**
66
-
67
-
or
68
-
69
-
***sql_variant** (if the base type of **sql_variant** is a string data type).
70
-
71
-
For example, the strings "McCavity" and "Mccavity" have different `BINARY_CHECKSUM` values. In contrast, for a case-insensitive server, `CHECKSUM` returns the same checksum values for those strings. You should avoid comparison of `CHECKSUM` values with `BINARY_CHECKSUM` values.
72
-
73
-
`BINARY_CHECKSUM` supports any length of type **varbinary(max)** and up to 255 characters of type **nvarchar(max)**.
74
-
75
-
## Examples
68
+
69
+
`BINARY_CHECKSUM` and `CHECKSUM` return different values for the string data types, where locale can cause strings with different representation to compare as equal. The string data types are:
70
+
71
+
-**char**
72
+
-**nchar**
73
+
-**nvarchar**
74
+
-**varchar**
75
+
-**sql_variant** (if the base type of **sql_variant** is a string data type)
76
+
77
+
For example, the strings `McCavity` and `Mccavity` have different `BINARY_CHECKSUM` values. In contrast, for a case-insensitive server, `CHECKSUM` returns the same checksum values for those strings. You should avoid comparison of `CHECKSUM` values with `BINARY_CHECKSUM` values.
78
+
79
+
`BINARY_CHECKSUM` supports any length of type **varbinary(max)**, and up to 255 characters of type **nvarchar(_n_)** / **nvarchar(max)**.
80
+
81
+
## Examples
82
+
76
83
This example uses `BINARY_CHECKSUM` to detect changes in a table row.
@@ -43,10 +43,10 @@ The **database/application developer** writes Transact-SQL queries, debugs store
43
43
44
44
Recommended tools:
45
45
46
+
-**[MSSQL extension for Visual Studio Code](#mssql)**: Connect, manage database schemas, and run queries directly in Visual Studio Code
46
47
-**[SQL Server Management Studio (SSMS)](#ssms)**: Create objects, run queries, and perform lightweight tasks
47
48
-**[SQL Server Data Tools (SSDT)](#ssdt)** for Visual Studio: Schema and project-based development
48
49
-**[.NET libraries](/azure/azure-sql/database/connect-query-dotnet-core)**: Programmatic access using libraries such as `Microsoft.Data.SqlClient`
49
-
-**[Azure Data Studio](#ads)**: Lightweight scripting
50
50
51
51
### [Data analyst](#tab/analyst)
52
52
@@ -55,7 +55,6 @@ The **data analyst** runs queries, and generates reports.
55
55
-**[SQL Server Management Studio (SSMS)](#ssms)**: Run queries and perform lightweight tasks
56
56
-**[sqlcmd](#sqlcmd)**: Lightweight CLI for automation
57
57
-**[MSSQL extension for Visual Studio Code](#mssql)**: Lightweight tasks and scripting
58
-
-**[Azure Data Studio](#ads)**: Queries and visualization
59
58
60
59
### [Data engineer](#tab/engineer)
61
60
@@ -72,7 +71,7 @@ The following table lists available tools and extensions.
72
71
73
72
| Tool | Description | Operating system | Feedback |
74
73
| --- | --- | --- | --- |
75
-
|**Graphicaltools**||||
74
+
|**Graphical tools**||||
76
75
| <aid="ssms"></a> **[SQL Server Management Studio (SSMS)](../ssms/download-sql-server-management-studio-ssms.md)**| Manage SQL Server and Azure SQL databases with full GUI support. Access, configure, manage, administer, and develop all components of the SQL Database Engine on-premises and the cloud, including Azure Synapse Analytics and SQL database for Microsoft Fabric. SSMS is a comprehensive application that combines a broad group of graphical tools and a rich script editor to provide access to SQL for database administrators and developers of all skill levels. | Windows only |[Feedback](https://aka.ms/ssms-feedback)|
77
76
| <aid="ssdt"></a> **[SQL Server Data Tools (SSDT)](../ssdt/download-sql-server-data-tools-ssdt.md)**| A modern development tool for building SQL Server relational databases, Azure SQL databases, Analysis Services (AS) data models, Integration Services (IS) packages, and Reporting Services (RS) reports. With SQL Server Data tools (SSDT), you can design and deploy any SQL Server content type with the same ease as you would develop an application in **[Visual Studio](https://visualstudio.microsoft.com/downloads/)**. | Windows only |[Feedback](https://aka.ms/vs-feedback)|
78
77
| <aid="mssql"></a> **[MSSQL extension for Visual Studio Code](visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code.md)**| The official SQL Server extension that supports connections to SQL Server and Azure SQL, and a rich editing experience for Transact-SQL (T-SQL). Write T-SQL scripts in a lightweight editor. | Windows, macOS, Linux |[Feedback](https://github.com/microsoft/vscode-mssql)|
@@ -96,7 +95,7 @@ These tools are available for Windows only.
96
95
| --- | --- |
97
96
| <aid="sscm"></a> **[SQL Server Configuration Manager](configuration-manager/sql-server-configuration-manager-help.md)**| Use SQL Server Configuration Manager to configure SQL Server services and configure network connectivity. |
98
97
| <aid="dreplay"></a> **[Distributed Replay](distributed-replay/install-distributed-replay.md)** <sup>1</sup> | Use the Distributed Replay feature to help you assess the impact of future SQL Server upgrades. Also use Distributed Replay to help assess the impact of hardware and operating system upgrades, and SQL Server tuning. |
99
-
| <aid="ssbdiagnose"></a> **[ssbdiagnose](ssbdiagnose/ssbdiagnose-utility-service-broker.md)**|**ssbdiagnose** reports issues in Service Broker conversations or the configuration of Service Broker services. |
98
+
| <aid="ssbdiagnose"></a> **[ssbdiagnose](ssbdiagnose/ssbdiagnose-utility-service-broker.md)**|**ssbdiagnose** reports issues in Service Broker conversations or the configuration of Service Broker services. |
100
99
| <aid="ssma"></a> **[SQL Server Migration Assistant (SSMA)](../ssma/sql-server-migration-assistant.md)**| Use SQL Server Migration Assistant to automate database migration to SQL Server and Azure SQL from Microsoft Access, Db2, MySQL, Oracle, and Sybase. |
101
100
102
101
<sup>1</sup> Distributed Replay is supported on [!INCLUDE [sssql16-md](../includes/sssql16-md.md)] through [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] only.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments