Performance is the number one challenge for any database, immediately followed by scalability. This means, therefore, that not only must the database be able to grow as the company and the data in its possession increase, but also that the database must be able to maintain content uploading and updating and queries response times consistent with the business needs.
Sadas Engine is over 100 times faster than transactional DBMSs and is able to research huge amounts of data without compromising performance. In fact, it has been specifically designed for business intelligence, analytics, big data, CRM, DWH applications, allowing to upload, manage and analyze any volume of data and always guaranteeing exceptional performance in the ETL and query phases.
Sadas Engine + QlikView
QlikView is wholly based on an in-memory data-store. In this way, it can refresh data in real time, allowing for immediate and interactive explorations. But when importing DBs of significant dimensions, the .qvw file can easily assume such a size as to seriously affect (or even prevent) the usability of the product.
An immediate solution would be to increase the physical capacity of the machine (RAM memory). But this increase of resources would not be cost-free, and may not be sustainable all the same if compatibility with even bigger databases (e.g. 50-100 GB) is required.
What to do then?