Sr. Training Manager with 201-500 employees
Real User
Top 20
Stores all of our data, and there is nothing that it can't do
Pros and Cons
  • "I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome."
  • "When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that."

What is our primary use case?

It has all of our data. Our company sells contracts when you buy a car. We sell aftermarket insurance for the tyre, wheel, ding, dent, windshield, etc. When somebody buys a contract, we capture all of that data into a legacy database PostgreSQL, and my task is to incorporate that into our financial platform using T-SQL. So, I write queries, procedures, and views. I use SSIS, and I use SSRS. My job is to get the data into our financial system so that we can process claims, payments, cancellations, and refunds. 

In terms of its version, we're up-to-date. We have version 2019.

How has it helped my organization?

This is the heart of the whole company. SQL Server is where all of our financials are. It has all of our data.

What is most valuable?

I've been using SQL Server for 20 years, and there is nothing that it can't do. It is awesome.

What needs improvement?

When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that.

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,386 professionals have used our research since 2012.

For how long have I used the solution?

I have been using this solution for 20 years.

What do I think about the stability of the solution?

We do clustering. If one SQL Server goes down, it automatically goes to another one.

How are customer service and support?

I don't ever need tech support. If it breaks, I can just rebuild it.

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

They're now using a different database for contracting called Road Runner. I don't know what that is, and how it stores data. I don't know anything about it. 

There is also Postgres. I like SQL Server more than Postgres. That's only because I know SQL Server. I don't know Postgres as well. So, I can't say which one is better because I don't have the same amount of experience in both.

How was the initial setup?

I can bring up a SQL Server in an hour or so and set it up.

In terms of maintenance, the number of people required depends on the need. 
We have a team of DBAs, developers, and UA analysts. We probably have 40 people in our IT area who are maintaining our solution. I'm just the developer. I'm the guy who makes the magic happen, but without other people collecting the information that I need to make the magic happen, I'm stuck. Without the guy who is an expert in permissions, partitioning, and performance tuning, I'm stuck. So, it's definitely a team effort. You can do it all, but you don't want to do it all because then you're running your head off, and you don't really get good at anything. It would be a jack of all trades, master of none type of scenario.

What other advice do I have?

You will seldom find a database that was designed correctly. Just because you got a poor-quality database doesn't mean that you're going to get a better database anywhere else. You rarely get to build a thing on your own. Usually, you inherit somebody else's stuff. So, the challenging thing is working with what you have while trying to implement a better solution. My only advice is to be patient.

I would rate it a nine out of 10. I wouldn't give anything a 10 because I don't have that kind of knowledge, but right now, it does what I need it to do.

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
System Administrator at ARTIc
Real User
Easy query creation, scalable, and reliable
Pros and Cons
  • "We have found the solution valuable because we are able to easily create a query, shrink, backup, and make new tables."
  • "If you are a new user then this solution could be difficult, they could improve by making the overall usage easier."

What is our primary use case?

We are using SQL Server for the backend of our SAP and are planning on moving to a cloud version soon.

How has it helped my organization?

This solution has helped our organization by providing a backbone for our SAP. We would not be able to operate without it.

What is most valuable?

We have found the solution valuable because we are able to easily create a query, shrink, backup, and make new tables.

What needs improvement?

We are using an older version of SQL Server and the migration to a newer version could be made easier.

If you are a new user then this solution could be difficult, they could improve by making the overall usage easier.

In an upcoming release, they could improve the ability to customize the solution.

For how long have I used the solution?

I have been using SQL Server for approximately ten years.

What do I think about the stability of the solution?

We have not experienced any problems with the stability of this solution.

What do I think about the scalability of the solution?

SQL Server is scalable.

How are customer service and technical support?

We have not used the support from Microsoft. However, we did have freelance support a few times.

How was the initial setup?

The installation is very easy. We did not have any challenges.

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

The price of the solution is very expensive. If I went with the cloud version of SQL a license would cost me approximately 11,000 Riyals per month.

Which other solutions did I evaluate?

We have a team that has evaluated other solutions before we chose SQL Server, such as Oracle.

What other advice do I have?

I would recommend this solution. However, Oracle has a good reputation for quality that might be a better choice.

I 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,386 professionals have used our research since 2012.
Database Architect at Huron Consulting
Real User
It is one of the most stable relational databases out there
Pros and Cons
  • "It is one of the most stable relational databases out there."
  • "I would like to see native plugins built for other platforms versus having to buy third-party plugins to tap into S3 buckets and AWS Cloud. Right now, it does not have those built-in plugins."

What is our primary use case?

Our correlation and relational databases are on Microsoft SQL Server.

The company uses two platforms: MySQL and Microsoft SQL Server. Some applications are on MySQL, and some applications are SQL Server. 

I have pretty much worked all my life in Microsoft SQL Server.

How has it helped my organization?

I am in the process of creating a data strategy to consolidate multiple siloed data centers. Once my plan is finalized and approved, then we are going to execute it on the Microsoft platform.

What is most valuable?

  • Performance-wise, it is an excellent tool.
  • It is a Microsoft product, so there's a lot of support. 
  • It's not a new tool; it has been around for a while. 
  • It is one of the top five relational databases in the market. 
  • It is very user-friendly.
  • There are a lot of resources available for it.

What needs improvement?

I would like to see native plugins built for other platforms versus having to buy third-party plugins to tap into S3 buckets and AWS Cloud. Right now, it does not have those built-in plugins.

I know that they are building SQL Server for the Unix environment, which is in the beta version, and not out yet. This has been a long time wish for a lot of people. Once that is out, we'll be able to tell how diversified they have become in regards to other platforms.

It hasn't 100 percent on scalability and third-party plugins.

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

It is one of the most stable relational databases out there.

What do I think about the scalability of the solution?

With the new versions and Azure, which is in the cloud, these do accommodate scalability. Until the 2014 version, the scalability wasn't there, but from the 2016 version and above, I think they have taken all these scalability features into consideration.

How are customer service and technical support?

I have not used technical support for Microsoft with my current company. I have used them in the past. It depends on the tier of support that was purchased by the company as to the level of support that you receive.

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

Our company has probably been using this solution since it was released.

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

It is expensive, but you get what you pay for.

Since we are a cloud-based company, there is AWS pricing on top of the SQL Server pricing. The Enterprise Edition can typically sell from around $1000 dollars a month, which is not cheap. Then, there is an additional one-time Windows cost, based on the code, which can go anywhere from $30,000 to $40,000 for the license.

Which other solutions did I evaluate?

From my perspective, the two vendors for this are Microsoft and Amazon (AWS).

They are working on making it better with every release, compared to Oracle Db2 and IBM.

What other advice do I have?

I would definitely recommend SQL Server. It's not cheaper any more, like it used to be, but if you can afford it, then it's the best.

When I select a vendor, from a tool perspective, I make sure that they have full support available, have been in the market for awhile, and the solution/application is stable.

From an open source perspective, like MySQL, Aurora, and MongoDB, they have done a great job in making a robust database container.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Analysis at Kirkby (Tyres) Ltd
Real User
Top 20
Stores and retrieves data as requested by other software applications
Pros and Cons
  • "Having everything in one centralized set of databases is the most valuable feature."
  • "I think just having everything in one centralized set of databases where there is easily managed manageable."

    What is our primary use case?

    The solution is used as our backend database for our in-house applications. 

    How has it helped my organization?

    It's consolidated all of our Microsoft Access databases.

    What is most valuable?

    Having everything in one centralized set of databases is the most valuable feature.

    What needs improvement?

    Over the years additional features, data warehousing, cubing, just better performance and better manageability in terms of the actual Microsoft SQL Server AppLINK console.

    For how long have I used the solution?

    I have experience with SQL Server. 

    What do I think about the stability of the solution?

    It is a highly stable solution. It was our database of choice because of its reliability. It just does what it says on the tin. We've never experienced any issues with it. I've never experienced any issues with it crashing or anything like that. 

    What do I think about the scalability of the solution?

    The solution is very scalability. I rate the scalability a ten out of ten. 

    How are customer service and support?

    Their technical team is very efficient. 

    How would you rate customer service and support?

    Positive

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

    We switched to SQL for the reliability and scalability.

    How was the initial setup?

    The initial setup is cumbersome as it's very menu-driven. The deployment takes half a day's time. We run it on a virtual machine or virtual service. We build a virtual server. We downloaded the ISO from Microsoft's licensing website.

    I rate the setup an eight out of ten. 

    What about the implementation team?

    The deployment was done by a single person, in-house. 

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

    The SQL server is affordable. I rate the pricing a five out of ten. 

    What other advice do I have?

    I rate the overall solution a ten 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
    PeerSpot user
    Group CEO at Mmusi Group
    Real User
    Top 5Leaderboard
    Good performance, stable, and easy to install
    Pros and Cons
    • "It works fine in terms of performance and stability."
    • "I would like Microsoft to evolve SQL Server because stateful databases dying are in a way. We would like to find out if it can absorb Hadoop and other similar things. They should make it useful for data mining. Data is evolving forever, and how we store it is also changing constantly. So, SQL Server also needs to change."

    What is our primary use case?

    We do data warehousing on it. We have databases on it. A lot of our applications use it for transactions and data.

    We're using version 2019. We're trying to migrate to 2021 because 2023 is not yet that stable.

    What is most valuable?

    It works fine in terms of performance and stability.

    What needs improvement?

    I would like Microsoft to evolve SQL Server because stateful databases dying are in a way. We would like to find out if it can absorb Hadoop and other similar things. They should make it useful for data mining. Data is evolving forever, and how we store it is also changing constantly. So, SQL Server also needs to change.

    For how long have I used the solution?

    I have been using this solution for two decades.

    What do I think about the stability of the solution?

    It works fine. There are no issues.

    What do I think about the scalability of the solution?

    It is scalable. There are a lot of users. There are over 300 applications using this solution. Each application has its own users. In the technical team, there are about 13 people working with it.

    How are customer service and support?

    I logged a ticket recently when I had an issue with the data manager. Their support wasn't that bad. I would rate them an eight out of 10.

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

    I've used different solutions. There are times when I use Db2, and there are times when I use Oracle Database. Oracle beats SQL Server when it comes to procedures and process optimization.

    How was the initial setup?

    The initial setup is easy. It takes 30 minutes at the most. What limits you is just your infrastructure in terms of:

    • Do you have enough room on those servers to process that stuff?
    • Do you have enough RAM resources?
    • Do you have enough storage?

    What about the implementation team?

    I can do it by myself.

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

    It is annual.

    What other advice do I have?

    I would recommend it to other users. I would rate it a nine out of 10.

    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
    Sr. Supervisor - Enterprises Application DBA at a manufacturing company with 10,001+ employees
    Real User
    A relational database management system that's easy to use
    Pros and Cons
    • "I like that it's very easy to use, and Veeam is excellent. There are tons of experts and writers in the area now, and we don't find the same for other databases."
    • "The price could be better. In the next release, it would be better if the database was more easily extendable."

    What is our primary use case?

    Despite the core database is not SQL Server in my working company, SQL Server is widely being used as the backend for many in-house applications and customized applications like Solarwinds.


    How has it helped my organization?

    Helping to effectively and efficiently manage the business-critical data

    What is most valuable?

    - There are hundreds of "Dynamic Management Views" (DMVs) & Dynamic Management Functions (DMFs) that are system views & system functions that return metadata of the system state and they provide valuable insight into the current SQL instance state. 

    - Resumable online index rebuild 

    - Table Partitioning and the Swap out to covert a Table Partition into a separate table.

    - Python & R2 Integration, Graph Databases

    - Automatic Database Tuning

    - Very reliable Backup technology and many more

    What needs improvement?

    The price could be better:

    Compare to Oracle it is cheaper but with the existence of many open source databases currently in the market, consider reducing the Licensing cost. Secondly, with the Core-based Licensing since SQL 2012 Version, the SQL Licensing price has substantially increased.

    Postgres Extensions is a concept in Postgres to extend the Postgres features that are very useful for Performance Monitoring & Optimizations. Similarly option to extend the features as necessary.

    For how long have I used the solution?

    I have been using SQL Server for 12 years.

    What do I think about the scalability of the solution?

    It's been scalable since 2016. With each version, they are adding more features which are very helpful. 

    How are customer service and technical support?

    On a rare occasion, I had contacted technical support about five or six years ago and only when I had a specific use case.

    How was the initial setup?

    The GUI-based step-by-step initial setup is easier for the initial setup and even the Jr.DBAs can handle it with minimal training. The automated installation is possible with PowerShell Scripts and the Infrastructure Provisioning and Configurations tools like Ansible. We managed to automate the SQL installation using Ansible Playbooks and Gitlab to deploy Continous Integration and Continous Deployment.

    What about the implementation team?

    We implemented this solution by ourselves.

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

    CPU Core-based Licensing & Windows Licensing costs are additional overheads compare to open source databases like MySQL and PostgreSQL.

    Managed SQL Server Database Service in Azure is lagging with many features like Linked Server, DB Mail.

    SQL Server deployment in the Cloud does not seem to be cost-effective with respect to the Licensing cost and average Life cycle of 5 years (I reiterate, this is in my opinion). 

    If you take Postgre SQL and MySQL, they provide almost all the same features even though they are both open source databases.

    What other advice do I have?

    I recommend this solution because you can engage in database manipulation, administration and manage almost all your requirements. When compared to Oracle licensing costs, SQL Server is better. 

    On a scale from one to ten, I would give SQL Server a 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
    President at a consultancy with 1-10 employees
    Real User
    Veteran solution with critical log shipping feature
    Pros and Cons
    • "One of the things I most like about SQL Server is the log shipping piece. This is a great feature."
    • "In the next releases, I would only like more enhanced backups and more restore points."

    What is our primary use case?

    This client, specifically, is using it for Dynamics NAV. I don't know what they're calling it today. Microsoft changes the names all the time, 365 NAV Dynamics. This is ridiculous. We're using it for that, and we have more of a niche CRM database called Tour de Force. It's owned by a company called White Cup. They own a bunch of companies, and it sits on Microsoft SQL, as well.

    What is most valuable?

    One of the things I most like about SQL Server is the log shipping piece.

    I have another client who uses GP, and they use Power BI to take the data out of the back end. I'm doing an IT assessment there, so I'm not really involved in that specifically, other than the fact this person has too many rights.

    I have an auditing background, and I spent 25 years doing IT auditing as well. I understand I'm not a programmer, but I've been involved with enough of them. The log shipping really is one of the greatest features. It is not the only database you can do it in, but that was one of the better features of it because I am a backup nut. We use Veeam Backup and Replication to a local mass storage, but then we fully replicate everything in Veeam to another site with the exact same server set up at our other location. But I wasn't satisfied with that from a disaster recovery point of view. My IT company was, but I was not. I said, "I want to do SQL log shipping. I want to do an SQL backup and SQL log shipping and move it to Azure in the cloud," which is what we do every day. We have an hour by hour backup, in addition to our multiple nightly backups and our replication to our other site, and we've had to use it and it worked. This is a great feature.

    What needs improvement?

    Somebody who knows it would easily say, "No problem," because we set up our log shipping in about three hours. We sometimes have challenges with it in terms of timing, of getting it out, backing it up, and sending it to the cloud. There are always the glitches, but I get a daily report on what's going on. Around 30 backup jobs are running at all times, because it is a big company. It's a 200 person company.

    In the next releases, I would only like more enhanced backups and more restore points. Data backup and cyber protection are the number one things everybody should be thinking about now. They may not be, but they should be. We're going to go to the Azure environment because that really is a duplicate of the on-premise environment, just somewhere else.

    For how long have I used the solution?

    I would say that I have been directly involved in the ERP world for as long as I can remember, but SQL really didn't appear on my radar until the mid-90s. I know that early GP was out there. I believe it was on an earlier version of SQL. I use it heavily now because I'm the CIO. I'm a consultant, but I'm a CIO of a client for almost nine years, where we have two major databases sitting on SQL.

    So I have always been involved in a Microsoft environment.

    We are always deploying the latest version. I have multiple clients with SQL and Oracle. But my big client is always up to date.

    Whether it is deployed on the cloud or on premises depends on the client. My big client is on-premise and we have a two year plan to move to the cloud.

    What do I think about the scalability of the solution?

    In terms of scalability, I haven't seen any problems with it. We have 120 users. Every once in a while we get a record lock in our data. It's very rare though. Once every six months somebody hits the same record and same night. It's very rare. You go out for a minute, come back in, and it's over.

    I don't have any Fortune 5,000, Fortune 2000, or Fortune 1000 companies. According to the governmental definition, they're small, they're SMB, but my big client is 200 million. To me, that's a lot of money-

    But in the eyes of the government, they're still a medium company. I have clients with 1,000 people, but they're only a $50 million company. Those are not for profits. They're paying people 10 bucks an hour. It's very hard to categorize that if you're looking at it from a business perspective versus a technical perspective. I have a client with 1,000 people with 82 sites. So that's a technical challenge, but they don't have the same kind of money as the other people do.

    It's a different way to categorize it.

    How are customer service and support?

    Calling Microsoft is like calling Verizon. I wouldn't do that. I have a middleman that I work with. It's easier because they have more clout than do. I know that.

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

    This client, the big client I've been talking about, had some ancient DOS system from the 70s when I got there in 2012. They had no data dictionary note. I think it was running on an early version of Unix on a Compaq machine. When I got there, it was 15 years old. The thing was still running until six months ago. You can't believe it. This thing wouldn't die. I tried to make it die multiple times, but we converted from that system onto Dynamics NAV.

    It's a two year undertaking. The SQL was stable all the time, never had a problem with it.

    How was the initial setup?

    In terms of the initial setup, you probably need to know what you're doing. I haven't seen any real laypeople get into the tables. I know it's possible to learn. Things like Power BI have made it easier, but if you don't know what the tables are you have to be a very methodical person to be able to do that stuff. We use a company called ArcherPoint for dynamics. They're one of the largest dynamics dealers in the country, and they have their stuff together. This woman I use there knows her stuff. She knows SQL very well, and my IT company also has a senior guy who they often talk to, and it always seems pretty straightforward, whatever they do. It's never a big install.

    Usually a few hours and it's over.

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

    This client has money, so I never hear any complaints. It seems reasonable to me. I think the biggest problem that Microsoft had back in the early 2000s was that the pricing of SQL was a nightmare. You could call five Microsoft people at Microsoft, and you'd get five different prices. Microsoft has a problem. Well, they have lots of problems. They characterize themselves as perfect.

    From 40 years ago, I already knew well in advance of the clients that there is a security hole. I'm looking at Business Central, and somebody who has a global super admin of the tenant can get into the client's accounting system if they have full rights to their 365 email system. That's a big security gap. Their IT company shouldn't be in their financial system. Why would that be? I came up with the idea after talking to five different Microsoft people to just buy another tenant that they don't have access to and they said, "Oh, that works."

    What other advice do I have?

    SQL Server is a good mainstream application that has been around for quite some time, and I like when things are around for a while. I don't like to be the first kid on the block. I remember when Power BI first came out. I waited a year and a half to use it.

    The big thing for NAV was to get reports. We still use it, but we mostly abandoned it. It's really not working as well as I would've liked. And that reads SQL tables. While that was great, you had to trust the person who wrote it, that it would include all the data you needed. There's a big trust. We often found lots of problems with it, so we decided to just program all these reports inside the application. That worked really well. The thing I don't like is, I know a lot of people don't know about the backend security of SQL. They think others cannot get into their system and I tell them they can, they have the SA password. People are shocked. That's a hole that they should plug.

    They should plug that and make that more apparent to people. When I did auditing, most clients had SQL based applications, and we'd always say, "Who's got the SA password," and they'd say, "What are you talking about?" Then we would tell them, and there is all this SQL injection stuff that used to happen. I haven't heard of any hacking through the back end in a while. Because you're talking about cybersecurity being so important now, people can hack in and get into the back end, although 99% of cyber is ransomware through email.

    The risk is probably still low, but I try to close up all the gaps if I can. Clients don't know about this stuff. They don't even know enough to ask. I find a lot of IT people don't even think about stuff like that.

    I'll ask a client if they back up their data and how often. If they talk to their IT guy? If they say, "Once a night," I ask, "Okay, what if it was the middle of the day and you go down? You lose all your data." I ask if they have ever heard of SQL log shipping. They start stuttering because they don't know how to set it up.

    It would be great if Microsoft was more up-front about how to do that stuff. It's a great feature.

    On a scale of one to ten, I would probably give SQL Server a nine. I don't give anybody a perfect score, certainly not in the technology world. Oracle is out there. NetSuite is just giving it away. You have a lot of other applications not running on SQL, like Intacct, who are creating proprietary, non-Microsoft things to come against what Microsoft is offering like interoperability with different applications. They are really pushing a different environment. I think Microsoft is going to win, but Sage is not a small company.

    We have all these big titans fighting each other.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Digital Transformation Architect at Comdata
    Real User
    Very stable, user-friendly, easy to troubleshoot, and easy to manage databases
    Pros and Cons
    • "It is a very user-friendly solution. It is easy to manage the databases and troubleshoot any issue. It is a perfect solution for the volume or transactions that we need to manage."
    • "The way to make cursors and manage raw data in rows can be improved. Currently, the way to construct or build these cursors is very hard, and you can waste memory. You need a highly skilled person to make it more efficient. It can also have support for Cubes, which is the organization of data in different dimensions by using MDX languages."

    What is our primary use case?

    We developed a product that is using five or six databases supported on SQL Server. 

    What is most valuable?

    It is a very user-friendly solution. It is easy to manage the databases and troubleshoot any issue. It is a perfect solution for the volume or transactions that we need to manage.

    What needs improvement?

    The way to make cursors and manage raw data in rows can be improved. Currently, the way to construct or build these cursors is very hard, and you can waste memory. You need a highly skilled person to make it more efficient.

    It can also have support for Cubes, which is the organization of data in different dimensions by using MDX languages.

    For how long have I used the solution?

    I have been using this solution for ten years.

    What do I think about the stability of the solution?

    It is very stable. I would rate it an eight out of ten in terms of stability.

    What do I think about the scalability of the solution?

    It is scalable. You can get scalability by using the link servers, or you can create another instance in another server and make a link with that server. It is very quick.

    We have around 50 users of this solution.

    How are customer service and technical support?

    I have not interacted with them.

    How was the initial setup?

    Its initial setup is easy. It takes a week. One of the things that you need to pay attention to is the collection.

    What other advice do I have?

    It is a nice product. You can use it as you want. If you don't know how to use it, you will waste it. Oracle is more powerful than this, but it is great for our needs.

    I would rate SQL Server 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
    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.