Tell your DBA to consider putting the staging tables into their own schema. I call mine "Temp", but "Staging" or "Landing" would be good names. This might remove...

More information is needed to see what you are doing. A picture of what you currently see would also be helpful.

If it helps get this done faster, I'm eager to read the article already. I didn't know what this could have meant, but reading the blog at the link...

I recommend a table that is then turned into a dimension. It will give you more flexibility to add/change things.

Also, a cardinal rule in data warehouse efficiency is to never join one fact table to another fact table. If you do, all bets are off for getting a response...

I don't think it's oversimplified at all. I think you got it.

I wonder how you even know you want to be a DBA if you don't know anything about it? I think most of us are accidental DBAs in the...

Presumably (although you say you want to normalise) you won't have any tables in any normal form, because that would requires primary key constraints that the database will enforce, which...

Trouble is that you appear to want an absolutist position that there's no business logic in the database, even if you have to redefine the term "business logic" to exclude...

It's not my intention to write a book...

I'm not exactly sure what the issue is as the drill through is of course supported in the Standard edition. Is the issue that the values on which they...

There is a role for triggers, but an anti-trigger bias isn't a bad thing.

You didn't answer my question: if you believe that business logic in the database is a bad thing, do you forbid it altogether and refuse to permit any normalisation to...

The application may be performing poorly, but it's not a chokepoint in the sense that the database is. ...

Well, then I'm glad. However, I didn't create that. As at...