Microsoft SQL Server Reporting Services Reviews

We use it to create reports within our internal systems, specifically our proprietary systems. So it's integrated into our existing applications.

We were able to embed the report builder within our internal proprietary systems, improving our reporting capabilities.

It's integrated, making it easier to use. It also provides better functionality within the SQL Server BI toolset.

There is room for improvement in the pricing model. The overall suite, including the BI suite, is expensive.

I have had a good number of years of experience.

It's pretty solid. It is a stable solution.

It's pretty scalable.

I usually refer to the FAQs for assistance.

The initial setup is pretty straightforward. 

I would rate my experience with the initial setup a seven out of ten, with one being complex and ten being easy. 

For the most part, the deployment takes a couple of days to install.

Around four people were involved in the deployment process. 

The ROI was not in monetary terms, but it has certainly improved usability and added extensive reporting within our internal toolset.

So, it saves time and improves efficiency.

 The suite itself is expensive due to the licensing model.

Overall, I would rate the pricing model a seven out of ten, with one being the cheapest and ten being the most expensive.

The decision should be made based on your usage of other Microsoft suite products. I would rate it an eight out of ten because of its feature set and its compatibility with other Microsoft BI toolsets.

In this solution, the cost should be reduced for the enterprise edition. Customers are looking for high availability for applications, but due to the high license cost, they may not agree. Microsoft should consider and think about the cost and licensing for the enterprise edition.

I have been working with this solution for a few weeks, I have worked on this. I was assigned to a project to work on it, and I got some tasks related to deployment and insertions. So, it was just useful for that.

I've been actively using SQL Server Reporting Services for the past year. I have worked with Microsoft SQL Server versions 2012, 2014, 2016, and 2019.

It is a stable solution. We don't use it daily. 

It is a highly scalable solution. We have around 3 to 5 end users for a single instance on-prem. 

I'm very satisfied with the service. And usually, whenever we have any issue or details, we get to the person for the support. I'm really satisfied with the service. Within a few minutes or within a few hours, the support person will be available. 

Positive

It's very friendly to use and also cost-optimized. It's easy to understand whatever we want to do, and it's also cost-effective and very user-friendly that this tool is as compared to Oracle and other databases.

I would rate my experience with the initial setup a nine out of ten, where one is difficult, and ten is easy.

It took around when we were migrating one of our databases from on-prem to Azure. It took around the database size of around 650GB, and it took around three to four days to completely migrate it from on-prem.

We migrated from SQL Server 2016 to Azure SQL Database. 

The deployment time varies depending on the complexity of the changes involved. If the changes are minor, the deployment can be done quickly. However, if the changes are more significant, testing and confirmation from the customer are required before proceeding with the deployment.

Overall, I would rate the solution a seven out of ten. 

We use the solution mainly for the KPIs and dashboards.

I mainly use the solution for the ease of reporting and for executive dashboards.

I'm starting to use Power BI this year, and it would be really nice to have better integration between the solution and Power BI.

I have been using Microsoft SQL Server Reporting Services since 2015.

Microsoft SQL Server Reporting Services is a stable solution.

I rate the solution an eight out of ten for stability.

Microsoft's support is not generally good, but I haven't had to deal with it. I would only use Microsoft support for the licensing part, which is very complex for SQL Server.

Negative

When I was relatively new to it, the solution's initial setup was complex for me. On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a three or four out of ten.

According to me, the solution's pricing is very expensive, but I don't know how much Oracle or other competitors would cost. Since I am unfamiliar with other pricing schemes, the solution's pricing may be fair. Getting the type of license we bought was very complicated. Value-wise, the solution's pricing is good for the price that we pay. I rate the solution a seven out of ten for the value we received from the solution's pricing.

The solution's data visualization capabilities have helped enhance our reporting and made my life easier. I don't have to deal with third-party software.

The solution's integration with other tools and systems has proved to be a time-saver. The solution's integration saved me a few weeks out of a year on a lot of analytics. I would recommend the solution to other users.

Overall, I rate the solution a seven out of ten.

In one particular case, we had reporting issues and we were sucking data off of a couple of different systems into a data monitor. You might call it a data rig now. Due to the fact that we did that, we were using the transformation pieces to pull it into that data monitoring, and put out some operational-type reports.

The fun part about it was because we could do a lot with it and it didn't need necessarily another layer reports. It was pretty much encapsulated well already. 

The solution's features are all just wrapped up in one nice easy package. I don't need a lot of toolsets to get everything I need done.

It's not a difficult solution to figure out.

It doesn't have quite the flexibility of a Tableau or something like that. Many users are more comfortable with Tableau and I'm not quite sure why that is right now, but it seems to be the case.

The visualization needs improvement. They're lacking. Once again, Tableau is better in this respect. Basically taking the data and visualizing it onto the different types of reports and stuff like that needs to get better.

I've been using the solution for the last twelve years or so.

On-premises, I've never had stability issues with its exception of the original versions. It's safe to say the solution is quite stable at this point. For me, at least, it's been stable. I don't think I have a problem with it in that sense. It doesn't crash or freeze and I can't say it's buggy or glitchy.

The solution doesn't scale horizontally. 

From a vertical scalability standpoint, it's fine. It depends on the same issues that all relational databases do. Even if you set it up for reporting, etc. However, from a horizontal scaling, it really wasn't the way that it was designed. At the end of the day, I don't really know. I haven't used it for scaling purposes personally and don't even know if it's capable of scaling horizontally.

We probably only have about 100 users on the solution. It's not a lot. We just use it for a financial app.

Typically, if a company has bad consultants, they need to contact technical support a lot. However, we have a very good understanding of the product, so that's not usually necessary.

We've previously used a lot of different products, including Oracle OBIEE and Oracle Business Intelligence Discoverer. Discover is quite old. Most people wouldn't even know what it is. 

The initial setup question is a tricky one to answer. It depends on what you call easy. Some implemented well, and it was due to the fact that we put it in a monitor because the data didn't join well and we had some bigger data management issues. Some people would call that complex, and yet, it's pretty normal as to why you put something into a monitor.

On a smaller deployment, it was probably a couple of months of work. The process was probably only 200 man-hours to get what we needed out of it. It wasn't a huge deal.

The solution doesn't need too much maintenance. It would've just been something that once it was done, the normal staff just go ahead and do the maintenance. That's after the ETL programs are built, and so on. Maintenance is not a big deal. We can pretty much figure everything out. 

We compare a few different solutions. Tableau is usually easier for users to get behind as it's a bit simpler to use. It has good visualization.

I'm not sure which version of the solution we are currently using. We've updated it a few times over the years.

I'd advise other users to just to be really clear on what you're trying to accomplish. You've got to make sure it's the right product for what you're trying to do.

I'd rate the solution seven out of ten.

The use case depends on the requirements of the system or applications. Organizations and individuals may use the product for different purposes ranging from small-scale applications to enterprise-level systems.

The solution is known for its robust security features. It is an excellent product. It is a widely used database management system.

The product should improve its performance. It should improve the optimization, encryption and access control. It should provide efficient resource management features.

I am currently using the solution.

The solution is stable. I rate the stability a ten out of ten.

I had a good experience with technical support.

The initial setup is easy.

The solution is expensive.

I would recommend the solution to others. Overall, I rate the product a ten out of ten.

Microsoft SQL Server Reporting Services needs to improve performance.

I have been using the product for six to seven years. 

Microsoft SQL Server Reporting Services is stable. 

The solution is scalable. My company has 25 users for the product. 

We get good support from Microsoft. 

The tool's deployment complexity is medium. 

Microsoft SQL Server Reporting Services can be deployed in-house. 

The tool's licensing costs are expensive. 

I rate Microsoft SQL Server Reporting Services an eight out of ten. 

We use the product to build reports based on customer requirements. It also helps us to export documents to different formats like Excel, CSV, and Word document and share it through emails or FTP. 

I am impressed with the product's seamless integration. It can work with different databases like Oracle. 

I would like the solution to add a scheduling feature for reports. 

I have been using the solution for 10-15 years. 

I would rate the product's stability an eight out of ten. 

I am not sure about the tool's scalability since we haven't tried deploying it on multiple servers. 

Microsoft's support is good. 

Positive

I would rate the product's setup a seven out of ten. The tool's deployment takes a couple of days to complete. Microsoft provides installation media when you purchase the license. You need to do a verification after the deployment and configuration. 

The solution is cheaper than its alternatives. 

I would rate the solution a seven out of ten. You need to use the solution if your technology stack is Microsoft and the backend database is an SQL server. 

We use this product to store all of the bank's data.

The SQL Server Reporting Services makes it very easy to get the data whenever we need it.

We are also using it as a manual data quality tool, where we can write the queries and then generate reports based on the data that we have.

The interface is intuitive.

Technical support is in minor need of improvement so that they can solve problems in a more timely manner. Some of them take too long to solve.

I have been using this product for approximately eight years.

Although we had issues with stability, they were network-related issues and had nothing to do with the product itself.

Scalability-wise, it is good. There are more than 50 people currently using it in my organization. Their roles are from the director down to the analyst level.

Technical support is excellent and I would rate them a nine out of ten.

My only complaint about the technical support is that sometimes, they don't solve the problem immediately.

I have been using this solution since the beginning and we did not switch.

The initial setup was straightforward.

The price is pretty good.

Next year, we will be completely moving to the cloud in Azure where we will be building data factories.

My advice to anybody who is implementing this product is to consider that it is straightforward to use, and given that it is Microsoft, they can move to the cloud at any time with Azure.

For me, I have never had any trouble using this product. 

Overall, we are very much satisfied with this product. I find it user-friendly and there are minimum outages. We did have problems related to our network but as an application, it's excellent. Our only complaint is that technical support wasn't always able to help us right away.

I would rate this solution an eight out of ten.