iData Frequently Asked Questions

Frequently Asked Questions


Where is my data hosted?

At present iData is solely an on-premise or customer cloud deployed tool. As such all of your data is within your own governance and security policy framework. Where IDS provide access to environment for trials or proof-of-concept exercises, these are typically hosted in a West-Europe datacentre provided by Microsoft.

I have a proof of concept to run hosted or delivered by IDS. Can I provide IDS with production data or access to production data sources?

Unfortunately IDS will not accept responsibility for client sensitive data. Where we have stringent processes and policies in place to ensure the security and traceability of data, we will only provide services and solutions within our client's own data landscape. This allows our clients full confidence in their own data security. 

Is my data encrypted in flight and at rest?

Our iData 2 product supports encryption in flight (movement of data and information from point to point), and IDS strongly recommend that it be configured to provide access through secure means. Data sources are configurable by the client. iData supports database and local file storage encryption. 

Are connections to data sources charged at and extra cost?

Our current licence model provides no limits to the number of data sources connected to. The connections and transformations our clients use iData for, increases their return on investment in the product.

What data connections and data sources does iData support?

iData currently supports direct connections to Microsoft SQL Server databases. The product will also read and output comma separated variable (CSV), Excel, and flat text files. We are striving to provide more connectivity on our roadmap enriching the connectivity and capability of our product.

If I have a non-supported database platform, can I still use iData?

Yes. This is a common scenario. IDS often face situations where access to data sources is restricted. To enable the benefits of the product, this can be circumvented by extracting the data to CSV format.
Our Kovenant TM methodology containing the concept of the initial 'Data Ingestion' stage, where data is taken from disparate systems and standardised into a 'staging' area for processing.

Is User licencing restricting access to data sources?

No, user limitations applied to a licence are set for access to the product, not the products connectivity.

What architecture do I need to implement iData in my environment?

When implementing iData the computer network, connectivity, and specification vary from client requirement to client requirement.
The most typical configurations are where a dedicated server is provisioned, where iData is installed along side a Microsoft SQL server instance. This server then has network connectivity to the data sources that are expected to provide, and accept the data outputs from the iData processing stages.

What specification of computer platform do I need to run iData?

The platform requirements for the iData product are available here: