Cinegy software provides different components such as servers and clients. Depending on which tasks have been delegated to each component, the system recommendations will vary.

This article provides an overview of the principal system components needed and their corresponding recommendations.

The diagram shows a possible Cinegy workflow network infrastructure:


The Cinegy workflow environment is made up of the following components:

  • Typical Microsoft Windows network. Servers and workstations participate either in active directory or in the legacy domain (the so-called "Windows NT domain").

    The legacy Windows NT domain must support WINS and/or DDNS.
  • Gigabit LAN connection is necessary to provide the performance needed for all the appointed servers. The only necessary network protocol is TCP/IP. Coupling that protocol with other network protocols (like NetBEUI or IPX/SPX) is not recommended.

  • Microsoft SQL Server installation. It is possible to use a single server installation, but it is recommended to use separate server machines for larger network installations.

  • File server with a domain controller, WINS/DDNS server or DHCP server. The file server must provide its resources over the SMB-TCP (SMB = Server Message Block; the so-called "Microsoft Network protocol").

SQL Server

The performance of the SQL Server database is determined by the processor performance. As the total number of users grows and/or the size of the database itself, the amount of installed RAM and the speed of the disk I/O system and how it is configured, become increasingly important.

Cinegy Archive requires one of the following SQL Server versions: SQL Server 2008 SP3, SQL Server 2008 R2 SP1, SQL Server 2012, SQL Server 2014.
SQL Server Express can be used only with the Advanced Services installed; the other SQL Server versions should have the full-text service installed.
With very large databases and many users it becomes crucial that none of these three – processor memory or disk I/O becomes a bottleneck or it will cause the entire system to slow down.
Study thoroughly all the Microsoft recommendations on the SQL Server installation and performance.
It is recommended to use a dedicated SQL Server for Cinegy software exclusively. Running other databases on the same server can affect the performance in an unpredictable way.
Cinegy clients need access to the SQL Server and databases, so it should be accessible via TCP/IP. Default port 1433 should be open in Windows Firewall.

SQL Server Hardware

SQL Server Performance

The following table gives an indication of what processing power is required in relation to the number of concurrent users on the Cinegy Archive SQL Server.

Processor RAM Number of users

Core 2 Duo E8400 4GB


Xeon X3430 8GB


Dual Xeon E5620 16GB

up to 250

Xeon E5-2670 32GB

up to 350

Test machines used SQL Server 2008 R2 SP1 on Windows Server 2008 R2

The number of users given in this table is estimated based on assumption that Cinegy Desktop client performs a range of tasks: search, browse, edit, logging, etc. If it is clear from the beginning that there will be a very large amount of searching with complex search queries, then the performance required will be much higher.

Cinegy Workspace users create less load on the database server than the average Cinegy Desktop user. Search queries from web users are serialized – queued – so in the worst case they have to wait. This is not the case with Cinegy Desktop search requests. Cinegy installations with more than 200 users have been deployed and are in use with even lower performance hardware than recommended in the table above. To be able to run the Cinegy system successfully and without performance issues, the rights and roles management of the Cinegy Archive database can be used to determine which user can do what. By limiting rights to powerful features available in the system, administrators can help limit possible performance bottlenecks.

The rights management issue is covered in the Cinegy Enterprise Manager Manual.
Disk I/O
It is always important to adhere to Microsoft’s best practices guidelines for SQL Server installations (available for free from Microsoft website).

This is not as important with small installations, but when building systems for more than 30 users, choosing the right disk layout can give a considerable boost of performance at very little extra cost. For example, using different disks for temp files, log files, the database itself and so forth will improve overall throughput by allowing the system to separate these tasks to dedicated disks. When building an I/O subsystem for a database one should also remember that the read/write performance is often secondary to the number of I/Os the subsystem can perform per second. The data that is written to a database in general does not exceed 8k per write, so formatting a volume with 64k block size for use with a database is counterproductive.


All larger, mission critical Cinegy Archive SQL Server database server installations will choose the option to use the standard Microsoft clustering feature of Windows Server Enterprise (this is not available using Windows Server Standard or Small Business Server).

A cluster typically consists of two machines that form one new virtual machine. One of the cluster machines will be active and the other will be passive standing by in case of an emergency. If the active machine were to fail, then the passive machine will take over and become the active one itself. The signaling of the state of the machines is done by a dedicated Ethernet "heartbeat" cable that connects the two machines.

This shared storage, the Quorum disk, which is usually a RAID5 system that has two SCSI or FibreChannel adapters allowing both machines to be connected at the same time. The important issue to remember when building a cluster is that all components need to be cluster capable. This is especially important for the storage adapters and for the storage subsystem itself. Every major server vendor can provide a list of clustering capable hardware they sell.

When clustering two systems, the amount of usable RAM is half of what the machine would have compared with running as a stand-alone machine. Therefore, to have a system with 16GB of usable RAM in a two machine cluster configuration 32GB of RAM is recommended in both cluster machines.

SQL Server Native Client

SQL Server Native Client is a data access library introduced in SQL Server 2005. Database mirroring is a primarily software solution to increase database availability and data redundancy. SQL Server Native Client provides implicit support for database mirroring. In addition to exposing features of Windows (formerly Microsoft) Data Access Components (WDAC), SQL Server Native Client also implements such features as database mirroring, multiple active result sets (MARS), query notifications, snapshot isolation, and XML data type support.

Refer to the Microsoft SQL Server documentation for more information about the new features supported by SQL Server Native Client.
For more information, please read the following article or visit the Microsoft SQL Server website.

Cinegy Archive Video Server

The Cinegy Archive video server has to support the streaming request of all users and accommodate for all the qualities in use. The most important recommendations are high performance network adapter and connection (1GB LAN or a fiber channel connection). A good quality RAID system should be installed to provide fast access to the data. The disk recommendations really depend on your own individual needs and you should calculate this generously considering the number of users and the streaming qualities you are planning to use.