Ingest

RainStor can ingest data from a production relational database, a data warehouse or a machine generated data source such as logs from a network and can function as both a primary or secondary repository. When data is sourced from a production database or data warehouse, RainStor functions as a secondary repository and is generally embedded and sold as a database archive, application retirement or analytics data retention solution.

RainStor is used as a primary repository for machine generated data that is immediately historical, never changes but is required to be kept online in an immutable, tamper-proof form.

RainStor expects incoming data to arrive in a delimited data format (e.g. CSV or BCP) or XML. This data can be served up through native export utilities, ETL tools or ESBs and the RainStor load process can be executed on a one-off, scheduled or continuous feed basis.

RainStor can load volumes at rates of 30 to 50 thousand records per second per core and this ingest process scales up (across cores within a server) and out (across servers) with 90% efficiency. This enables RainStor to continuously de-duplicate and store billions of records a day, while at the same time providing continuous query access.