An open source relational database with an active community and boasting several third-party tools, applications and libraries to extend its functionality.
gridSQL currently supports MySQL version 5.7.
In order to fulfill your requirements for your MySQL workloads, we offer four performance classes - Standard (max. 4GB RAM), High (max. 16GB RAM), Insane (max. 32GB RAM) and Ultra (max. 64GB RAM).
CPU Limits & Autoscaling
Our autoscaling Platform Services will scale according to the load of your application. The minimum CPU usage is 1, and the maximum is 32. The maximum CPU cores available can be set anywhere in between, and the database will scale up to the maximum cores you set, if nothing is set then the 32 core limit will be used. The amount of cores in use can be easily seen in the metrics of the running Platform Service.
Storage Limits & Autoscaling
Our autoscaling Platform Services will scale according to the load of your application. The maximum possible storage is 1024GB. The current usage can been seen within the platform services metrics, and previous accumulated usage can bee seen within the Usage Dashboard.
Security Zones connect your managed database service to your infrastructure, and the network configuration is completely automated. For increased security they are private networks located in a separate zone and are not connected to the public Internet, allowing your service to run encapsulated. You can either use the default Security Zone or create and name your own Zone. You also have the option to enable your servers to access the database service by connecting them to your specified Security Zone.
In order to prevent overloading, you can limit the maximum number of simultaneous connections to your database service. The maximum number of connections can be specified anywhere between 10 to 4000, with 4000 being the default set value.
The MySQL server can operate in different SQL modes, and can apply these modes differently for different clients, depending on the value of the sql_mode system variable. DBAs can set the global SQL mode to match site server operating requirements, and each application can set its session SQL mode to its own requirements.
Here is a list of possible values:
Activating replication enabled you to configure the binary logging format. This allows to set a replica server to do other activities on, for example backups. The binary logging format can either be:
You can also specify a Server ID.
Maximum Allowed Packet Size
This refers to the maximum packet length sent or received from the database server, dependent on the max_allowed_packet variable. The range varies from 1MB all the way up to 1GB, with the default maximum allowed packet size set as 16MB.
Server Time Zone
You have the possibility to specify the time zone in which your database service operates in, with the default time zone set as Coordinated Universal Time (UTC).
Using query cache parameters, you can significantly improve query performance by caching query results. Should you choose to enable it, there are two subparameters associated with query caching, namely:
- Query Cache Limit : Used to set the maximum size for each set of query results, preventing a single large query result set taking up most of the available memory. The default value is specified as 1MB.
- Query Cache Size : Used to set the overall size of the query cache, with the default value specified as 32MB.
Once your PaaS service has been successfully created you can have the possibility to view the Service Access section within the detailed view for your service. You have the option to include the credentials, password and/or the port. Using this section you can easily set, generate and copy several variants:
- Connection String
- Connection Parameters
- PHP Data Object (PDO)
- Data Source Name (DSN)
Keep in mind that you can only connect to your service from servers within the same Security Zone.