Version 26.3
1. Overview
Dundas BI, now Simba Custom Analytics, is a web-based server application that can run on Windows or Linux or in containers, using SQL Server/Azure SQL or PostgreSQL databases for storage.
Users can then log on from any device using a supported web browser and connect to a variety of other databases and data sources, which may require additional drivers to be installed.
2. Client
One of the following is required for client-side devices, and a recent version is recommended:
Desktop:
- Chrome
- Firefox
- Safari
- Microsoft Edge
Mobile:
- iOS
- Android - Android Chrome browser only
3. Server
Below are the hardware and software requirements for installing on your own server, computer, or cloud resource.
Processor:
- 1.5 GHz - minimum for evaluation or testing
- 2.0 GHz - minimum for production use
- x64 architecture (e.g., AMD64 or Intel 64)
At least two logical cores are required for in-memory storage.
RAM:
- 4 GB - minimum for evaluation or testing
- 8 GB - minimum for production use
- 16 GB - minimum for production use with in-memory analytics
Hard disk space:
- 10 GB free - minimum for evaluation or testing
- 50 GB free - minimum for production use
Operating systems:
The following 64-bit operating system versions are supported:
- Windows 10 or higher - evaluation or gateway use only
- Windows Server 2012 R2 or higher
- Ubuntu 22.04 LTS
- Ubuntu 24.04 LTS
- Ubuntu 26.04 LTS
- Debian 12
- Debian 13
You can also deploy on other distributions using Docker and/or Kubernetes.
There are certain known limitations when running on Linux, including Docker and Kubernetes.
.NET:
- .NET 10 - installed or download link opened automatically when needed
Web server:
The application is hosted on one of the following:
- For Windows: IIS 8.5 or higher - installed automatically as a prerequisite
- For Linux: a reverse proxy server such as NGINX - can be installed automatically
Application database server:
One of the following is used by the application to store its own data:
- Microsoft SQL Server 2017 or higher
- Microsoft SQL Server Express Editions - supported but not recommended for production use due to limitations; Microsoft SQL Server Express LocalDB is not supported
- Microsoft Azure SQL
- PostgreSQL version 9.6 or higher
This can be on the same server or separate from the web server (the database server must be configured to accept remote connections if separate).
4. Data sources
You can connect to the following types of data sources, each of which may have additional (driver) requirements for the server or gateway as indicated below. Kubernetes and Docker deployments rely on Linux support.
The ODBC and JDBC data sources listed below allow you to connect to various other data sources that have ODBC/JDBC drivers. The Generic Web data provider can connect to various online data sources.
| Data Source | Windows Support | Linux Support |
|---|---|---|
| Amazon Redshift | Drivers included | Drivers included |
| Azure Table / Azure Cosmos DB | Drivers included | Drivers included |
| Composer Including Simba Self-Service Analytics and Agentic Intelligence |
Drivers included | Drivers included |
| dBase (DBF) database files | Drivers included | Drivers included |
| Elasticsearch 8 or higher | Drivers included | Drivers included |
| Exasol | Drivers included | Drivers included |
| Flat file sources | Drivers included | Drivers included |
| Generic Web (additional web data sources) | Drivers included | Drivers included |
| Google Analytics / BigQuery / Sheets | Drivers included | Drivers included |
| IBM DB2 database |
Drivers included | Drivers included |
| JDBC (additional data sources) | Java SE Runtime Environment version 8 or above (x64) and the 64-bit JDBC driver for the specific data source | 64-bit JDBC driver for the specific data source |
| MemSQL | Drivers included | Drivers included |
| Microsoft Access |
Microsoft Access Database Engine 2010 prerequisite | ODBC/JDBC only |
| Microsoft Dataverse For Dynamics 365 Online |
Drivers included | Drivers included |
| Microsoft Excel | Drivers included (Microsoft Access Database Engine for legacy support) |
Drivers included |
| Microsoft SQL Server 2005 or higher Including SQL Server Express, Azure SQL, Azure Synapse |
Drivers included | Drivers included |
| Microsoft SQL Server Analysis Services 2005 or higher Including tabular instances, Azure Analysis Services |
Drivers included | Not supported on Linux |
| MongoDB 4 or higher | Drivers included | Drivers included |
| MySQL 5.0.45 or higher | Drivers included | Drivers included |
| OData (Open Data Protocol) | Drivers included | Drivers included |
| ODBC (additional data sources) | 64-bit ODBC driver for the specific data source | 64-bit ODBC driver for the specific data source |
| Oracle database | Drivers included | Drivers included |
| Oracle 11g Essbase | Drivers included | Drivers included |
| Pardot | Drivers included | Drivers included |
| PostgreSQL 13 or higher |
Drivers included | Drivers included |
| Salesforce.com |
Drivers included | Drivers included |
| SAP HANA |
Drivers included | Drivers included |
| SAP NetWeaver BW 7.0 or higher Uses XMLA web service |
Drivers included | Drivers included |
| SharePoint Lists and Excel Services |
Drivers included | Drivers included (online credentials only) |
| Snowflake | Drivers included | Drivers included |
| Teradata 12.0 or higher | .NET Data Provider for Teradata | Install the Teradata driver |
| Trino database | Drivers included | Drivers included |
| Vertica database |
Drivers included | ODBC/JDBC only |
| XML files | Drivers included | Drivers included |
Additional details about installing and using drivers for certain data sources are available in the How-To section of the documentation on connecting to data.
5. Installation
The following requirements apply when installing directly on your own servers.
5.1. For Windows
The deployment application checks if the following prerequisites are installed on the server and can automatically download and install any missing prerequisites (this requires an active internet connection).
If you need to install them manually, use the links below to access them. In the Prerequisites screen of the Deployment application, you can also click on the prerequisites and press F8 to download a list of URLs.
- IIS (on Windows Server, add the Web Server role)
- ASP.NET Core Runtime 10.0 - Windows - x64
- ASP.NET Core Runtime 10.0 - Windows - Hosting Bundle
- .NET Desktop Runtime 10.0
- (Optional) Microsoft Access Database Engine 2010 Redistributable x64 for Microsoft Access and certain Microsoft Excel legacy support such as for XLS files
- (Optional) Python 3.10 - 3.14 for the metric set Assistant and Python transforms. The Assistant also requires the following packages to be installed into the virtual environment, and they will be noted along with required version numbers as missing in the installation log files if they can't be downloaded:
- Python nltk module
- Python pandas module
- Python requests module
- Visual C++ 2015, 2017, 2019, and 2022 Redistributable - x64
5.2. For Linux
Certain requirements are installed automatically when running the deployment wizard (this requires an active internet connection). You can install the following ones manually using the provided links:
5.3. Additional requirements
During installation, you may be asked for the following (unless you choose an Express installation option):
- The user ID and password of an account that has db_create permissions on your SQL Server instance, or a usesuper account on PostgreSQL.
NoteAfter the installation, the SQL Server administrator will require only db_owner permissions. A PostgreSQL administrator will require the CanSelect, CanUpdate, CanInsert, and CanDelete table privileges, as well as the CanCreate database privilege.
- When using a PostgreSQL database for application and warehouse storage, a PostgreSQL instance with the uuid-ossp extension installed (you will be notified if it is missing). This is part of the postgresql-contrib package.
- For Windows installations, the user ID and password of an account to use for the IIS application pool.
- A web server port for accessing the application website (the installer may choose a default) or an existing website for installing as an IIS virtual directory (this can be the IIS 'Default Website').