A key benefit to Conductor is being able to move data between databases without needing to deal with logins, permissions or driver compatibility issues. This is all thanks to the Agents, they are responsible for moving data in and out of databases that hide behind a firewall.
If your database is not behind a firewall and is publicly accessible with credentials supplied then you will not require an Agent.
If you are having problems with your Agent and you can’t find the information you need here, ask us for help.
From this page you can monitor and see which Agent is responsible for each Data Source and destination. You can delete an Agent you no longer need simply by clicking delete, but only once it’s no longer responsible for any Data Stores. You can update a pre-existing agent by clicking Download.
Download a New Agent
To download a new Agent you must go through a new or existing Data Store, and download one there. Once this has been completed you can assign the Agent to other Data Stores as needed.
Connect an Agent
Agents automatically connect when they are downloaded. If there is a problem and an agent disconnects, just wait as it should automatically reconnect itself. There is no way to manually reconnect an agent. If necessary you can always download or update the disconnected agent or download a new one.
Remove an Agent
An Agent cannot be deleted if it is connected to any Data Stores. You will need to delete every Store the Agent is tied to, and the Processes it is running. Then you will be able to remove it from the main Agents screen.
Update an Agent
To update an agent go to the Agent page and click ‘download’ on an existing Agent.
We auto update our agents with bug fixes and improvements. If this is not selected then you may miss out on important changes to the Agent. If you are worried about updates happening at inconvenient times, you can always turn off auto updates and update manually by clicking ‘download’ on the the main Agent page any time that suits.
This lets you keep an eye on how your agents are doing. If it’s not showing any stats, you may need to click refresh to fetch the most recent data.
Having trouble with SQL Server?
An issue encountered when using the Agent to integrate data with SQL Server can prevent the agent from interacting with the database. To fix this issue, the NT AUTHORITYSYSTEM user will need to be added to any databases that you will be importing or exporting data to.
1. Open the Security Folder in SQL Server Management Studio
When you expand logins, you will see the NT AUTHORITYSYSTEM login. Double-click the user to open the Login Properties window.
2. Map the NT AUTHORITYSYSTEM user to user databases
In this case, we have a database called Scrap that we are going to use for storing application data, so we click on User Mapping and put a tick in Map and enable the user as a db_datareader and db_datawriter roles.