|
<< Click to Display Table of Contents >> ODS Operational Data Store |
There are business scenarios in which you may want to expand the features integrated with Bizagi using business report tools such as report generated with Tableau, PowerBI, and SQL Server reporting services, among others.
To expose the data for reporting tools with the most updated information Bizagi features ODS.
Bizagi's ODS creates a separate replica of the Production, Test and Development database with read-only capabilities for custom reporting purposes. This allows you to execute queries without affecting the performance of your processes within the main transactional database.
For each environment, a distinct server and database is set up to maintain data segregation and is deployed within the same region to minimize latency.
The replicated database is accessed through a connection string provided in the Onboarding process by Bizagi, with a SQL name, a user and a password.
There are two options to access the ODS:
Through Private access, or through Public access.
1.Private access:
a.VPN access: Establishes a private, secure connection to the ODS from the customer's network.
b.VNet peering: Ideal for customers with Azure resources that need to access the ODS from Azure.
2.Public access: Offered when the customer opts not to use a VPN due to internal policies or preferences.
The following table can help you identify the best option to access your ODS:
Criteria |
Private Access (VPN/Vnet Peering) |
Public Access |
|---|---|---|
Security |
Restricted internet access. Only accessible through VPN, and security is enforced with robust layers provided by Azure. Data is encrypted via TCP 1433. |
Public access is restricted based on the source's public IP, and security is enforced with robust layers provided by Azure. Data is encrypted using TCP port 1433. |
Performance |
It depends on the performance of the VPN tunnel. |
It depends on the performance of the internet connection. |
Setup Complexity |
It requires VPN setup and maintenance, as well as configuring a private DNS record. |
It's easier to set up, as only the public source IP is required. |
Access Control |
Strict access control is shared with the client because it depends on domain encryption and rule settings. |
Access is easier to manage by authorizing IPs through tickets. |
Use Case |
Ideal for environments needing strict isolation. VNet peering is only available for customers with Azure resources |
Suitable for environments where easy access is a priority. |
Last Updated 11/26/2024 2:50:20 PM