question

radu_bak avatar image
radu_bak asked

Is SSAS still a viable solution? (with SQL Server 2016 and up)

I have an instance of SQL Server 2016 installed and I have built some reports on it for transactions, sales totals, grouped by month, accounts etc.

I created stored procedures which stores this information in a few reporting tables where I get my data from.

I've had a few contradictory discussions with colleagues about choosing to store this data in SSAS. I worked with SSAS a few years ago on a pre-existing solution, but even though I found the concept interesting, I always preferred the OLTP part of SQL Server.

I solved my problem "in my own way" and personally I've found indexing solutions within the transactional database that meet my needs for reporting, by using combinations of columnstore and rowstore indexes. However, people around me try to keep pushing for SSAS, the only argument being "it's where you should keep your reporting data!".

Since I haven't had any great experience with SSAS, I'm asking more knowledgeable people if there's a case for actually having your reporting data in SSAS and when is the best time for that? Or is it all the time?

Thanks in advance for reading my question and hopefully answering!

ssas
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.