InterSystems Caché® was a multi-modal operational database for transaction processing applications, that provided several APIs to operate with same data simultaneously: key-value, relational, object, document, and multidimensional.
Great for a one for all, heavy bundled, and licensed solution. When trying to evolve and scale, it can be very limiting. Think future proof as something that fits now could be hard to change later and work around.
Microsoft SQL Server is ideal for highly available SQL workloads by using SQL Server Always On availability groups. Microsoft SQL Server might not be appropriate for solutions which require a very low resource footprint, since it requires significant CPU cores and RAM memory as well as high IOPS, always depending on the usage scenario.
The great functionality hides behind an old UI that can be cumbersome to navigate, making Cache configurations take more time.
The easy installs of Cache need specific setups to work well, and if yours is unique or if your servers are highly specialized on a networking level in terms of ports, VMs, or otherwise, then there may be some difficulties getting things to work.
I think it is unlikely that sql server has disappointed someone, it is likely that someone will come initially discouraged if the needs and problems that occur are very challenging, but definitely have a SQL oriented system means having a solid base to work and on which maintain the their data securely
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
I've only worked with products that do one thing before, but there's so much that Cache offers versus piecing different services together manually. Not only does the product offer a more robust tool-set, but the support is wonderful and I've never encountered a better vendor in any industry in terms of how well they interact with their customers and care about helping you solve your problems. They want you to grow and to get better.
Microsoft SQL is slower than MySQL and Access but far more feature-rich and reliable. Access is almost obsolete nowadays, so not too many people are considering it, but unless budget or an open-source ethos is a factor, Microsoft SQL is superior in every way. Many commonly used tools, like Crystal Reports, support it.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.
