Michael Seim on 23 Aug 2024 17:34:49
There are so many limitations with DirectQuery that it has made my team revert back to Tableau for a use cases. I was about to write an idea to allow for all the prohibited techniques in DirectQuery to be made available (stored procedures, DROP, CTEs, etc.) but then I got to thinking in a different way.
The reality is that I can do everything I want to do via the IMPORT style data connection. It's SOOO close to everything I need. But it's not LIVE connected to the database. But here's the thing, I don't need a LIVE connection at all. Not really. I just want the data IMPORTED upon report-load and parameter-change.
So that's my idea... I would encourage consideration of adding a new Refresh Frequency option to IMPORT style semantec models of "Refresh upon load and parameter change".
If that were possible, ALL the limitations of a DirectQuery, at least for my situations, are solved. In case anyone is curious, I'm not suggesting this for anything large, not at all. I'm merely looking to run a "current status report" of a server state. In that situation you're talking about a few hundred or maybe a few thousand records being returned. The query/stored procedure takes mere seconds to run. The user experience would be just fine. And the data would be pulled as of the moment the report is loaded which is exactly what I'm really after.