Senior Service Architect at a tech services company with 501-1,000 employees
Real User
Stable, great with other Microsoft solutions, and can scale
Pros and Cons
  • "The solution is stable."
  • "The performance is not always the best."

What is most valuable?

While I don't like SQL Server so much, the selection was for clients so we needed to utilize it. Of course, one thing is that as great with this and other Microsoft products is that it's quite well documented and there are also light versions available. If you need to do something, you can also try it somehow on your own computer and so on. 

If I'm helping a client to define what they need to have or what they need to do in a public sector procurement process quite often we cannot fix the database as it would be limiting the competition. That's why we never rule out the SQL Server; it should be included as an option at this level.

The solution is stable. 

I haven't had issues with sizing or scaling.

What needs improvement?

If it would be more powerful it would be pretty nice. The performance is not always the best. 

Whenever we were setting up the databases, there were some character problems that did not exist on some of the other solutions. However, the exact issues are hard to recall and list. I prefer Linux solutions. That said, when we began the previous project, Microsoft SQL Server was not available for Linux platforms yet.

Nowadays, it's my understanding that there are different versions. I haven't been checking if the current versions are supporting Transact-SQL and stuff like that. I remember that when we had the first Linux-based SQL Servers were introduced, they were, of course, a bit limited from the feature point of view. Whenever it is Unix or Linux or whatever platform, it's easier to manage them and to handle them whenever you are doing remote work. 

I'm not so big fan of the Microsoft platforms as a server. However, whenever it's needed then it's needed. If you are a consultant, you need to adjust your whole mindset to whatever it's needed.

For how long have I used the solution?

I've used the solution, approximately, for several years. However, there have been gaps. There are different phases, however, I could count something like seven years where I was in an architect position in any project where this server was utilized. 

What do I think about the stability of the solution?

For the needs we had for the client it was sufficient. Whatever we needed to have - whether more server or more virtual server, the performance for the platform wasn't as good as I would like. I'm not entirely satisfied.

Buyer's Guide
SQL Server
March 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the scalability of the solution?

I haven't been utilizing the scale capabilities. I don't have a clear impression on that, however, for our purposes, we've never had an issue.

How are customer service and support?

I've never dealt with technical support. The databases were handled by the service provider or service operator of our clients. We have a public sector client and they have their partner who is handling or is responsible for the platforms. Therefore, if we had a problem with the platform, the right bureaucratic way to go about getting a resolution is that we contact the service provider they have. They probably contact Microsoft. The process is bureaucratic.

Which solution did I use previously and why did I switch?

I'm also familiar with other servers such as Oracle. While we must do as the client wants or needs, if I could choose, I would probably utilize databases like Oracle or open-source databases more often. It depends on the cases. That said, quite often I'm in a position where I cannot suggest the technology, so I use what the client requests.

What's my experience with pricing, setup cost, and licensing?

We didn't pay anything for it as it was provided for our client by the provider. I cannot say about the enterprise licenses or anything. When we began the work and we needed it for our own machines, I prefer the solutions which are available, of course, as open-source or are free. And Microsoft had this express version of their database which we can utilize as well. In that sense, it is okay, however, of course, in general, I don't know.

What other advice do I have?

I've been working for a client as a consultant so I'm helping them with deployments. With one client, we're using on-premises deployments. Our client has their own service provider or service operator so they have their own IT partner who is handling their databases. If I have understood it correctly, the databases were on-premises for our client, however, it's a bit complicated when you are having and dealing with large-scale public sector actors in Finland. There are plenty of kinds of players involved.

Whether or not I would recommend the solution depends. If you are utilizing some solutions where you need the Microsoft platform-based database, it's completely okay. And if you have, for example, the solutions where you have utilized Transact-SQL or whatever, it's okay. However, if you have this kind of situation where you can make your own choices freely, you have options. And if you're utilizing Java or C, et cetera, quite often the path or logic would go towards some of the databases on the Microsoft side.

There is no clear answer. Quite often when you begin to think about your solution or you think about what you are building, the database is the first thing you decide on. There are other factors too, such as a business case or if you're just building from scratch and so on and so on. I wouldn't like to say that I never would recommend it, however, if you are building everything from the scratch and you can make all the decisions, likely it is not the first option you have or I'd suggest. 

I'd rate the solution at an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Information Technology Manager at OrchidaSoft
Real User
Reliable, easy to maintain, easy to develop, and easy to use
Pros and Cons
  • "The performance of SQL Server is perfect."
  • "Security is an area that can be improved."

What is our primary use case?

We develop software for another company. We mainly develop on-premises solutions.

We use this solution with our accounting ERP software. Our product is called Orchida ERP and we have many clients in Egypt who are using this software. Its database is SQL Server.

We mainly work in ERP. 

We currently have a small project in SharePoint for Microsoft, but 80% of our work is with Orchida ERP

We have our software with SQL server for 20 years. Our software will not work without SQL Server. 

We provide consultancy in installing this solution for our clients.

What is most valuable?

It is easy to maintain, and it's easy to set up.

It is also easy to develop. Overall, it's easy.

It can work with many different sizes of data, anywhere from 10 to 50 gigs of data.

The performance of SQL Server is perfect. It does not need to be enhanced.

What needs improvement?

If you work with more than 50 gigs of data, it will run slower than Oracle.

Security is an area that can be improved. It could be more secure; more security is needed.

We have some clients who have been exposed to the SQL injection virus. 

We would like SQL to be able to manage this problem or to come up with an alerting system to alert the user that the server has been exposed. This has become more of an issue because of the Corona Virus and people are working from home.

Some have been infected by the SQL injection Virus and will lose their data.

For how long have I used the solution?

I have been using  SQL Server for 20 years.

Most of our clients work with version 14 and version 19, which is the latest.

What do I think about the stability of the solution?

It's a stable solution.

What do I think about the scalability of the solution?

SQL Server is scalable. Our clients are medium-sized companies, not large. They don't have professional IT.

We have 20 people in our organization who are using this solution, but we have many clients who are using it. We sell our consultancy service to more than 200 clients every year.

How are customer service and technical support?

If we have any issues, we search Google and the internet to resolve them.

Our company has not used Microsoft Support. 

Which solution did I use previously and why did I switch?

We have tried many versions of Oracle, including Oracle 11, Oracle 12, and the latest version, which is easy to maintain and similar to Microsoft.

Some of our clients are also using Express SQL. It is not good, but also not bad. If you have small amounts of data then it will meet the requirements.

How was the initial setup?

The installation is straightforward. It is easy, you continuously click the next button until you are done.

It takes 20 to 25 minutes to install. There are no issues with the installation, it is very basic.

What about the implementation team?

We did not use an integrator, we have an in-house team to install and implement this solution.

What's my experience with pricing, setup cost, and licensing?

Some of our clients purchase the license and others do not; they use Express SQL Server.

Which other solutions did I evaluate?

One of our clients is using an SQL Server on Linux. We don't use it but it is a very interesting product. It's a good trend, the Linux environment has become a market share that is growing in Egypt.

What other advice do I have?

I would recommend this solution to others who are interested in using it.

We can't compare this solution with other databases, as we do not have enough experience with other similar tools. 

Overall, SQL Server is good. I would rate SQL Server an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
SQL Server
March 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Senior Manager - RPA & Transition at a financial services firm with 10,001+ employees
Real User
Stable with prompt technical support and capable of scaling
Pros and Cons
  • "The performance is reliable."
  • "You do need to have technical knowledge in order to install the solution. It's not something a layperson can do."

What is our primary use case?

Typically, the SQL Server is used in many, many ways. We primarily use SQL Server when there is a data requirement for our projects.

Typically there are uses around where you are creating a database. I've yet to store the data in our RPA server. We need MS Excel through Microsoft.

Any sort of  RPA process where you require data through housing data or using a database, you need an SQL Server.

What is most valuable?

The solution is extremely stable. The performance is reliable.

The scalability of the solution is very good.

Technical support is pretty good. they are prompt in their responses.

What needs improvement?

You do need to have technical knowledge in order to install the solution. It's not something a layperson can do.

The scalability can always be improved.

For how long have I used the solution?

I've been using this solution for a number of years now. It's been a while. I have some experience with it. 

What do I think about the stability of the solution?

The stability of the product is very good. It's reliable. There are no bugs or glitches. It does not crash or freeze. It doesn't give us any trouble.

What do I think about the scalability of the solution?

The solution is very capable of scaling. A company should have no trouble expanding the solution as needed.

You can always add on to the server or make compartments into it.

We have a team of about 200 or more people using the solution.

We do plan to continue using the solution.

How are customer service and technical support?

We've dealt with technical support in the past. We found that their responses have been prompt. Given their engagement to typical organizations, they do decent work. I would say that we are mostly satisfied with the level of support on offer.

Which solution did I use previously and why did I switch?

We did not use any other databases prior to SQL. We only use SQL.

How was the initial setup?

The initial setup does take some time. It depends upon how you are establishing the server in your environment and depends upon the firewall of your organization. It is a lengthy process, however, it is not that grueling. Depending upon the firewall of your organization, it does take time. That influences the time.

What about the implementation team?

I can handle the installation myself. I did not need the help of a consultant or integrator. However, whoever installs it must be somebody who has the technical knowledge. Not everybody can do it.

What's my experience with pricing, setup cost, and licensing?

We have an organizational license.

What other advice do I have?

We are customers and end-users. We do not have a business relationship with SQL.

We are using the latest version of the solution. I cannot recall the exact version number.

I would recommend the solution to other users, companies, and organizations.

I'd rate the solution at an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Manager at a computer software company with 1-10 employees
Real User
I like the community where we can get good responses and replies to our questions
Pros and Cons
  • "SQL Server is quite stable. And now we are using the Lattice 2017 version."
  • "In some cases it is quite difficult, like the lack of ease of the replication and other issues. They have to improve on that. They do not have features like "always on," which is complicated."

What is our primary use case?

I handle the banking software. We have another software called City Life, a life insurance package. We develop those packages - the banking package and the life insurance package. We have almost 70 - 80% of the market share in our country. I also use and love Delphi. We develop in that language. The backend is SQL Server at this moment and we are researching how we can move from SQL Server to some other open source solutions.

What is most valuable?

The only problem with this product is that it doesn't have an open source version.

What needs improvement?

Our customers are willing to pay less. For SQL server they have to buy it, they have to purchase the license. So, if we can get some free open source, like Firebird, InterBase, Firebase, or something like MySQL and also PostgreSQL, whichever one is suitable for us, we'd like to pick one.

Additionally, in some cases it is quite difficult, like the lack of ease of the replication and other issues. They have to improve on that. They do not have features like "always on," which is complicated.

One feature which we don't like is that they are providing CLR, and CLR can only be written in dot net, C sharp. But actually it should be open for all languages to write CLR so that we can hide our code. The next thing is that the tangent PSQ is encryptable but it is decryptable, as well. From the developer's point of view, all procedures are exposed.

For how long have I used the solution?

I have been using SQL Server for a long time, since version 6.5.

We are still using it, but everybody is going towards open source, that's why we would like to go for open source as well. 

What do I think about the stability of the solution?

SQL Server is quite stable. And now we are using the Lattice 2017 version. But the most important thing is that the license cost is quite expensive.

How are customer service and technical support?

We solve issues on our own. If we need something we Google it and find it. There is a good communication base and a community where we can get responses, replies, and some blog posts.

What other advice do I have?

I'm looking at Firebird. My concentration is Firebird. I understood and researched that Firebird is the best one because it is quite robust, it has already matured, and the developer's community is quite high and stable. I'm just researching whether it can handle the huge amount of database as it did in Microsoft SQL server.

On a scale of one to ten, I would give SQL Server an eight out of 10.

Disclosure: My company has a business relationship with this vendor other than being a customer: reseller
PeerSpot user
Meindert Van Der Galiën - PeerSpot reviewer
Information Technology Software Developer at a financial services firm with 501-1,000 employees
Real User
Top 10Leaderboard
Easy to use, can be used for free, and has great scalability
Pros and Cons
  • "It's a good learning environment, it's easy enough to learn and understand. Anybody that picks up the language early on will be able to develop in it."
  • "From a development perspective, the solution needs to be a lot easier to understand or it needs to be easier to implement API packages for connection pooling so we don't have connection interruptions when, let's say, a hundred people simultaneously access the network on a given system, utilizing a specific or single database."

What is our primary use case?

We have a few use cases. They range from temporary storage to long-term storage to backup systems. We're using the full versatile suite for the product currently. It's not just a stand-alone system.

How has it helped my organization?

I don't have access to that level of knowledge. We just basically work with it on a small scale capacity in our department. That type of information and statistics are held by our IT administrators.

What is most valuable?

The solution is very easy to use for me. SQL is the most user-friendly system for databasing aside from Postgres. 

Due to the financial costs of Postgres, the SQL system is a good alternative as the product can be utilized free of charge. 

It's a good learning environment, it's easy enough to learn and understand. Anybody that picks up the language early on will be able to develop in it.

What needs improvement?

With any development language, any programming or software language available, there's always room for improvement. 

With SQL, it requires the more advanced integrated capabilities of Postgres, however, those capabilities do really come with obvious kinds of costs. For example, if SQL were to improve its functionality to incorporate the functionality that is in Postgres. Obviously, some kind of financial licensing will need to be incorporated. It's a bit of a catch-22 with a system similar to an SQL Server. If we want to avoid costs, we have to take a step back from certain integration capabilities.

From a development perspective, the solution needs to be a lot easier to understand or it needs to be easier to implement API packages for connection pooling so we don't have connection interruptions when, let's say, a hundred people simultaneously access the network on a given system, utilizing a specific or single database. Any type of connection pool or connection integration that could increase the total number of users to access simultaneously would be beneficial. That said, I also know there are some security risks involved with that type of connection pooling. However, something from SQL-side that can increase its connection access or its connection stability for multiple user access to a single database system would be great.

For how long have I used the solution?

I've been using the solution for the past six months or so.

What do I think about the stability of the solution?

The solution is extremely stable. It's got an amazing backup repository system, a fail-safe system for if any type of data should it be lost. It's got a backup system that stores everything on a day-to-day basis or an hourly basis as well. Depending on the backup and storage drive that you're using or the capacity of the server it is installed on or the local machine, you can pretty much back up any type of critical data, any recent data, or any archive-based data relatively fast. You can also pull that data again, based on the system restore and the server restore is fairly quick.

What do I think about the scalability of the solution?

The solution is 100% scalable to any kind of circumstances you find yourself in. It's easy to use and ready for any type of environment you're working on. It's scalable to any environment as well as to any amount of data. The only limiting aspect of scalability is if you're working on a local system or working on a server-based system. The physical data storage capacity is the only hindrance to scalability. If you've got sufficient data storage, then the scalability is endless.

The only people, to my knowledge, that have any access to the SQL Servers would be the administration and the department of development. The numbers range from anything from 50 to 150 people at any given time.

I'm not sure if we have plans, as an organization, to increase usage.

How are customer service and technical support?

Any technical support queries we relay to our IT administration team and the IT administration team handle it directly with Microsoft Support. I haven't actually dealt with them directly.

Which solution did I use previously and why did I switch?

I have experience with Postgres.

The main functionality that I've encountered within the six months is that Postgres is capable to incorporate itself or integrate itself with any known choosing standard API. With the SQL Server, we've got to use connection strings or connection pooling to do this. The API function is not as robust in SQL Server as it is in Postgres as the Postgres user package is based on APIs. Packages based on other companies or software languages that have the communication protocols are already enabled. With SQL Server, you have to hard code those connection strings or connection poolings for the APIs, which makes it far more difficult to use. However, it is still capable of doing it, it is just a longer approach.

How was the initial setup?

Due to the fact that Postgres is a fully integrated package installation, done from a single installer, with SQL Server you can do an advanced complex installation which requires a lot of IT administration background knowledge. Alternatively, you can do a stand-alone use case installation system, if you're just using it for a backup system. They've got a backup package that you install and that's the standard installation you use. Due to SQL's user-friendly approach, it's got a lot of pre-made installation packages that you can install based on the needs or necessities of the company.

The length of time that SQL Server standard installation takes obviously depends on network speed, and UT package downloads. It could take anywhere from five minutes to half an hour. This is all dependent on the network speed that you're running the server installation on. If you've got a fast enough network speed, it should take no longer than five minutes. With a home-based network speed, say a fiber line with 10 megs, it should take you about 15 to 30 minutes just for a standard installation.

What's my experience with pricing, setup cost, and licensing?

The solution is very affordable. It can be used free of charge.

There are payment packages for SQL based on dollars for any level of additions. They offer enterprise, express, and production additions that are available as well as community additions and student additions, which are completely free.

Which other solutions did I evaluate?

Before anybody had even considered doing any kind of database access, they reviewed all possible capabilities, according to price, functionality, and integration requirements. Ultimately, they settled from the start on SQL Server.

As far as I remember, our administration team did review other options. I'm not familiar with the options that were available prior to this, however, as they stated to me, before SQL has been the one from the go ahead, the option that they chose and they've been running with it since then.

What other advice do I have?

Overall, I would rate the solution at a nine out of ten. We've been quite happy with the solution so far.

Basically with any databasing system, SQL included, a company should be looking at the requirements for why they're looking for any type of databasing system. Is it for backups? Is it for storage? Is it for cross-communication between departments or inter-department communication? Who's going to have the access prior? If it's just going to be on a technical or development level, not a lot of people need to worry about integration requirements except the installation team. Other than that, companies should just look at the financial as well as system requirements that are basically needed for the project or for the company you're in. If a company needs a large scale solution, financially speaking, SQL would be a good solution, however, Postgres would be a far better solution due to its capabilities, integration and API access.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Officer at a manufacturing company with 201-500 employees
Real User
Easy to set up with ample online documentation to resolve issues independently
Pros and Cons
  • "Stability and usability, which is quite simple, are two of the solution's most valuable features."
  • "The solution could be better when it comes to security."

What is our primary use case?

While we were still using the solution, we employed version 2008, which is a bit on the old side. 

We basically used the solution for hosting the database for Sage ERP.

What is most valuable?

Stability and usability, which is quite simple, are two of the solution's most valuable features. 

What needs improvement?

The solution could be better when it comes to security. 

The solution is part of Windows services, which means that if these should stop running, the database system, too, would be affected. This makes it very crucial to constantly monitor the SQL Server, something which reflects on cheap personnel time. 

Scalability could be better.

Although it comes with a cost, using the most recent version is highly advisable, since it would ensure a certain measure of bug fixes and stability. The sole issue would involve the cost, as this is expensive. 

When it comes to integratable features, the monitoring should be addressed. 

For how long have I used the solution?

We used SQL Server for nearly six years, although we have since moved to another platform. We have used the solution at some point within the last 12 months. 

What do I think about the stability of the solution?

The solution has good stability, although my advice is to use the most recent version towards this end, to provide for bug fixes. This will ensure some stability. 

What do I think about the scalability of the solution?

The scalability could be improved. 

How are customer service and support?

As support would have involved a licensing fee, we opted not to make use of this. 

We find there is ample documentation online to allow us to resolve issues through independent research.

How was the initial setup?

The initial setup was straightforward.

What's my experience with pricing, setup cost, and licensing?

Although it comes with a cost, using the most recent version is highly advisable, since it would guarantee a measure of bug fixes and provide some stability. The pricing is expensive, though, this being the sole issue. 

We chose not to make use of support, as this would have incurred a licensing fee. 

What other advice do I have?

I rate SQL Server as an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
SQL Server Senior Architect at a computer software company with 1,001-5,000 employees
Real User
High performance, easy installation, but better integration needed
Pros and Cons
  • "SQL Server has good performance. It is one of the best features."
  • "SQL Server could improve the integration with nonrational database solutions, such as MongoDB."

What is our primary use case?

SQL Server can be used for managing and storing information.

I have a lot of databases with more than one terabyte of information and we use technology, such as Stretch database to switch out the information to Azure databases with this type of technology.

What needs improvement?

SQL Server could improve the integration with nonrational database solutions, such as MongoDB.

For how long have I used the solution?

I have been using SQL Server for eight years.

What do I think about the stability of the solution?

SQL Server has good performance. It is one of the best features.

What do I think about the scalability of the solution?

We have approximately 300 instances of SQL Server. 

I have approximately five customers using this solution.

How are customer service and support?

I currently have one ticket open with Microsoft support and I have been waiting about two days. However, it's not a critical incident. The technical support they provide us is good.

How was the initial setup?

In the latest version of SQL Server, Microsoft has split the product. For example, if you want to start with the engine or the reporting server you have to download it separately.  I think that the installation is easier on the new versions. There are other kinds of options that you can set up in the installation progress. For example, the number of 10 DV files or the limit of maximum use of memory.

The installation process takes approximately 10 minutes.

What's my experience with pricing, setup cost, and licensing?

There is a license to use this solution. However, the model is not easy to understand. There is a guide you have to read about all the information on how it works. If you read this documentation, you can understand how it works. We are paying for our SQL Servers by CPU cores with an enterprise license.

What other advice do I have?

If a new company wants to implement SQL Server, they need to know that there should be a person who has all the knowledge about DBA position, such as how the SQL Server will be set up because I have a lot of customers and when I checked they have a lot of bad options or practicing in their SQL Servers instance. If someone wants to start with SQL Server, they have to improve and have good knowledge about this technology. It's important to have knowledge about this technology. They should take some courses or maybe have a person who has all the knowledge about this technology with certification, it's the most important. It's not easy to keep up to date with the best practice from a provider, in this case, Microsoft.

I rate SQL Server a seven out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Senior Manager at a financial services firm with 201-500 employees
Real User
Easy to manage with good stability and knowledgable technical support
Pros and Cons
  • "The solution is easy to set up."
  • "The configuration process can be a little complex."

What is most valuable?

We find the Microsoft SQL Server affordable compared to its real competitors. 

We find it easy to manage. 

It offers a very robust infrastructure for us.

The solution is easy to set up.

We have found the stability to be good.

We've had a good experience with technical support. They are helpful.

What needs improvement?

We may use different levels of SQL Server when it comes to licensing. We have some Enterprise and some Standard services. They can improve the recovery processes of the replication or disaster recovery scenarios for the lower-tiered version, such as the Standard server.

While we have many options in Enterprise, it's expensive for most companies.

The configuration process can be a little complex. 

Technical support can take a while to respond in Turkey.

The solution may be better with some integration with some factory cloud software. With the standard version, the lodgement process is never enough. We are replicating near real-time to make recovery easy and to make all the RPO targets as expected. 

You cannot recover SQL Servers, especially for big financial companies like ours. It's not easy to erect SQL Servers on any other site, and with an acceptable data loss in the foundations.

For how long have I used the solution?

Personally, I have used the solution for about 15 years at this point. It's well over a decade. I've used it for a while. 

What do I think about the stability of the solution?

The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. it's reliable. 

How are customer service and technical support?

The Microsoft team never responds fast in Turkey. I cannot say they are fast. Unless you have some Enterprise agreement, they're not quick. However, I find that when I deal with the same technician a few times, they are quite good and very helpful. They are very capable. They know what they are talking about. 

Which solution did I use previously and why did I switch?

We also use Oracle Servers. 

How was the initial setup?

The initial implementation is easy and straightforward. It's not overly complex or difficult to set up.

However, it's not just the server we have to set up. We have a cluster environment. Mostly it's just, click, click, click and you are done, however, the configuration process is a bit more difficult. Adjusting performance levels, in particular, can be a real challenge.

What's my experience with pricing, setup cost, and licensing?

The enterprise version of the solution is very expensive and most companies would likely find that they wouldn't be able to afford it. 

What other advice do I have?

We're a customer and an end-user.

I'd rate the solution at a nine out of ten. We've been very happy with its capabilities. 

I would recommend the solution, however, it will only be effective if the company hires an effective administrator. While there are default settings, you will likely need to configure quite a bit and connect most of your hardware in the correct way. To be effective, it really needs to be tuned by a professional. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Product Categories
Relational Databases Tools
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros sharing their opinions.