InterSystems IRIS vs. Valentina

It is best suited in the scenario where a single interface is required for providing [a complete end-to-end] solution to the customers. You don't need [a] separate platform to write code or [perform] database operations. All you need is InterSystems IRIS software and you are done. You can also use analytics functionality which is one of the greatest [features] which many customers need for their solution[.]

If you have to manage a lot of different databases from different vendors, you could do well by standardizing on this product. It checks all the boxes for a proper database management studio. You would only have to learn one product to manage them all. However, if you are looking to find a good product for a single database vendor, you might be better off finding a tool that was designed specifically for that vendor product.

Incentivized

• Connecting with mutliple vendor platforms and systems allowing us to consume and provide data as needed.
• Allowed us to implement our own RESTful api engine to server data to our internal applications.
• Setting up their recommendations for high availability allow us to perform server maintenance with minimal down time to our users.

• Foreign Key Constraint data viewer! This was a tremendously helpful feature that not many other products have. Just pick a constraint and see the data in the child tables! No setup required!
• Supports any and every database imaginable.

Incentivized

• Enhanced documentation, more comprehensive and user-friendly documentation, including detailed tutorials and examples
• Improving compatibility and integrations with others programming languages
• Introducing tools and techniques to optimize the performance of ObjectScript applications, such as profiling tools, performance monitoring utilities, and code optimization guidelines
• A better compatibility with Python libraries

• Somewhat laggy performance. Boot up speed was on the slow side and connecting to our database servers was also a little slower than other products.
• User interface can be a little clunky. Instead of the usual tree view of servers, databases, and schemas, you are presented with lists that you click on and get new windows to pick the new list of data from. Not organized efficiently.

Incentivized

The interface is very intuitive, the documentation is very good so it is not complicated to operate.

The security is complex, but you can create a special role to access and the user ONLY can operate with the part that it allows.

Also, you can examine the data very quick with the SQL Browser integrated.

The InterSystems WRC has always been helpful and responsive. The folks I have spoken with are always understanding of our needs and questions and regardless of if the question is simple or complex we are always met with the same professionalism and helpfulness every time. I have no hesitations contacting InterSystems for help!

Will done based on a proper planning, so this will makes execution more easier and better.

Tibco was not originally planned to be used for HL7 Integrations and as such we had to create some very complicated processes in order for the messages to parse and validate appropriately. It was simply not built for this type of interoperability. Comparatively, InterSystems IRIS for Health (HealthConnect) has out of the box HL7 features that would parse messages, offer a variety of validation options, simplified data lookups and transformation and reduced the amount of time it took to develop connections with out vendor systems. InterSystems IRIS also allows one to push just single files into production at a time so there is less of a chance of us pushing something that should not be in production yet as our previous system was set up to with TIBCO deployments

Incentivized

Compared to Microsoft's SQL Management Studio, Valentina studio was comparable, just harder to get used to in the UI department. It ran slightly slower than other products but did save some time with neat features they baked into the product. However, in using DBeaver Community and DBForge Studio for PostgreSQL from Devart, we found different products that the team ultimately decided to use. DBeaver has all of the features we needed most (minus the constraint data viewer) and a more intuitive UI that we were used to. DBForge Studio for PostgreSQL has a very standard Windows look and feel and lacks some features, like database/table designers, but makes up for those shortcomings in the much easier filtering and sorting options right in the data grids. You can even write a query and edit the data returned, which is something we don't see in many of these tools. Our team ultimately settled on the developers using DBeaver and the support team that needs data viewing/editing capabilities using DBForge Studio.

Incentivized

• Very Fast and scalable software to deal with big data flow, safe and robust.
• The studio IDE is quite old fashion and lacks a few facilities
• amazing for complex data consumption, its milyi-model capability wich allows multiple different models for a single set of codes.

• It saved time in some areas of finding child data by not having to write queries to find it.
• The user interface caused some extra training for some users and ultimately caused them to not like using it.

Incentivized