Create a JDBC type data source
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Data Management
Create a JDBC type data source record to define what data an import set should import.
Before you begin
About this task
Procedure
- Navigate to All > System Import Sets > Administration > Data Sources.
- Click New.
-
Complete the form.
Field Description Name A unique name for this data source. Import set table label A label for the import set staging table to use. Import set table name The ServiceNow AI Platform uses the label you entered to construct a unique table name. This prevents namespace collision with an already existing table. Type JDBC. Use MID Server MID Server to use to connect to this data source. Format Select one of the following formats: MySQL, Oracle, or SQLServer. Instance name Used to support dynamic port connectivity with SQL Server. To ensure connectivity, provide the instance name for a SQL Server that receives a new port number dynamically after each reboot. This field only appears when SQLServer is selected as a data source format. Database name Name of the database instance. Database port Port number for the database. Leave this field empty when using dynamic port connectivity with SQL Server. Use Batch Import If selected, specifies that loading data should be batched when you click Load data or Test load 20 records. Batch Size Specifies how big the batches should be. Appears only when the Use Batch Import field is selected. The glide.import_set_load_usebatch and glide.import_set_load_batch_size properties affects these fields. The priority order for the properties and fields are as follows: If the property is set, use the property value. If not, use the field value. If neither property is set, use the default batch size of 1000.- For example, if glide.import_set_load_usebatch = true and glide.import_set_load_batch_size = 200, use 200 as the batch size, regardless of the field values.
- For example, if glide.import_set_load_usebatch = true and the glide.import_set_load_batch_size property is not set, use the default batch size of 1000.
- For example, if the glide.import_set_load_usebatch property is not set and the Use Batch Import field = true, use the Batch Size field value (or the default of 1000 if the Batch Size field value is not set)
- For example, if the glide.import_set_load_usebatch property = false and the Use Batch Import field = true, do not use batch import, since the property is set to false.
Use integrated authentication Selected to allow the JDBC connection to use the ID of the user configured for the Windows MID Server service for SQL Server authentication. For additional details, see JDBC type data source. Username User name for authentication on the JDBC server. Password Password for authentication on the JDBC server. Server Name of the server from which the tables will be imported. Query Type of query to run: All rows from Table or Specific SQL. If you select to run a SQL statement, the SQL statement field appears. Query timeout Number of seconds the JDBC driver will wait for a query (SELECT) to complete. Zero (0) means no timeout. If timeout is exceeded, the integration considers the JDBC result inaccessible and places it in an error state. Connection timeout Number of seconds before MID Server connection cache pool closes and removes it from the pool. Zero (0) means no timeout. Table name Name of the table from which the data is being exported. SQL statement SQL statement to extract the desired data from the database. Use last run datetime Controls the amount of data that is retrieved from a database during an import run. If unselected, then all rows in the table specified are imported, every time. You might want to use this setting if this is a one-time import, or if all the data in the target table is new. If selected, two additional fields appear, enabling you to select a datetime value to limit imported data to delta values only. Last run datetime The datetime value in this field is automatically populated from the database field you select below and represents the latest value from the previous run. This value acts as a dynamic filter to restrict the number of records retrieved to those records that have changed since the data source's last runtime. Last run database field Field name from the source table that will be used as the filter in the next run. This value may need to be case sensitive, depending on the target database type. Additional Database Parameters Optional parameters to add to the end of the URL generated for this data source. Semicolon-separated list of parameters. You may need to configure the form to view this field. - Click Submit.
What to do next