In a previous posting, I showed you how to create a Vendor listing report using SSDT and SSRS. This was a handy report, but it showed all of the data in the tables and you could not search on specific criteria. This week I am going to show you how to create a parameterized version of the report so you can search by area code or really any part of the phone number.
In a previous article I demonstrated how to create a SSRS report that runs against a SSAS Cube. This time I am going to show you how to create a report with a query that you already have created.
Last time I showed how to create a connection to an Oracle database by creating a Linked Server in SQL Server. Most of the time this works fine, but when you are pulling a lot of information, it tends to run slow. By using OPENQUERY, the query will run very, very fast.
Last week I attended SQL Saturday. In last years posting: SQLSaturday #595 Cleveland 2017 I explained all of the benefits and all of the great FREE training and networking that you can do. This year I will give you a rundown of the sessions I attended in 2018.
Sometimes you need to pull data from an Oracle database into your SQL Server database. No magic is required, you just need to use a Linked Server. This article will show you how easy it is.
In a previous posting we created our first SSRS report pulling from our SSAS cube data. It ran fine, but it brought back all of the data in the database. This posting will show you how to add a parameter so only selected information is brought back. You may think of this like a WHERE clause in your SQL statements.
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.