Microsoft SQL Server Reporting Services Reviews

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. 

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.

We use the solution to create dashboards and important reports for project management. 

We can create quality reports in real time. 

I like the tool's usability. 

We have had issues with the refresh interval since we have too many reports scheduled. Microsoft SQL Server Reporting Services is also expensive. 

I have been using the solution for more than five years. 

I would rate the solution a nine out of ten. 

I would rate Microsoft SQL Server Reporting Services' scalability a seven out of ten. 

I did not have good experience with Microsoft SQL Server Reporting Services' support at times. 

Negative

I would rate the product a seven 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 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.