Terms and Conditions for SQL Shared Database Services
Customers who purchase a Database on the SQL Shared Platform must agree to the following terms and conditions in addition to the WebCentral Standard Terms and Conditions which may be viewed at http://www.webcentral.com/terms/.
1.1 All new databases requested will be created on an SQL 2008 server (according to the product purchased). A job response in Mission Control will provide details of login credentials, database name and server name.
1.2 Existing SQL 2000 and 2005 databases will continue to be supported but no new requests will be accepted for SQL 2000. For policies relating to older versions of SQL, see from clause 4 below.
2.1 A Set-up Fee of AUD$49 will apply to all new SQL 50 to 750 MB databases (available to Economy and above hosting levels).
2.2 A Set-up Fee of AUD$99 will apply to all new 1GB to 3 GB SQL Server databases.
2.3 A monthly management fee will apply to all new SQL server databases.
|
Database Size |
Monthly |
Setup |
|---|---|---|
|
<50 MB |
$15 |
$49 |
|
51 - 250 MB |
$29 |
$49 |
|
251 - 750 MB |
$49 |
$49 |
|
751 - 1 GB |
$75 |
$99 |
|
1 GB - 2GB |
$99 |
$99 |
|
2 GB - 3GB |
$149 |
$99 |
3.1 SQL Service customers receive the following features:
3.2 Customers whose databases exceed the number of user connections will have their excess connections automatically terminated. WebCentral takes no responsibility for problems caused by the termination of excessive user connections, however notification will be provided via an automated job logged in Mission Control.
3.3 To comply with Microsoft Licensing Terms and conditions, the database may be used only to support public and Internet accessible
It may not be used to support line of business applications (e.g., Customer Relationship Management, Enterprise Resource Management and other similar applications).
3.4 SQL Replication is not supported by Webcentral on the Shared SQL 2008 platform, however the database can be used as a subscriber. Setup, configuration and monitoring of the database as a subscriber is the responsibility of the customer.
3.5 WebCentral will only supply a hosting environment, not a testing environment. Customers hosting SQL databases should run the database in a similar environment in their premises and test off line.
3.6 Full-text search support is provided for character-based data. The Full-Text Search facilities can be used to create special indexes of all pertinent words in selected columns of selected tables. Administration of full-text indexes can be managed either through SQL Server Management Studio or through a set of stored procedures.
3.7 The following features are not supported on the SQL 2008 Shared platform:
4.1 SQL Replication is not supported.
4.2 WebCentral will only supply a hosting environment, not a testing environment. Customers hosting SQL databases should run the database in a similar environment in their premises and test offline.
4.3 Customers with workloads that detrimentally impact other customers on the SQL server will have their databases moved to a tuning server environment. WebCentral will give prior notice of the move if practicable. The customer will have two weeks to tune their SQL workload on the tuning server failing which the service may be suspended or terminated. The customer's database will be moved back to the SQL environment only after the workload has been tuned to WebCentral's satisfaction.
4.4 Applying to SQL Lite, Standard SQL and Premier SQL only: Full-text search support is provided for character-based data on SQL servers. The Full-Text Search facilities can be used to create special indexes of all pertinent words in selected columns of selected tables. Administration of full-text indexes can be managed either through SQL Server Enterprise Manager (for SQL 2000 databases), SQL Server Management Studio (for SQL 2005 and SQL 2008 databases) or Full-Text system stored procedures. The space taken up by the Full-Text Search indexes is included in the space quota for your site.
5.1 The IDQ server environment permits a SQL workload limit of 60 SQL statements per second. Customers who exceed the SQL workload limit for their SQL instance will be advised to tune their application and reduce the SQL workload below the above specified limit. The requested tuning must be actioned within two working days of being advised by WebCentral. 5.2 Customers with SQL workloads that detrimentally impact other customers on the IDQ server will have their databases moved to a SQL tuning server environment. WebCentral will give prior notice of the move if practicable. The customer will then be given two weeks to tune their SQL workload on the SQL tuning server failing which the service may be suspended or terminated. Once the offending SQL workload has been tuned to WebCentral’s satisfaction the databases will be moved back to the IDQ environment.
5.2 WebCentral will only supply a hosting environment, not a testing environment. Customers hosting SQL databases should run the database in a similar environment in their premises and test off line.
5.3 Full-text search support is provided for character-based data on IDQ servers. The full-text search facilities can be used to create special indexes of all pertinent words in selected columns of selected tables. Administration of full-text indexes can be managed either through SQL Server Enterprise Manager (for SQL 2000 databases), SQL Server Management Studio (for SQL 2005 databases), or Full-Text system stored procedures. The space taken up by the full-text search indexes is included in the space quota for your site.
6.1 Two (2) database users are provided with each database for application and administrative use. An additional 8 (to bring the number of users to a maximum of 10) per database will be permitted.
6.2 A web-based interface for the MySQL databases will be provided, at no extra charge and maintained by the technical departments, as a means of managing the database.
6.3 Connections from external networks and use of client software packages other than those provided by the hosting platform are not supported for security and interoperability reasons.
6.4 InnoDB/Berkeley DB table types are not supported.