Look at the columns you filter and join on. Try indexing those and compare the statistics of your queries before and after...

try
- indexing the fields you're filtering on.
- limiting the columns returned
- add RAM, like to 32GB. 8GB for SQL Server is just painful.

Others may disagree, but I don't know why you would store an instance of a non-event. It's going to make your fact table much larger than it could be. And...

Can't you do something like FILTER() on the DimCourse table to get just the courses you want, then use CROSSJOIN, which creates a Cartesian Product?
https://docs.microsoft.com/en-us/dax/crossjoin-function-dax

You can nest queries if you want... not that big a deal.

SELECT x.Field1, x.Field2
FROM (SELECT a.Field1, a.Field2
             FROM MyTable a
  ...

use a tally/numbers table and DATEADD. Maybe I should add a link to Jeff Moden's article on Tally tables.

December 10, 2018 at 6:52 pm

#2015954

Rod,
did you ever get this figured out?

Not bad for a beginner!  I should ask you what you tried first. (It helps if you post that too, because people are more likely to help you if you...

Since you have a bunch of GETDATE()'s... why not just stuff that value into a variable, and then just compare to that?

DECLARE @CompareDate DATE =...

The whole point of doing the delete in batches is that it doesn't increase the size of the log.

or am I missing something?

As for processing a...

How about this? (Thanks for the data, but if can provide CREATE TABLE scripts, you'll get better answers, because people can just copy & paste to create your setup.

When you set up the connection to your data source, did you specify Oracle as your source? Looks like SSRS is expecting you to be connecting to a different data...

Is your backend Oracle? That looks like PL/SQL, not T-SQL.