Database Server Specifications

The following table describes specifications and other important information about the database servers

Server Specifications

Item

Description

Database Server

We recommend a separate server for the database to eliminate resource contention between the Code Insight application and database.

Character Set

Select UTF-8 as the character set when installing your MySQL database server.

This is a critical step. To ensure that application data is stored properly in the database, UTF8 must be selected as the default character set when installing MySQL.

Linux Installation:

Ensure that you have a my.cnf file in your /etc/mysql directory

If you do not have a my.cnf in your /etc/mysql directory, locate one of these files in the /usr/share/mysql directory and copy it to /etc/mysql. Rename the file my.cnf.

• mysql-large.cnf (MySQL prior to 5.5)
• my-large.cnf (MySQL 5.5 to 5.6)
• my-default.cnf (MySQL 5.6+)

Navigate to the /etc/mysql/my.cnf file, and edit the file as follows:

[client]

#password= [your_password]

port= 3306

socket= /var/lib/mysql/mysql.sock

default-character-set = utf8

[mysqld]

default-character-set = utf8

default-collation = utf8_general_ci

character-set-client = utf8

character-set-server = utf8

skip-character-set-client-handshake

Windows Installation:

Navigate to my.ini or my-default.ini file located in your MySQL Server installation directory (for example, C:\Program Files\MySQL\MySQL Server 5.6), and edit the following lines:

[mysqld]

default-character-set=utf8

Storage Engine

Select InnoDB as the default storage engine if you are using MySQL.

Linux:

Edit the my.cnf file in the [mysqld] section.

default-storage-engine = INNODB

Windows:

Add the following line to the my.ini file:

default-storage-engine=innodb

Alternatively, you may use the InnoDB plug-in. For more information, see http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-plugin-installation.html

Buffer Pools

To support Code Insight electronic updates, you may need to change the memory configuration for your database instance.

MySQL

Specify a combination of innodb_buffer_pool_instances and innodb_buffer_pool_size so that each buffer pool instance is at least 1 GB.

Oracle uses auto memory management. See Memory Configuration and Use.

SQL Server uses auto memory management. See Memory Management Architecture.

Sizing

Have a DBA configure your database as you would for any other enterprise web application.

Start with a base of 30 GB to accommodate the Code Insight Data libraries and other data such as users, groups, and projects disk space for the database. We recommend that you start with a base of 30 GB.

Scale up by 2 MB for every 5,000 files scanned.

Begin by estimating much you will scan in the first 6 months and add that to the 30 GB base size.

As for data volume, Code Insight does not move large amounts of data and does not have extremely high concurrent transaction rates.

Set innodb_buffer_pool_size = 1G.

Backup

This is a DBA activity per the customer's data policies.

Perform a database dump or export of the entire central database schema regularly.

Back up the workspaces directory at the same time you back up the database so they remain in sync.

For additional information on backup and recovery, see Performing Backup and Recovery.