Database Requirements
The following page and subsequent installation guide section is for TeamConnect 6.2. For earlier versions, download the PDF from the TeamConnect PDF Hub. Note: This link may require a login.
The database server should be installed and configured on a hardware platform and operating system certified by your database server vendor. TeamConnect requires at least 500 MB for its tablespace, and requires a larger tablespace when your data is added or you add custom elements to your design.
Supported Databases
| TeamConnect Version | Supported Versions | Certified On |
|---|---|---|
| TeamConnect 6.2 (Note: we dropped support for SQL Server 2016 starting with 6.2.1) |
Oracle 19c (starting in 6.2.4) | 19.3 |
| Oracle 12c R2 | 12.2.0.1.0 | |
| SQL Server 2017 (TCE 6.2+) | 14.0.1000.169 | |
| SQL Server 2016 (only for TCE 6.2) | 13.0.4224.16 |
Oracle Requirements
For Oracle, the login that you provide for TeamConnect's use must have the following database privileges:
- CONNECT and CTXAPP roles
- CREATE TABLE system privilege
- CREATE VIEW system privilege
- CREATE PROCEDURE system privilege
- CREATE SEQUENCE system privilege
- CREATE TRIGGER system privilege
- CREATE MATERIALIZED VIEW system privilege
- User quota "Unlimited", value -1, unit MBytes
For future expansion, enable auto extend for the data file.
For Data Warehouse you need additional rights, which are listed in the Data Warehouse Release Notes.
SQL Server Requirements
For SQL Server, the login that you provide for TeamConnect's use must have the following roles:
- public role
- db_owner role
Your SQL Server DBA must also alter the database configuration as follows:
- ALTER DATABASE <dbname> SET ALLOW_SNAPSHOT_ISOLATION ON
- ALTER DATABASE <dbname> SET READ_COMMITTED_SNAPSHOT ON
For future expansion, ensure that "Enable Autogrowth" is selected for the database.
Localization
If you plan to localize TeamConnect for multiple languages, your Oracle database configuration should include:
- NLS_NCHAR_CHARACTERSET parameter set to AL16UTF16. (This is the default.)
- All text columns set to NVARCHAR2 datatype. This is done automatically for newly created databases; if you are upgrading from an older version, you may need to perform manual tasks to make your database compatible. See Upgrade Considerations for more information.
Estimating Your Actual Database Size
Each customer's design is unique; thus the number of custom fields, field types, documents stored and the numbers of rows of data for each object type will be unique as well. You must also take into account the amount of data and documents that will be migrated from legacy applications into TeamConnect via your initial data conversions. Finally, the number of users and the volume of new records they will be entering yearly is important. Using this information, and any historic information you have regarding year to year data growth from the legacy systems and expected increases in user community etc., is important to be able to estimate the initial database size and yearly database growth.
For these reasons, estimating the size of the TeamConnect database is not a simple task. We recommend that you conduct a database sizing exercise as part of the initial TeamConnect implementation plan. This will ensure that you are able to provision the correct amount of initial database space and accommodate the yearly growth. Current TeamConnect customers have database sizes varying from less than 5 gigabytes of data to over a terabyte.
Database Search Considerations
TeamConnect features full-text search capabilities (outside of Elasticsearch's Global Search), but those capabilities are constrained by the search capabilities of your database server software. If you store a document with a specific file type that your database server does not support for its full-text search feature, the content of that document is skipped during the TeamConnect full-text search.
Please review the documentation supplied with your database server's version to determine which file types are supported.