Database Connections


Navigation:  Data >

Database Connections

Many professionals who use Content Grabber will normally involve the use of one or more of their database servers, and a web-scraping agent can both import and export data to multiple servers. To increase performance and reliability, you can also configure an agent to have its primary database on an external server instead of using the default SQLite file database.


Development Environments

As you gain proficiency with agent development and deployment, you may find it best to use separate computing environments for the various stages: a developer environment, a testing environment, and a production environment. Each of these environments will typically have its own database, and so the database connections in your agent will need to change when you move an agent from development into testing, and then from testing into production.


Unique Database Names on Your Network

To make it easier to move agents between different computer environments, you can configure network database connections - each of which has a unique name on the network. Using such names will allow for an automatic switch to a new connection if the agent moves to another computer on the network. Also, we recommend that you take this approach, even if you are only using a single computer to design and run agents, since you won't have to configure a new database connection each time you create an agent.


Another benefit of using unique-name database connections is the agent will contain only the name of the connection. This design gives additional security when you send agents to others, since the agent will contain no database connection information.


If you don't configure a network database connection, then the connection will be known only to the agent in the location that you configure the agent. You can use the database connection anywhere in the agent, but it will be unknown to other agents.