DBM schema collection config updates (#31321)

* (DOCS-11601) Updated config on schema explorer page

* (DOCS-11601) Updated MySQL config info

* (DOCS-11601) change alert box to warning box

* (DOCS-11601) SQL Server updates

Author: jeff-morgan-dd

content/en/database_monitoring/schema_explorer.md

@@ -21,7 +21,8 @@ instances:
     port: 5432
     username: datadog
     password: 'ENC[datadog_user_database_password]'
-    collect_schemas: true
+    collect_schemas:
+      enabled: true
     ## Optional: Connect to a different database if needed for `custom_queries`
     # dbname: '<DB_NAME>'
 ```

layouts/shortcodes/dbm-mysql-agent-config-examples.en.md

@@ -67,7 +67,22 @@ instances:
 
 ### Collecting schemas
 
-Starting from Agent v7.65, the Datadog Agent can collect schema information from MySQL databases. To enable this feature, use the `schemas_collection` option.
+<div class="alert alert-warning">Datadog Agent v7.65+ is required for MySQL schema collection.</div>
+
+To enable this feature, use the `collect_schemas` option. See the sample [mysql.d/conf.yaml](https://github.com/DataDog/integrations-core/blob/master/mysql/datadog_checks/mysql/data/conf.yaml.example) for more details.
+
+```yaml
+init_config:
+instances:
+  - dbm: true
+    host: localhost
+    port: 3306
+    username: datadog
+    password: 'ENC[datadog_user_database_password]'
+    collect_schemas:
+      enabled: true
+```
+**Note**: For Agent v7.68 and below, use `schemas_collection` instead of `collect_schemas`.
 
 **Note**: To collect schemas for a table, MySQL requires that the Datadog Agent has SELECT access for it. This is a [MySQL-enforced restriction](https://dev.mysql.com/doc/refman/8.4/en/information-schema-introduction.html#information-schema-privileges). Without SELECT access, the table will not appear in metadata queries.
 

layouts/shortcodes/dbm-sqlserver-agent-config-examples.en.md

@@ -80,7 +80,9 @@ instances:
 ```
 
 ### Collecting schemas
-Starting from Agent v7.56, the Datadog Agent can collect schema information from SQLServer databases running SQLServer 2017 or higher. To enable this feature, use the `schemas_collection` option. Schemas are collected on databases for which the Agent has `CONNECT` access.
+<div class="alert alert-warning">Datadog Agent v7.56+ and SQL Server 2017 or higher are required for SQL Server schema collection.</div>
+
+To enable this feature, use the `collect_schemas` option. Schemas are collected on databases for which the Agent has `CONNECT` access.
 
 <div class="alert alert-info">To collect schema information from RDS instances, you must grant the <code>datadog</code> user explicit <code>CONNECT</code> access to each database on the instance. For more information, see <a href="/database_monitoring/setup_sql_server/rds/?tab=windowshost#grant-the-agent-access">Grant the Agent access</a>.</div>
 
@@ -97,7 +99,7 @@ instances:
     connector: adodbapi
     adoprovider: MSOLEDBSQL
     database_autodiscovery: true
-    schemas_collection:
+    collect_schemas:
       enabled: true
     database_metrics:
       # Optional: enable metric collection for indexes
@@ -111,13 +113,14 @@ instances:
     connector: adodbapi
     adoprovider: MSOLEDBSQL
     database: users
-    schemas_collection:
+    collect_schemas:
       enabled: true
     database_metrics:
       # Optional: enable metric collection for indexes
       index_usage_metrics:
         enabled: true
 ```
+**Note**: For Agent v7.68 and below, use `schemas_collection` instead of `collect_schemas`.
 
 ### One Agent connecting to multiple hosts
 It is common to configure a single Agent host to connect to multiple remote database instances (see [Agent installation architectures][1006] for DBM). To connect to multiple hosts, create an entry for each host in the SQL Server integration config.