--- title: "Add a database node" description: "Add a database for agentless scanning through a Windows Connection Manager." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/database-node/" --- # Add a database node In addition to monitoring devices, Guardian can also monitor various types of databases using a Windows Connection Manager. You can use Guardian to monitor the following database types: Applies to: `Guardian Classic` - Microsoft SQL Server. - MySQL. - Oracle. - PostgreSQL. - DB2. Monitoring a database lets you keep track of things like changes to user roles, stored procedures, and the overall schema of the database. To monitor a database, you'll ensure the relevant drivers are installed on the Connection Manager virtual machine. Then, you'll add the database as a database node in Guardian. This topic describes how to install database drivers, ensure you have a user account with the proper permissions on the database, and add a database node in Guardian. ## Dependencies To add a database node, you need: - A **Windows Connection Manager** configured in Guardian. For more information, see [Windows Connection Manager](https://docs.cloudhouse.com/guardian/classic/inventory/connection-managers/connection-managers/windows/windows-connection-manager/index.md). - The **required drivers** installed on the virtual machine running your Connection Manager. For more information, see [Database Drivers](#database-drivers). - A **user account** on the database with the necessary permissions for the database type. For more information, see [User Permissions](#user-permissions). ## Database drivers In order for Guardian to access your database, you need to have the proper drivers installed on the virtual machine running the Connection Manager. These drivers will vary depending on your database type. Use the following table to identify which drivers you need to install: !!! note When downloading drivers, select 64-bit options if options are presented. Additionally, if you want to check which drivers are already installed on your virtual machine, you can do so using the virtual machine's **ODBC Data Source Administrator (64-bit)** application. **Microsoft SQL Server** : No additional drivers are required. All required drivers are pre-installed on any operating system compatible with the Windows Connection Manager. !!! note If your Microsoft SQL Server is running on Microsoft Azure, the **Microsoft SQL Server 2012 Native Client** driver is required. To download this driver, visit [Microsoft's website](https://www.microsoft.com/en-us/download/details.aspx?id=29065). **MySQL** : The **MySQL Connector/ODBC** driver is required. To download this driver, visit [Oracle's website](https://dev.mysql.com/downloads/file/?id=453005). !!! note A free Oracle account is required to download this driver. You'll be prompted to create an account or log in using an existing account when accessing the above link. **Oracle** : The **ODAC 12c Release 3 (12.1.0.2.1)** driver is required. To download this driver, visit [Oracle's website](https://www.oracle.com/database/technologies/odac-downloads.html). **PostgreSQL** : The **PostgreSQL ODBC** driver is required. To download this driver, visit the [PostgreSQL website.](https://ftp.postgresql.org/pub/odbc/releases/REL-16_00_0005/psqlodbc_x64.msi) **DB2** : The **IBM DB2 ODBC CLI** driver is required. To download this driver, visit [IBM website](https://www.ibm.com/support/pages/db2-odbc-cli-driver-download-and-installation-information#%5B

%5DDownload%5B<%2Fh2>%5D) and select the **IBM Data Server Client Packages** download link that corresponds with your version of DB2. With the correct drivers installed, you must now ensure you have a user account set up on the database with the proper permissions for Guardian to access it. For more information, see the next section. ## User permissions Before you can add a database node in Guardian, you must ensure you have a user account with the permissions Guardian needs to monitor the database. The following table outlines the tables/catalogs the user account must be able to select in order for Guardian to effectively scan the node: !!! tip When creating this account in your database, give it a name like `guardian` so you can easily identify it. **Microsoft SQL Server** : `information_schema.routines`, `information_schema.columns`, `sys.databases`, `sys.database_principals`, `sys.indexes`, `sys.objects`, `sys.schemas` **MySQL** : `information_schema.columns`, `information_schema.global_variables`, `information_schema.statistics`, `mysql.user`, `“SHOW PROCEDURE STATUS”` **Oracle** : `ALL_DB_LINKS`, `ALL_INDEXES`, `ALL_MVIEWS`, `ALL_OBJECTS`, `ALL_SEQUENCES`, `DBA_PROFILES`, `DBA_TABLES`, `DBA_TAB_COLUMNS`, `DBA_USERS`, `ROLE_SYS_PRIVS`, `SYS.REGISTRY$HISTORY`, `V$PARAMETER` **PostgreSQL** : `information_schema.columns`, `pg_catalog.pg_roles`, `pg_catalog.pg_user`, `pg_indexes`, `pg_settings`, `pg_proc` **DB2** : `syscat.columns`, `syscat.indexes`, `syscat.roles`, `syscat.routines`, `syscat.tables`, `sysibm.sysuserauth`, `sysibmadm.dbcfg` Once you have a user account with the listed permissions, you can proceed to adding the database as a node in Guardian. Keep the **user ID** and **password** for the database account ready as you'll need them when adding the node. ## Add a database node To monitor a database, you'll add it as an Database node in Guardian. This lets you keep track of the database's schema, user roles, and more. To add a database node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. From the **Database** section, select the type of database you're using. Then, click **Go Agentless**. ![Db node 01](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/misc/db-node-01.png) 3. Here, complete the following options: ![Db node 02](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/misc/db-node-02.png) **Connection manager group** drop-down list : The Connection Manager group that is responsible for scanning your database node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Short description** field : Optional field to provide additional information about the node. **Connection string** field : This string defines certain elements required for Guardian to connect to the database. For example, the `host`, `server`, and `user ID`. The values present in this string vary depending on the database type. However, an example string with placeholder text will be displayed in this field automatically. Replace the placeholder values in the provided string with your own. !!! note The `password` value can be encrypted. If you want to encrypt the password, enter it in the **Password** field below rather than directly in the connection string. **Password** field : The password of the user account authorised to connect to the database. Guardian will take the password you enter here, encrypt it, and replace the encrypted password in the connection string in the previous field. **Host Node** drop-down list (Oracle only) : The node that hosts your Oracle database. When working with Oracle databases, Guardian must perform certain checks on the host node in addition to checks run on the database itself. Select the name of the host node from the drop-down list. 4. Once you've completed the above options, click **Scan Node** to add the database node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [Job History](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)