Deploy Dataedo
In this section you'll learn how to deploy Dataedo in supported architectures. To learn basics, check the section below, or jump directly to the deployment guides:
Deployment basics
To ensure Dataedo operates effectively, you need three key components:
- Repository: for storing data
- Desktop: for importing and bulk editing
- Portal: for browsing and daily editing
For optimal performance, we recommend that you deploy these components within the same network or location to minimize latency. Ideally, they should reside in the same environment as the documented databases or data sources.
For example, if your databases are hosted on physical servers within your company, it's better to keep the Repository on-premises rather than in the cloud. If your databases are in the cloud, ensure the Repository is hosted in the same region to facilitate faster imports.
Repository
You can host the Repository on either SQL Server or Azure SQL. The easiest setup is to use the Desktop/Portal interface, but some organizations may prefer configuring the database through scripts due to internal policies. In such cases, or if must host the Repository on Azure SQL, you can execute the scripts directly.
Ensure the Portal and all Desktop users can access the Repository, which includes granting access to database users and keeping the firewall open.
Dataedo portal
The Portal should be hosted on a server or virtual machine, not on a local machine. We highly recommend Docker for its ease of maintenance. If Docker is not an option for you, you can set up the Portal on Windows, typically using Windows Server and Internet Information Services (IIS).
The Portal must have open network access to allow users to connect. When setting up the Portal, you will specify a single user account to query the database. This user account should have both user and admin roles in the database.
Users in your organization can authenticate using different methods. If you don't have an Unlimited license, the Portal will need to periodically connect to the Dataedo server to verify the license's validity.
Dataedo desktop
The desktop application requires Windows and can be installed locally. However, for recurring tasks such as imports, profiling, or data quality checks, it’s best to deploy the Desktop on a virtual machine within the same network or location as the Repository.
The Desktop must maintain a continuous connection to the Repository during operation. When performing imports, it must also have access to the relevant data source or database.
The Desktop authenticates through a database user account with user and admin roles. If you do not have an Unlimited license, the Desktop application will need to periodically connect to our server to verify your license status.
