We changed our name from IT Central Station: Here's why
Prashant Baste
Solution Architect at a tech services company with 1,001-5,000 employees
Real User
Top 20
Very fast with an easy initial setup and reasonable pricing
Pros and Cons
  • "The initial setup isn't overly complex."
  • "The backup capacity needs to be bigger."

What is our primary use case?

We are primarily using the solution for pulling data and analysis.

In the auto industry, are the dealer management systems for which there is kind of portals from which the dealers are maintaining information can have access to retail data, bookings, and details surrounding individual customers.

We are fetching data and using it for analytics purposes, basically.

What is most valuable?

The basic features of the solution are excellent overall.

The initial setup isn't overly complex.

The pricing is reasonable.

The solution scales well.

The solutions very fast. It reads and writes six to eight times faster than any other tool.

What needs improvement?

The solution is very different from Oracle, which is a product we also use.

Mainly the data capacity needs to be improved. The data values are limited. They are smaller or medium scale. The MySQL is working fine, however, when it comes to large data sets or large data volumes, Oracle can handle them better. The backup capacity needs to be bigger.

What do I think about the stability of the solution?

When it's medium or small-scale data volume, people are referring to MySQL, however, when the data volume grows the people are referring to Oracle. In my estimation, the stability is fine.

What do I think about the scalability of the solution?

The scalability of the product is pretty good. It can scale effectively and expands better than other options.

We have around 40 users on the solution currently.

Our main usage is not for the database and we simply use basic aspects of the platform.

How are customer service and technical support?

Technical support isn't an aspect of the solution I know too much about. I've never been in direct contact with them. Therefore, I can't speak to how helpful or responsive they are. 

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

We also currently use Oracle. 

How was the initial setup?

The initial setup isn't too complex or difficult. It's pretty straightforward. It's less complex of a process as compared to other solutions.

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

The cost isn't overly expensive. It's very reasonable. Our customers are happy with the price. It's in a good range.

What other advice do I have?

We are partners with Microsoft. We use multiple deployment models, and typically those are private cloud or on-premises options.

Overall, I would rate the solution at an eight out of ten. We've been mostly very satisfied with the capabilities of the product. It's fast. It's our preferred product.

I'd recommend the solution to other users and organizations.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
AhmedElbadry
NMS Service Automation & RPA Technical Lead at Vodafone
Real User
Top 5
Scalable with a straightforward setup and good stability
Pros and Cons
  • "From a security perspective, we have no complaints."
  • "It would be ideal if the solution offered better integration capabilities."

What is our primary use case?

The solution is a part of a product. We use it for our database, among other items.

What is most valuable?

The solution is very stable.

The product scales well.

From a security perspective, we have no complaints. 

The initial setup is very straightforward. 

What needs improvement?

The solution should work to improve its search functionality.

It would be ideal if the solution offered better integration capabilities. In the future, we expect that our company will need to make more integrations with other systems.

For how long have I used the solution?

I've been using the solution for three years. It hasn't been that long.

What do I think about the stability of the solution?

So far, the stability has been very good. We haven't experienced any crashed or anything of that nature. There are no bugs or glitches. It's reliable and the performance is good.

What do I think about the scalability of the solution?

The solution is very scalable. The only thing that would limit its ability to expand is how your environment is designed. That said, a company should have no trouble scaling it if they would like to.

There are only five of us using the solution right now.

We do plan to increase usage in the future.

How are customer service and technical support?

While I haven't had a chance to open a ticket with technical support, I plan to open one next week, as I have an issue I need to ask them about. However, since I have yet to be in contact, I cannot evaluate their level of service.

How was the initial setup?

The initial setup is not complex or difficult. It's easy. It's very straightforward and the setup guide is available if you Google it. Anyone can search for the installation guide on whichever version you're installing.

The deployment is quick. It only takes about 30 minutes or so.

We have a technical team of five engineers. If any maintenance is needed, we can handle it. 

What about the implementation team?

I installed the product myself. I found an installation guide and just followed the directions. I didn't need the help of a consultant or integrator.

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

We do not currently pay a licensing fee in order to use this product.

What other advice do I have?

I'm currently using the 2017 version. I am not using the latest version of the solution.

In general, I would rate it at an eight out of ten. For the most part, we have been satisfied with its capabilities.

I'd recommend the solution to other users and organizations.

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.
Flag as inappropriate
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
566,121 professionals have used our research since 2012.
Systems Engineer at a tech services company with 11-50 employees
Real User
Top 5Leaderboard
Stable, easy to use, and offers a quick deployment
Pros and Cons
  • "The installation is pretty straightforward."
  • "The pricing of the product could be better."

What is most valuable?

Right now, we are using DB2 and the SQL Server. It's really helpful for the replication of data. It's real-time and very easy to use.

The product is very stable. We find it to be reliable.

The scalability is okay. 

The installation is pretty straightforward.

What needs improvement?

For now, we've found the features to be sufficient. I cannot recall feeling anything is actually missing.

The pricing of the product could be better. They could make it more reasonable or more competitive.

Microsoft's technical support could be better.

For how long have I used the solution?

We've been supporting these servers for a couple of years at this point. It's likely been about two or so years. We've worked with them for a while. 

What do I think about the stability of the solution?

The solution is very stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. We're happy with it.

What do I think about the scalability of the solution?

The scalability potential depends on the resources. If the resources are enough, we can scale it. For us, it's already enough. However, if a company plans to expand, it should be prepared for that beforehand. 

We have more than ten users on the solution currently.

How are customer service and technical support?

Microsoft technical support could be improved upon. They aren't the best. They could always be better.

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

We also use IBM DB2. We support it for our customers.

How was the initial setup?

We have found the solution to be straightforward. It's not overly difficult or complex. A company shouldn't have any issue with implementation.

The product implementation process depends on the needs of the client. For us, deployment was around 30 minutes to one hour. It's pretty quick.

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

The solution could be priced more competitively. We'd, of course, like it to be lower. Microsoft can sometimes be expensive.

Each customer needs their own license.

What other advice do I have?

We use the solution both on the cloud and on-premises. 

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

I would recommend the solution to other users and companies. They should know that it is very easy to use. 

We had two people that handled the initial setup - an engineer and a manager. It's pretty easy to handle if an engineer is doing the setup.

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
Flag as inappropriate
Head of IT, CTO at a insurance company with 51-200 employees
Real User
Reliable, scalable, and user-friendly but the pricing could always be better
Pros and Cons
  • "It's much more friendly in comparison with Oracle."
  • "I am fine with the pricing, but pricing is an area that can always be improved."

What is our primary use case?

We are using this solution as a database. The main purpose is as an SQL Server.

How has it helped my organization?

Our backend and core systems are using Microsoft SQL Server. We have no complaints from anyone who is using it.

We have nothing that we can compare it with.

What is most valuable?

It's much more friendly in comparison with Oracle.

We are using the standard features. I don't see any areas that can be simplified with the standard functionalities. We don't use any special extended features.

From my point of view, using SQL Server 2017 and 2019 is very good. I haven't experienced any issues or been in a situation where I was struggling with problems for which I didn't have access to proper documentation or proper functions.

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?

After eight years in our company, we have not had any issues with SQL Server from a stability point of view.

What do I think about the scalability of the solution?

We are a small company. We don't have any issues with this and we are fully virtualized. If we need to, we can extend the amount of CPUs as we want.

Our core system is being used by 50 users, but they are not accessing the SQL Server. We have approximately 10 users in our company who are using the SQL Server.

How are customer service and technical support?

I have never used technical support.

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

I am using Avamar and Data Domain. I have been using Data Domain for four or five years. It was used as the data storage for the backup solution in our sister company.

I worked with Oracle in the previous company. Microsoft SQL Server is better.

We have also used Software Center, Active Directory, Microsoft Exchange, and almost everything that is Microsoft-based.

How was the initial setup?

It was installed by an outsourcing company. It is another sister company.

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

It's cheaper than Oracle.

I am fine with the pricing, but pricing is an area that can always be improved.

We are Microsoft D-level partners. Pricing is not an issue for us, because of the outreach of our mother company.

What other advice do I have?

We are a Microsoft-based company.

I would rate SQL Server a seven 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
Technical Content Writer at a computer software company with 51-200 employees
Real User
Top 5Leaderboard
Reliable with a simple setup but requires a knowledgable user
Pros and Cons
  • "The solution is stable. It's reliable."
  • "The scalability could be better."

What is our primary use case?

We primarily use the solution to store databases. 

What is most valuable?

Since MongoDB, we have come up and there are lots of tools that do enhance the database management system or keep an eye on our data. People can easily access it. 

The solution is stable. It's reliable. 

The initial setup is simple. 

What needs improvement?

MongoDB is a bit better. A traditional database system, like the SQL Server, is failing to catch up.

You need an experienced person to use that piece of technology so that you can store everything in a logical manner. We'd like it to be easier to store in a logical manner.

The scalability could be better. 

For how long have I used the solution?

We've been using this solution since 2012. It's been a while at this point. 

What do I think about the scalability of the solution?

It's not scalable. It hinders your performance as it's slow in nature and you need experienced people to work on it. That is why it's not very scalable.

We currently have ten to 15 users on the solution. 

At this time, we have no plans to increase usage. We are focusing more on MongoDB.

How are customer service and support?

We don't have any experience with Microsoft technical support. Therefore, I wouldn't be able to rate how responsive or helpful they are.

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

We did not previously use a different solution. We are currently moving towards MongoDB, however.

How was the initial setup?

The installation is easy, especially since the new version has come up. Now, with the latest versions, installation is easy.

I cannot remember the time it took to complete the installation.

What about the implementation team?

Earlier, we had to bring in a technical team, however, our own technical team is quite experienced now. They can now do it themselves.

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

We pay a yearly subscription fee. 

What other advice do I have?

We use both cloud and on-premises deployment models. We're using the latest version of the solution. 

I'd recommend the solution to other users and organizations. If there are people who can't afford MongoDB or if an organization doesn't want to migrate to MongoDB, it's important to keep in mind the users would have to learn the fundamentals of the SQL server first. Knowledge of it is a necessity.

I'd rate the solution at a six 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.
Flag as inappropriate
Analytics Manager - Data and Capability at a financial services firm with 1,001-5,000 employees
Real User
Scalable as a cloud, good as a data warehouse, and offers good analytics
Pros and Cons
  • "As a data warehouse and storage solution, it's quite good."
  • "The solution could use better governance on the management side, especially around data governance."

What is our primary use case?

We use the solution for many tasks. We use it as a data warehouse. However, we also use it for workflows and processing jobs.

What is most valuable?

The analytics are pretty good.

As a data warehouse and storage solution, it's quite good.

It's easy to put the data back onto the SQL Server or Oracle. 

The solution is pretty fast. We find it to be responsive.

There are a lot of services, such as the SSISS, SIS, and SSI's that work quite well.

What needs improvement?

The solution could use better governance on the management side, especially around data governance.

The product could do better at allowing for integrations. 

For how long have I used the solution?

I've been working with the solution for many years. It's likely ten to 15 years at this point. It's well over a decade, so I have some long-term experience with the product overall.

What do I think about the scalability of the solution?

The scalability for the solution is good, at least where it concerns the cloud. Using the cloud makes everything very easy to scale. On-remises, if you run out of dick space, it's a bit difficult.

How are customer service and technical support?

We've been in touch with technical support in the past. We manage the data center ourselves, however, if we run into issues we know we can contact them for assistance. I'd say we are quite satisfied with the level of support we get.

How was the initial setup?

I can't recall how the initial setup was. It was a while ago. We've had the solution for a very long time.

What other advice do I have?

We're just customers and end-users.

I don't know if I would recommend the solution per se. There are other options out there. Something that is a NoSQL database. Something like Snowflake, for example, might be a very good option for data warehousing. They are more adept at handling different types of data.

You shouldn't have to create tables or systems, you should just be able to query files.

I'd rate the solution at an eight out of ten. However, for the current scenarios we have, there are other options that may be more suitable. It's not the only product available on the market, and the competition is quite good.

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.
Database Administration Team Leader at a transportation company with 10,001+ employees
Real User
Top 10Leaderboard
A stable relational database management system with a valuable Always On feature
Pros and Cons
  • "I believe Always On is the most valuable feature. It's also easy to use and not very tricky."
  • "Analysis services have a lot of room for improvement. Basically, manageability on the available tools. They should have improved them already. They are not very efficient. My main headache is with the analysis service, and it would be really good if Microsoft developed some additional tools that are more user-friendly to manage the analysis. This is both from the perspective of management, users' roles, and performance analysis. My main wish for SQL Server would be that management tools for analysis services grow and mature a bit."

What is our primary use case?

We use it for both database services and analysis services.

What is most valuable?

I believe Always On is the most valuable feature. It's also easy to use and not very tricky.

What needs improvement?

Analysis services have a lot of room for improvement. Basically, manageability on the available tools. They should have improved them already. They are not very efficient. My main headache is with the analysis service, and it would be really good if Microsoft developed some additional tools that are more user-friendly to manage the analysis. This is both from the perspective of management, users' roles, and performance analysis. My main wish for SQL Server would be that management tools for analysis services grow and mature a bit.

For how long have I used the solution?

I have been using SQL Server for about 15 years.

What do I think about the stability of the solution?

It's stable. The database service is better than the analysis service, but it's quite stable. It's as stable as the support it has. If it has a good infrastructure and good machines with disks, it's quite stable.

What do I think about the scalability of the solution?

SQL Server is vertically scalable. We have about 3,000 people using this solution.

How are customer service and technical support?

We haven't used their technical support a lot. I would say it depends on the scope of the help you need. On a scale from one to ten, I would give technical support a seven.

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

I don't know the exact prices because my focus is essentially technical and not on the bills. A few years ago, they changed the billing policy for the Enterprise Edition, and it became less attractive. But I believe they are still cheaper than Oracle. SQL Server isn't cheap, but it's not expensive either. 

What other advice do I have?

I would tell potential users that it's important to have a good infrastructure, but my advice is for any database, not only SQL Server. It's important to have a good infrastructure and a good network if you're planning to use Always On and clusters. I believe the most important thing is the infrastructure where the SQL Server will be based.

On a scale from one to ten, I would give SQL Server an eight.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Specialist Systems Engineer at a tech services company with 51-200 employees
Real User
Easy to install and helps us to keep customer data safe
Pros and Cons
  • "I use the menu on the management view credit section to get information from the database."

    What is our primary use case?

    We use SQL Server for database integration as we sometimes use queries to take information from the database. For example, if I need a couple of information that is archived or not indexed, I will inform the SQL Server team to help.

    What is most valuable?

    I use the menu on the management view credit section to get information from the database.

    For how long have I used the solution?

    I have been using SQL Server for eight to ten years, but I still check Google for things that aren't clear to me. For service delivery, we use on-premises solutions for our customers.

    What do I think about the scalability of the solution?

    We don't use SQL Server as our primary product. Our focus is on safe customer SQL admin as we don't want problems with customer data in our system.

    How are customer service and technical support?

    I think we consulted once for support in the active directory. We requested the support of Integration Engineers for installation, and their service was very good. However, in the last eight years, we have also used Microsoft support with satisfaction.

    How was the initial setup?

    For the initial installation process, I did an installation for database testing using SQL Server Express. Sometimes, the trials for the samplers are not allowing the SQL Server Express. So, when I was doing the installation, I just selected database management because it isn't the default and it has helped me not to fill out the same details for future use.

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

    I cannot answer that question concerning pricing and licensing because I'm just a technical staff member. However, we are just a customer of Microsoft and some of our clients say SQL Server is very high in price.

    What other advice do I have?

    SQL Server is a very good product and we use Microsoft SQL Server software that runs on Windows as most of our clients make use of the Windows operating system. But I don't have a hundred percent trust in Microsoft products. Why am I saying that? This is not a security issue. I am just... We are hitting this kind of issue because, as you know, Windows servers sometimes get corrupted or we need to restart them.

    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.