SQL Server is licensed separately by Microsoft from Windows Server. Any licensing queries should be directed to the Microsoft Licensing website or your Microsoft Licensing Reseller.
MS SQL Editions capable of running CallScripter are:
Express – not recommended but supported with caveats on usage and data storage. Please contact us to discuss your requirements
Workgroup/Web – not recommended, but is supported. Some advanced functionality may not work fully or be fully integrated in to the product. Is not part of active testing.
Standard and above (Enterprise, Professional) - recommended. Standard and above provide the required features for all CS features and functionality. Actively tested.
MS SQL Versions capable of running CallScripter are:
SQL 2000 and before - not supported or compatible.
SQL 2005 - supported but not recommended. Some new functionality is not supported with this version.
SQL 2008 (2008, 2008R2) - supported but not recommended due to improvements in later SQL editions.
SQL 2012 - supported and recommended.
SQL 2014 - supported and recommended.
SQL 2016 - not supported or compatible
SQL Configuration
SQL should be installed on the server selected for the Database Server role, which could be the same machine as the Application Server, or a separate box depending on the scale of your installation.
A standard install of SQL is all we require. Often SQL authentication should be enabled, but this is down to your configuration. The SQL server should be reachable from the Application server in terms of network connectivity. If you have an edition with SSRS this should be installed as default on to the CallScripter SQL Server/Instance.
We support the SQL Collations"Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" to ensure certain SQL dependant features are run in a user search friendly manner and all characters are handled in the required manner. This is required for the CallScripter Database, SQL instance and SQL System Tables.
You may wish during install to consider the placement of data and transaction logs according to SQL Server Best Practice. Information on that topic is available from Microsoft.
Access to the SQL instance through SSMS will be required by the installation and on-going support team. As is the SSRS configuration interface if this feature is being used.
SQL Maintenance
The CallScripter SQL database will require standard SQL maintenance tasks to be carried out upon it. These primarily include maintaining the SQL indexes.
This can be done via 3rd party tools, MS SQL Maintenance Plans or we can provide a sample script that intelligently maintains the indexes that require it.
Please note that the CallScripter database is not compatible with online reindexing.
