In previous postings we have created a data warehouse, created a SSAS cube, now we are going to write a report using SQL Server Reporting Services to create a report against the cube data that we created.
In the last article, we connected Excel to our SSAS Cube, and did some pivot table analysis. Now we are going to increase our analysis ability by adding a date dimension so the data can be further broken down.
Last week we created a cube using SSAS. Now I am going to show you how your end users will connect to it using Excel and how they can use the data in a meaningful way while using their favorite tool (Excel).
Today we are going to create a very simple SSAS cube to show some of the useful things that you can do with Sql Server Analysis Services. In production or a real world scenario, you would do much more planning and analysis, but this article will show you the steps that you will need to complete. This is really the tip of the iceberg of things that you can accomplish with SSAS, so feel free to explore.
You just finished your SSIS project where you needed to load a CSV file into a Sql Server database table, but now you just found out that multiple files with the same data will now need to be loaded. Using the Foreach Loop Container in SSIS makes this relatively easy.
Here is an issue you may receive if you try to import data from an Excel spreadsheet into a Sql Server database table:
Error at Data Flow Task [OLE DB Destination ]: Columns “firstname” and “FirstName” cannot convert between unicode and non-unicode string data types.
Many times you do not initially install SSAS when you build your Sql Server instance. This posting will show you how to install. There will be future articles concerning Tabular Models and the cool things you can do with them.