Configure the Target Server Database Properties File

During installation, a target server database properties file (target_database.properties) is created based on the database connection information you provided. You can configure the target_database.properties files to change the values that you chose during installation or create more target_database.properties files to connect to other instances.
wlasql113
During installation, a target server database properties file (
target_database
.properties) is created based on the database connection information you provided. You can configure the 
target_database
.properties files to change the values that you chose during installation or create more 
target_database
.properties files to connect to other instances.
When naming the target server database properties file, use only alphanumeric characters and underscores (_). The first character must be alphabetic.
If the target database is specified in the job definition, the agent uses the corresponding properties file. For example, if localdb is specified in the job definition, the agent uses the localdb.properties file to connect to the SQL Server instance.
If the target database is not specified in the job definition, the agent uses the default value that is specified in the mssql.default.TargetDB parameter in the agentparm.txt file. For example, if the mssql.default.TargetDB parameter is set to defaultdb, the agent uses the defaultdb.properties file to connect to the SQL Server instance.
You can also override a default property in the system properties file by defining the property in the 
target_database
.properties file. A system property that is defined in the 
target_database
.properties file overrides the value of the same property in the system properties file.
In addition to the properties defined in the system properties file, the 
target_database
.properties file can contain the following properties:
  • db.url 
    Specifies the JDBC URL. The agent constructs the JDBC URL based on the database connection information you provided during installation. You can modify this property to use a custom JDBC URL.
    Example:
     jdbc:jtds:sqlserver://localhost:1433/msdb
    If you are using a dynamic port, the database instance name is required, for example: jdbc.jtds.sqlserver://remotehost/msdb;instance=ProdInstance.
  • db.username
    Specifies the user that the agent uses to create a JDBC connection to a SQL Server instance. The user can be a Windows domain user for Windows domain authentication or a SQL Server user for SQL Server authentication.
  • db.password
    Specifies the password for the user name.
    To avoid specifying passwords in job definitions using the CLI, we recommend that you set up a default user. As the
    target_database
    .properties file can contain encrypted passwords, we recommend that you secure and restrict access to the agent directories and their contents.
    The password must be encrypted. To encrypt a password, use the Password utility that is provided with the agent.
  • db.domain
    Specifies the Windows domain name for Windows authentication.
    • If the db.domain argument is specified, the agent assumes that the db.username property contains the Windows domain user. In this case, Windows domain authentication is used.
    • If the db.domain argument is not specified, the agent assumes that the db.username property contains the SQL Server user. In this case, SQL Server authentication is used.
Example: Windows Domain Authentication
This example shows a 
target_database
.properties file that uses Windows domain authentication:
db.url=jdbc:jtds:sqlserver://localhost:1433/msdb db.username=AUSER db.password=3B38CA1614D55535 db.domain= MYDOMAIN
Example: Dynamic Port
This example shows the previous 
target_database
.properties file using a dynamic port:
db.url=jdbc:jtds:sqlserver://localhost/msdb;instance=MYDBINSTANCE db.username=AUSER db.password=3B38CA1614D55535 db.domain= MYDOMAIN