docs: add Database Monitoring use case and DB-... identifiers

Author: kb-newrelic

distributions/nrdot-collector/README.md

@@ -19,6 +19,7 @@ Note: See [general README](../README.md) for information that applies to all dis
 | ATP (Host Monitoring w/ process metrics)   | `alpha`  |  N/A (new)   | [Docs](https://docs.newrelic.com/docs/opentelemetry/nrdot/atp/overview/) |
 | Gateway Mode          | `alpha`   | N/A (new)                 | [See 'Gateway Mode' below](#gateway-mode) |
 | On-Host Integrations (OHI) | `alpha` | N/A (new)                 | [ECS](https://docs.newrelic.com/docs/opentelemetry/integrations/ecs-monitoring/overview/), [ElasticSearch](https://docs.newrelic.com/docs/opentelemetry/integrations/elasticsearch/elasticsearch-otel-integration-overview/), HAProxy (Coming Soon), [Kafka](https://docs.newrelic.com/docs/opentelemetry/integrations/kafka/overview/), [NGINX](https://docs.newrelic.com/docs/opentelemetry/integrations/nginx/nginx-otel-overview/), [RabbitMQ](https://docs.newrelic.com/docs/opentelemetry/integrations/rabbitmq/overview/), Redis (Coming Soon) |
+| Database Monitoring       | `alpha`   | N/A (new)                 | [SQL Server](https://docs.newrelic.com/docs/opentelemetry/database/otel-mssql/), [Oracle DB](https://docs.newrelic.com/docs/opentelemetry/database/otel-oracledb/) |
 
 Note: While it's technically possible to have a single collector serve multiple use cases at the same time, we generally do not recommend or support this pattern due to the operational complexity that comes with it (configuration, deployment, scaling, ...). Instead we recommend deploying one collector per use case and chain them as necessary. Please note that when we say 'one collector' we refer to a logical service, not a single instance, i.e. you should still employ common scaling practices to ensure your architecture is resilient.  
 

distributions/nrdot-collector/component-inventory.md

@@ -10,6 +10,7 @@ This document maps each component in the `nrdot-collector` distribution to the u
 - **Gateway**: Gateway Mode
 - **OHI**: On-Host Integrations (shared infrastructure used across multiple integrations)
 - **OHI-{name}**: On-Host Integration specific to a product. The suffix indicates the target integration (e.g., `OHI-kafka` for Kafka monitoring).
+- **DB-{name}**: Database Monitoring specific to a database product. The suffix indicates the target database (e.g., `DB-sqlserver` for SQL Server monitoring).
 
 ## Receivers
 
@@ -31,8 +32,8 @@ This document maps each component in the `nrdot-collector` distribution to the u
 | `prometheusreceiver` | Gateway, k8s |
 | `rabbitmqreceiver` | OHI-rabbitmq |
 | `redisreceiver` | OHI-redis |
-| `nroracledbreceiver` | OHI-oracle |
-| `nrsqlserverreceiver` | OHI-sqlserver |
+| `nroracledbreceiver` | DB-oracle |
+| `nrsqlserverreceiver` | DB-sqlserver |
 | `receivercreator` | OHI |
 
 ## Processors
@@ -88,5 +89,5 @@ This document maps each component in the `nrdot-collector` distribution to the u
 | `httpprovider` | Core |
 | `httpsprovider` | Core |
 | `yamlprovider` | Core |
-| `aesprovider` | OHI-oracle, OHI-sqlserver |
-| `secretsmanagerprovider` | OHI-oracle, OHI-sqlserver |
+| `aesprovider` | DB-oracle, DB-sqlserver |
+| `secretsmanagerprovider` | DB-oracle, DB-sqlserver |