If the operating system or filesystem places a limit on the number of files in a directory, MySQL is bound by that constraint. The efficiency of the operating system in handling large numbers of files in a directory can place a practical limit on the number of tables in a database. If the time required to open a file in the directory increases significantly as the number of files increases, database performance can be adversely affected. MySQL 3.22 had a 4GB (4 gigabyte) limit on table size.

There is no cap on the maximum size allowed as long as they are below the available diskspace quota in your Hosting Plan.

Of course, these are not actually unlimited, but limited to available disk space and memory/swap space. Performance may suffer when these values get unusually large. The maximum table size of 32 TB does not require large file support from the operating system. Large tables are stored as multiple 1 GB files so file system size limits are not important. The maximum table size, row size, and maximum number of columns can be quadrupled by increasing the default block size to 32k.

BIG! - CrimeStar's database actually consists of many different data tables. The database tables used with the Professional Edition can grow to a maximum of 2 Gigabytes each, the maximum size of the database can potentially be many (hundreds of) gigabytes of data. Because of this large capacity, CrimeStar is capable of handling the volume of data created by most law enforcement agencies.

MSSQL databases are allowed a maximum database size of 300MB and will be counted as part of the diskspace quota in your Hosting Plan.

MarketWide easily accesses multiple databases and servers without database size limitations. Current DSI client installations range from small (200,000 records) to huge (over 1 billion records). Database platforms we work with range from Pentium/Windows NT machines to half-million dollar multiprocessor Unix systems. DSI guarantees that MarketWide will operate correctly with any major relational database engine, as long as the database is ODBC compliant.

We do not give out shell accounts by default for security and resource usage reasons. Additionally (and for similar reasons) we like to personally set up MySQL databases only for customers who request them. If you'd like to put in a request, contact customer support for more information. Additionally, remember that only Domain and Super accounts can use CGI, MySQL, PHP, etc.

MySQL is an open source database server that employs Structured Query Language (SQL). A database server is a program that can store large amounts of information in an organized format that's easily accessible through scripting languages like PHP.

We can receive files of up to 200MB on our servers. However, this has never actually happened as most large Access databases when zipped with WinZip do not exceed about 150MB (even those which are 900MB+). However, if your database when zipped is larger than 200MB we may still be able to receive it. On completion, the file will be sent back to you either via courier, FTP, email or on-site depending on your wishes.

We are now allowing MySQL databases again. To create yourself a database, run the "mysqlme" located in "/usr/local/bin/". The program will create a MySQL user entry for your userid and then create a database for you with the name of your userid. You can have more than one database by specifying a database name with the "-db dbname" option. A database will then be created called "userid_dbname".

By default the module will list all of the databases on your system on the main page, even if some are not actually usable by the logged-in user. To change this, follow these steps : In the Database access control list field, remove the existing *: * line and enter one line per user, containing the username, a colon and list of databases he is allowed to use.

This is dependent on the page size being used, but the absolute maximum row width in an Ingres table is 32K. The maximum row width can be configured in CBF, the default is 2008 (which is the maximum for a 2K page). Refer to Chapter 6 in the Database Administrators Guide for details of the Page Header size which you must allow for when calculating the maximum row width for your chosen page size for page sizes less than 64Kb.