Azure SQL Managed Instance vs. IBM InfoSphere Optim

Data management scenarios where there is a strong need to provide dynamic context for web based applications. Also can work as an infrastructure piece for ticketing systems without relying on another set of database software. The ease of importing data from Microsoft Excel &/or .csv files makes this really easy to use when importing data into the managed instance.

Incentivized

Optim is especially recommended for those companies that have their own or third-party development teams that must be provided with a complete data environment to test the applications. Optim is not recommended for use as an ETL or Data Integration tool.

Incentivized

• ease of use with microsoft products
• data management
• GUI interfacing

Incentivized

• Easily extract data from production environments with no-coding
• Intelligent filtering capabilities using physical or logical relationships.
• Advanced data masking funtions

Incentivized

• hard to use without Microsoft knowledge
• Intimidating CLI
• Commands are not intuitive

Incentivized

• Poor UI
• Complex architecture

Incentivized

Azure to our enviironment where we have everything integrated stacks up far better than MySQL where we would have to reinvent and use everything to fit a MySQL environment including the data and the commands within that data. Furthermore, doesn't work really well on SQL Management Studio which makes it completely useless for what we are trying to do.

Incentivized

• Decision Driven decisions have been quicker
• Negatively cumbersome at start when training
• Positive use of PaaS services instead of devoting VMs

Incentivized

• Optim can save companies a lot of money by protecting the sensitive data found in their databases, thus avoiding the theft of real customer information with the economic and media impact that this has.
• Accelerate the generation of non-productive environments saving time from human resources.

Incentivized