[db] Add docs for context info propagation

.chloggen/db-propagate-context-info.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: db
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add doc for context information propagation
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [2162]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

docs/database/database-spans.md

@@ -13,6 +13,7 @@ linkTitle: Spans
   - [Notes and well-known identifiers for `db.system.name`](#notes-and-well-known-identifiers-for-dbsystemname)
 - [Sanitization of `db.query.text`](#sanitization-of-dbquerytext)
 - [Generating a summary of the query](#generating-a-summary-of-the-query)
+- [Propagating context to databases](#propagating-context-to-databases)
 - [Semantic conventions for specific database technologies](#semantic-conventions-for-specific-database-technologies)
 
 <!-- tocstop -->
@@ -478,6 +479,41 @@ Semantic conventions for individual database systems or specialized instrumentat
 MAY specify a different `db.query.summary` format as long as produced summary remains
 relatively short and its cardinality remains low comparing to the `db.query.text`.
 
+## Propagating context to databases
+
+**Status**: [Development][DocumentStatus]
+
+Instrumentations SHOULD propagate the context information to databases.
+
+| Attribute      | Type   | Description                           | Require level     | Stability                                                      |
+|----------------|--------|---------------------------------------|-------------------|----------------------------------------------------------------|
+| `service.name` | string | Logical name of the service [1]       | `Required`        | ![Development](https://img.shields.io/badge/-development-blue) |
+| `traceparent`  | string | The trace context of current span [2] | `Recommended` [3] | ![Development](https://img.shields.io/badge/-development-blue) |
+
+**[1] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fall back to `unknown_service:` concatenated with [process.executable.name](https://opentelemetry.io/docs/specs/semconv/attributes-registry/process/), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
+
+**[2] `traceparent`:** MUST be in the [text format](https://www.w3.org/TR/trace-context/#traceparent-header).
+
+**[3] `traceparent`:** `tracparent` have extremely high-cardinality. It's RECOMMENDED to propagate this info if the high-cardinality is safe for the behind databases
+
+Instrumentations SHOULD propagate the context information to the SQL queries following [sqlcommenter](https://google.github.io/sqlcommenter/spec/).
+
+**Examples:**
+
+- Query with `service.name`:
+
+  ```sql
+  SELECT * FROM songs /* service.name=music-player:play */
+  ```
+
+- Query with `service.name` and `traceparent`
+
+  ```sql
+  SELECT * FROM songs /* service.name=music-player:play, traceparent=00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01 */
+  ```
+
+Instrumentation SHOULD propagate `traceparent` as part of the [sqlcommenter](https://google.github.io/sqlcommenter/spec/) if high-cardinality of `traceparent` is safe to the specific databases.
+
 ## Semantic conventions for specific database technologies
 
 More specific Semantic Conventions are defined for the following database technologies:

docs/database/sql-server.md

@@ -9,6 +9,7 @@ linkTitle: SQL Server
 <!-- toc -->
 
 - [Spans](#spans)
+  - [Propagating context to SQL Server](#propagating-context-to-sql-server)
 - [Metrics](#metrics)
 
 <!-- tocstop -->
@@ -152,6 +153,23 @@ and SHOULD be provided **at span creation time** (if provided at all):
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
+### Propagating context to SQL Server
+
+**Status**: [Development][DocumentStatus]
+
+Instrumentations SHOULD propagate the context information to databases.
+
+| Attribute      | Type   | Description                           | Require level | Stability                                                      |
+|----------------|--------|---------------------------------------|---------------|----------------------------------------------------------------|
+| `service.name` | string | Logical name of the service [1]       | `Required`    | ![Development](https://img.shields.io/badge/-development-blue) |
+| `traceparent`  | string | The trace context of current span [2] | `Recommended` | ![Development](https://img.shields.io/badge/-development-blue) |
+
+**[1] `service.name`:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fall back to `unknown_service:` concatenated with [process.executable.name](https://opentelemetry.io/docs/specs/semconv/attributes-registry/process/), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
+
+**[2] `traceparent`:** MUST be in the [text format](https://www.w3.org/TR/trace-context/#traceparent-header).
+
+Instrumentations SHOULD make use of [SET CONTEXT_INFO](https://learn.microsoft.com/en-us/sql/t-sql/statements/set-context-info-transact-sql?view=sql-server-ver16) to set `traceparent` information as adding sql comments to queries changes their unique identifier in SQL Server.
+
 ## Metrics
 
 Microsoft SQL Server client instrumentations SHOULD collect metrics according to the general