Limitations
Maximum database size
Built-in database option (default setup):
The maximum database file size can be approximately 2 gigabytes. Note that, SpeedBase does NOT save binary data (file attachments) to your database.
That means, all data saved to the database is plain text data only. This makes approaching the database size limit quite unlikely for vast majority of small business applications.
SQL Server database option:
If you plan to use Microsoft SQL Server as the backend database for Speedbase, the limitation is determined by the edition of the SQL Server product.
For more information, consult the documentation of the SQL Server product you plan to use.
Maximum number of users
Built-in database option (default setup):
There is no limit to the number of login accounts you can create for your SpeedBase database. However, the number of users who can CONCURRENTLY connect to and ACTIVELY
work on your database is limited due to performance and reliability considerations. While this number can vary widely depending on factors such as database design,
the type of changes being made by users, and hardware performance, performance degradation or other issues are generally not expected with approximately 20-30 concurrent and active users.
- Concurrently connected users are those who have started the SpeedBase application and keep it running. By default, SpeedBase starts automatically with Windows, so each computer
that is powered on and has a user logged in represents a concurrently connected user.
- Actively working users are those who are actively searching for, opening, modifying records, or performing any configuration tasks in your database using keyboard and mouse.
In other words, you may have hundreds of user accounts, provided that only a limited number of users need to connect and work on your database simultaneously.
If you encounter any issues related to an increased number of concurrent users later on, you may consider switching to SQL server as the backend database for improved performance and scalability.
It's perfectly fine to start with the default setup and migrate to SQL Server at any time later, as SpeedBase can easily handle data migration to SQL Server.
SQL Server database option:
If you plan to use Microsoft SQL Server as the backend database for Speedbase, the limitations will depend on the edition of SQL Server you choose.
For more information, refer to the documentation for the specific SQL Server edition you plan to use
Maximum number of records
The maximum number of records you may create is not restricted by SpeedBase.
It is not possible to tell or estimate a maximum because the performance can be affected by various factors such as, database design, system performance,
the number of relationships together with the number of records on related catalogs and local network speed in case of multiuser applications.
For improved performance and stability reasons, customers who plan to grow their database to maintain records approaching a million or more,
or observing a bottleneck because of the local network speed limit are recommended to switch to the SQL server (as backend) option of SpeedBase.
Note that, SpeedBase is capable of migrating your data from the default, built-in database to SQL Server, that means, you may just start with the default setup and
consider migration at a later time and only if the performance degrades, which is highly unlikely to happen for most small business applications.
Maximum number of fields per catalog
You may create any number of catalogs and between 186 to 248 "standard" fields on each catalog.
The actual limit for data fields you may create depends on your selection of data types.
Certain data types which we refer here as "relational fields" here allocate 2 fields from the limit each.
When you create one of the following field types, the remaining number of fields you may create decreases by 2 instead of 1.
- Relational lookup fields,
- Computed fields which display data from parent record,
- File fields.
Tip: You may check the number of currently allocated/remaining fields from the field list window.
Right click the desired catalog, select "Fields". The information is displayed at the bottom of the field list window.
Most applications require relatively fewer number of relational fields and the maximum number of fields you may create is well above 200.
If your application requires significant number of relational fields, you may calculate the actual maximum fields you may create
as shown in this example:
Example
3 text fields would spend 3
5 expression type computed fields would spend 5
3 relational type computed fields showing parent data would spend (double each) 6
2 file/image fields would spend (double each) 4
Number of field resource consumed: 18
The remaining number of fields you may create: 248 - 18 = 230
Maximum number of relational fields per catalog
The limitation described in this section applies to the built-in database of SpeedBase only.
If you are using SQL server or other database types, the limitation depends on the database type and system resources.
The following fields are considered as relational fields:
- Relational lookup fields: A relational lookup field which shows data from parent record. Only the catalog showing
the lookup field is affected.
- Computed fields which retrieve and display data from parent record.
These are the computed fields for which the task was set as "Copy data from parent record".
- File fields.
The maximum number of relational fields allowed per catalog is 30.
Beware that computed fields which retrieve data through multiple related catalogs may further decrease this limit.
Tip: If you plan to create a high number of fields with "file" data type, consider creating a separate catalog which will hold
the files and file related information only. You may then create a relationship between the file catalog and main catalog which will make
it possible to display/attach an unlimited number of files related to each record from the main catalog.
Tip: You may check the number of currently allocated/remaining relational fields from the field list window.
Right click the desired catalog, select "Fields". The information is displayed at the bottom of the field list window.
Text Fields
The maximum length of text in a small text field allowed is 255 characters.
The maximum length of text in a long text field allowed is 262,144 characters.
Numeric Fields
The minimum integer number allowed is approximately -2 billion.
The maximum integer number allowed is approximately +2 billion.
The maximum/minimum decimal number allowed is up to 16 digits for the integer part and up to 8 digits for the decimal part.
File Fields
For local database setup: SpeedBase does not apply any limit for the number of files or total size of all files because files attachments
are not saved to the database. Those limits are set by your operating system and available disk space.
For remote database setup: If you choose to save your files in your SQL Server database, the maximum total size of files you may
save is determined by the limits of the chosen backend database. Consult your SQL Server product documentation for more information.
Date & Time Fields
The minimum date allowed is 1/1/1000
The maximum date allowed is 31/12/9999