FlyingBinary Ltd

EXASol Data Warehousing

Massively parallel processing and optimised vector operations, true column store architecture, a Database as a Service DbaaS in the FlyingBinary big data suite, simplifying data integration, management, analysis and visualisation. The EXASol engine delivers blazing query performance and scales simply and linearly. Automated tuning significantly reduces cost of ownership.

Features

  • Massively parallel processing, MPP, using vector operations
  • In memory architecture with optimised caching
  • True column store with maximised compression
  • Scales from gigabytes to petabytes in one architecture
  • Automatic load distribution across infrastructure
  • Highest performance of any database vendor, scales 100Gb to 100Tb
  • Built to power performant scalable Analytics Services
  • Meets both Database as a Service or Data Warehousing requirements
  • Complements Tableau Private Visualisation service

Benefits

  • Optimised engineering delivers very rapid analytics
  • Automated tuning reduces costs and admin resource requirements
  • Simple peer node architecture provides linear scalability
  • Massive scalability removes need to change products as you grow
  • Automated loading supports large user numbers / query workloads
  • Automated database management reduces operational costs
  • Optmised column storage increases user query flexibility
  • Linear scale supports large scale deployment across enterprise
  • On average 66% cheaper than transactional databases

Pricing

£74000.00 per instance per year

Service documents

G-Cloud 9

368374857092534

FlyingBinary Ltd

Dr Jacqui Taylor

+44 77 899 668 02

jacqui.taylor@flyingbinary.com

Service scope

Service scope
Service constraints Exasol is designed as an analytical (OLAP) database, and as such it is not optimised for high volume transactional (OLTP) operations.
System requirements Requires a dedicated network port to connect to the database

User support

User support
Email or online ticketing support Email or online ticketing
Support response times We respond to all questions within 8 business hours. Normal business hours are 0800-1800 Mon-Fri excluding UK holidays. We regularly respond to questions within 4 business hours, and we triage all inbound questions to establish urgency and set appropriate priorities.
User can manage status and priority of support tickets No
Phone support Yes
Phone support availability 9 to 5 (UK time), Monday to Friday
Web chat support No
Onsite support Yes, at extra cost
Support levels Our standard support service is by email 0800-1800 Mon-Fri excluding UK holidays and we respond to all questions within 8 business hours. We regularly respond to questions within 4 business hours, and we triage all inbound questions to establish urgency and set appropriate priorities. We can offer several extensions to the standard service at extra cost: extended hours support at 10x7 or 24x7; 4 business hour response; phone support; web chat support; onsite support. The support service is provided for issues, incidents and service requests. We will also respond to questions about how to use the service, but we reserve the right to direct clients to our training services if users are clearly not equipped to use the service competently.
Support available to third parties No

Onboarding and offboarding

Onboarding and offboarding
Getting started There are four types of onboarding help available, which may be used in combination: online help; key contact getting started assistance; additional onboarding assistance; service training courses. Key contact getting started assistance is included within the cost of the service. It is usually conducted as an interactive web screenshare session, but may also be provided as a pre-recorded video session with a follow up teleconference, or as an onsite session. Onsite sessions outside the M25 area will incur an additional cost. Online help is available to all client users of the service and is included within the cost. Additional onboarding assistance and service training courses are both provided via the companion Cloud Support service.
Service documentation Yes
Documentation formats
  • HTML
  • PDF
  • Other
Other documentation formats Online videos and self-paced training courses
End-of-contract data extraction Users can extract data either by using an appropriate SQL SELECT statement, or for larger volumes the EXPORT command. Both of these methods can deliver data in CSV or Fixed-Block format with user definable delimiters. These tools are available at any time, not just at contract end, and may be used for any data extraction purpose required. There are no restrictions: all user data may be extracted from the service for any reason, at any time. User data extraction does not require supplier intervention, but clients may choose to limit this functionality to client super users or administrators. There is no limit to the number or size of data extractions performed, but the service is priced on a "fair use" basis for network charges. Excessively large or very frequent data extractions may incur an additional cost or bandwidth limits. Alternatively, the companion Cloud Support service offers assistance with data extraction, at an additional cost.
End-of-contract process Prior to the end of contract/contract renewal date, we discuss the forward plan with the client key contact. In the event of contract end, we work with the key contact to ensure that all user data and collateral is retrieved or extracted before the contract end date. Although there are standard data extraction tools built in to the service, there may be a requirement for special data migration to the client's chosen new service. In that instance, we can work with the new supplier to migrate data to maximum benefit for the client, such work would be performed within the companion Cloud Support service and incur an additional charge. In the event that the client is unable to extract all required data before the contract end date, it is often possible to extend the duration of the data extraction features of the service for an additional period; or to extend the full service for an additional period; so that the client does not suffer unnecessary unavailability.

Using the service

Using the service
Web browser interface Yes
Using the web interface The web interface is for installation, management, configuration and monitoring of the Exasol system. There is no web interface for running SQL queries. Users of this interface can define the hardware and software configuration of the Exasol database cluster, configure the database resource utilisation of the database software, and schedule and manage backup and restore operations. This interface also allows access to system log files, is the method for installation and upgrade of the Exasol software and enables users to extract and upload diagnostic data to the Exasol support portal.
Web interface accessibility standard None or don’t know
How the web interface is accessible The web interface is strictly limited to database installation and admin management. The vast majority of database access, including performance monitoring and audit, is performed via third party tools with their own user interfaces. While we have not had a particular focus on development of accessibility features for the admin web interface, we are very responsive to our user community and are keen to support the priorities they identify.
Web interface accessibility testing No specific accessibility testing performed to date.
API Yes
What users can and can't do using the API Users can connect to the database via ODBC, JDBC, .Net or JSON connection, or through a direct programming API for languages such as C++, R and Python. Once connected, the full range of SQL operations including queries, access control, data definition and monitoring are available provided the user has the appropriate level of privilege. Database monitoring functions such as query logs, user access logs, resource utilisation of queries, and database table sizes are available via SQL (to users with the appropriate privileges) as this data is stored within SQL tables in the system schema. Configuration of the Exasol system hardware and software is not available via the API - this is achieved from the web interface. The Exasol system is designed to be largely self-managing and self-tuning, and this means that there are fewer configuration parameters for the user to set, and also that typically much less management and operation resource is required.
API automation tools
  • Ansible
  • Chef
  • OpenStack
  • SaltStack
  • Terraform
  • Puppet
  • Other
Other API automation tools Exasol provides an open XML/RPC interface to enable automation
API documentation Yes
API documentation formats
  • HTML
  • PDF
  • Other
Command line interface Yes
Command line interface compatibility
  • Linux or Unix
  • Windows
  • MacOS
Using the command line interface The full range of SQL operations including queries, access control, data definition and monitoring are available provided the user has the appropriate level of privilege. Database monitoring functions such as query logs, user access logs, resource utilisation of queries, and database table sizes are available via SQL (to users with the appropriate privileges) as this data is stored within SQL tables in the system schema. Configuration of the Exasol system hardware and software is not available via the API - this is achieved from the web interface. The Exasol system is designed to be largely self-managing and self-tuning, and this means that there are fewer configuration parameters for the user to set, and also that typically much less management and operation resource is required.

Scaling

Scaling
Scaling available Yes
Scaling type
  • Automatic
  • Manual
Independence of resources Our testing tells us the lower and upper levels of cloud resource required to maintain performance for normal levels of demand. We reserve and dedicate the lower level of cloud resources to each client, so that no client user can impact the performance of any other client. As client demand increases, we monitor performance and ensure that additional cloud resources are available to maintain performance, to the upper level. The service is priced on a "fair use" basis, so exceeding the upper level of demand means either reduced performance, or request further cloud resources, at additional cost.
Usage notifications Yes
Usage reporting API

Analytics

Analytics
Infrastructure or application metrics Yes
Metrics types
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
  • Network
  • Number of active instances
  • Other
Other metrics Each SQL statement is logged with internal resource utilisation statistics
Reporting types
  • API access
  • Regular reports
  • Reports on request

Resellers

Resellers
Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Conforms to BS7858:2012
Government security clearance Up to Developed Vetting (DV)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations Yes
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency At least once a year
Penetration testing approach Another external penetration testing organisation
Protecting data at rest Physical access control, complying with SSAE-16 / ISAE 3402
Data sanitisation process Yes
Data sanitisation type Explicit overwriting of storage before reallocation
Equipment disposal approach Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Backup and recovery

Backup and recovery
Backup and recovery Yes
What’s backed up
  • All database data and configuration
  • Operating system content and configuration and application programs
Backup controls All operating system, application and database data are backed up automatically on a regular schedule. There is usually no need for user intervention or decisions to be made. If there are specific needs, for example to match with business use cycles, then these requests can be passed to the support team for implementation.
Datacentre setup
  • Multiple datacentres with disaster recovery
  • Multiple datacentres
  • Single datacentre with multiple copies
  • Single datacentre
Scheduling backups Supplier controls the whole backup schedule
Backup recovery Users contact the support team

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks TLS (version 1.2 or above)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)
  • Other
Other protection within supplier network Within the Exasol cluster, data is encrypted at rest and in transit. inter-node traffic within the system is carried by a separate internal private network which is not accessible to user accounts and is encrypted using AES128 or AES256.

Availability and resilience

Availability and resilience
Guaranteed availability We guarantee the service will be available 99% of the time during business hours. Measured over the last two years, we have comfortably exceeded 99.5% availability. For use cases requiring higher availablity guarantees, we can discuss alternate cloud deployments and architectures, at additional cost. No financial recompense is offered for a single failure to meet service level within a year. In the event there are two or more failures in successive months, then a discount equal to one twelfth of the annual cost will be offered for renewals at the next anniversary.
Approach to resilience All cloud resources are virtualised, so there is no dependency on any single hardware component. The underlying infrastructure is 99.999% available. All service components are replicated at a second site. This provides geographic (availability zone) resilience, in addition to providing an alternate source of service provision in the case of some outage that affects multiple hardware components, or a whole data centre or geographic location. All client deployments are managed as separate cloud instances, ensuring that performance-affecting activity occurring in one client deployment cannot impact any others. In addition to the dual site service, there is also the option of a cheaper, single site option. This still has all the benefits of the resilient cloud infrastructure, but lacks the additional geographic resilience provided by second site operation.
Outage reporting Service affecting incidents are reported to client key contacts by email. Service affecting incidents include any observation of diminished service performance, reduced or missing functionality and not just observation of service outage. Initial emails may include only a report of the observation. Follow up emails will include notification of full service restoration, or estimated time to restoration, or additional details of mitigations or workarounds. Client key contacts may also request further details or additional help, as the emails are issued by a client support team, capable of responding to requests for additional information; the emails are not issued by "no-reply" mailboxes.

Identity and authentication

Identity and authentication
User authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password
  • Other
Other user authentication Exasol also supports authorisation using industry-standard LDAP connections in addition to the specific methods listed.
Access restrictions in management interfaces and support channels The management interface uses separate network connections and a separate set of usernames, passwords and privilege levels. Access is secured via TLS V1.2 with usernames and strong passwords. Normal user accounts access the database using the standard network interface and do not use the management interface connections.
Access restriction testing frequency At least once a year
Management access authentication
  • Public key authentication (including by TLS client certificate)
  • Username or password
Devices users manage the service through
  • Dedicated device on a segregated network (providers own provision)
  • Dedicated device over multiple services or networks
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)
  • Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

Audit information for users

Audit information for users
Access to user activity audit information Users have access to real-time audit information
How long user audit data is stored for User-defined
Access to supplier activity audit information Users have access to real-time audit information
How long supplier audit data is stored for User-defined
How long system logs are stored for User-defined

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification No
ISO 28000:2007 certification No
CSA STAR certification No
PCI certification No
Other security accreditations No

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance accreditation No
Security governance approach Our security governance is meshed with our corporate governance, with our CEO having final responsibility for G-Cloud services and governance policies and our CTO having day-to-day responsibility for policy implementation. Our policies cover people, processes, technology and information assets, at board, management and operational levels. We review our policies and update our practices in light of new regulation, standards and best practice to ensure we are able to counter current and emerging threats.
Information security policies and processes Our information security policy follows guidance in ISO27001, is owned by our CEO and implemented by our CTO. The top level Information Security Policy is supported by Architecture, Operations and Client Access policies. The policy states security objectives and establishes principles to ensure current and continued adherance and continual improvement. The policy set is integral to staff induction and all staff are required to agree and accept that information security governance is a core working principle. Operational checklists enforce security practices at the day to day level, and activities cannot be signed off without verified completion. The checklists also contain sections for feedback and challenge so that we actively improve. All staff are expected to challenge, because if we don't, bad actors will. Standard reporting flows from operational analyst or team lead to manager to CTO, but any staff member can invoke exceptional reporting directly to management or board, to ensure that important issues receive appropriate attention. Internal reviews ensure that all information security processes are working smoothly and as designed. If exceptions are found, we perform root cause analysis to understand if/how we need to change working practice to support our information security objectives.

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Service hardware components are managed by our data centre suppliers. Component lifecycle management is accredited to ISO27001, including storage overwrite and secure destruction. Service software is assembled from existing software components (proprietary and open source), is obtained only from the official repository, and security checked before use. No custom software is used. The service deployment checklist records all versions and change dates. Planned infrastructure or software changes are reviewed for new or changed features or capabilities, and internal software library dependencies. If needed, configurations are changed to disable unnecessary new features or mitigate any additional security exposure.
Vulnerability management type Supplier-defined controls
Vulnerability management approach We monitor vulnerability feeds, vendor and security researcher blogs to understand emerging threats. We then make an assessment to confirm any potential to affect service, and if so, determine severity and likelihood. Based on our assessments, we create a mitigation plan that may include a change to operation practice, a planned upgrade or an emergency upgrade. Operational changes and emergency upgrades are carried out as soon as reasonably practical following assessment and planning. Planned upgrades are accommodated within the normal upgrade or patching cycle.
Protective monitoring type Supplier-defined controls
Protective monitoring approach System event monitoring is used to facilitate the identification, classification and analysis of potential security incidents. Any security-related incident is classified as a severely service affecting incident, is escalated accordingly and actioned immediately. Different techniques and processes are employed to mitigate and recover service integrity, depending on the nature of the incursion. Further details are available on request.
Incident management type Supplier-defined controls
Incident management approach All service incidents follow a standard process. A triage step classifies to: common event not service affecting; service affecting; severely service affecting. Common events are handled by following a routine process. Events affecting service severely are immediately escalated to acquire necessary resource and management support. All other incidents are handled by the respective support team. Clients can report incidents by email to the support team. Update reports and communications are issued for all client-reported and service affecting incidents. When service affecting incidents are resolved, root cause analysis is performed to determine mitigating actions.

Secure development

Secure development
Approach to secure software development best practice Supplier-defined process

Separation between users

Separation between users
Virtualisation technology used to keep applications and users sharing the same infrastructure apart Yes
Who implements virtualisation Supplier
Virtualisation technologies used VMware
How shared infrastructure is kept separate While cloud resources are fully virtualised for flexibility and scale, our security is hardware based and implemented at the network layer directly on Cisco switches, allowing both high security and high performance. Individual cloud compute and storage resources are accessed via secure VLAN segmentation on top of this configuration. The combination of VMware vSphere hypervisor and high speed access to block storage via fibre channel allows full customisation of cloud resources. Security and network services available include customisable firewalls, network address translation, virtual IP addresses, load balancing and multicast.

Energy efficiency

Energy efficiency
Energy-efficient datacentres Yes

Pricing

Pricing
Price £74000.00 per instance per year
Discount for educational organisations No
Free trial available No

Documents

Documents
Pricing document View uploaded document
Skills Framework for the Information Age rate card View uploaded document
Service definition document View uploaded document
Terms and conditions document View uploaded document
Return to top ↑