Query folding doesn’t get a lot of press, but this unassuming functionality can dramatically improve Power BI performance. Visualizations or reports contain multiple queries that need to be processed and can tax your computational power. If your queries are complex and you’re running dashboards off a laptop, for example, things can bog down when query steps get handled locally instead of back at the data source.
Also called query delegation or predicate push-down, query folding is a way to maximize limited resources by generating a single statement to retrieve and transform source data. The goal of folding is to offload as much of the query heavy lifting and processing back to the source database. It helps you to best optimize what gets sent back to the data source and can also dramatically reduce what is imported into Power Query and processed locally. By understanding the steps of your query, you can make changes that will improve Power BI performance. The best part of query folding is it is built-in and ready for you to use!
See a demo on query folding. We go behind the scenes on how Power Query looks at your data. Along with an overview on query evaluation and folding, you’ll learn how to:
- Know what sources can achieve folding
- Determine when a query can be folded
- Understand the icons and indicators of what steps in your queries can be folded
- Leverage Query Plan to see what’s happening with your queries behind the scenes
Trainer and Consultant
Pat is one of our most popular instructors, regularly receiving high marks from students for their subject matter knowledge, clarity of communication and ability to infuse fun into classwork. Pat has over 20 years of experience in data science, business intelligence and data analytics and is fluent across multiple BI platforms. They are a Tableau Certified Associate and well versed in Power BI. An expert in Cognos, their product experience goes back to version 6. Pat has extensive experience in Actuate, Hyperion and Business Objects and certifications in Java, Python, C++, Microsoft SQL.Read more
Welcome to another Senturus webinar. Welcome to the final webinar of 2022. Oh! my goodness. And just some unrelated news, it will only be interesting to a few of you, this is our last GoToWebinar webinar. Starting in 2023, all of our webinars will be on Zoom. So Yeah, this is it. This is the last webinar of the year, the last GoToWebinar. Oh, my goodness gracious, but Penny, I know you’ll keep calm until all of them.
I see you out there, Penny, I see a lot of you that just come, because you want to hear me talk. I know how it is.
All right, everybody, today, we’re talking about query folding. We’re going to get our laundry on and a different kind of folding.
Click on the GoToWebinar arrow to see the whole control panel.
And here, you can submit questions. I’m paying attention to that question pane, the whole gosh, hack darn time we’re talking.
So please, send us questions. If for some reason we don’t get to your question, we will cover it, hopefully, at the end of the Q and A section, because maybe you’ll ask me a question, I don’t know, It actually happens.
If for some reason we don’t have time to get to it, or we can’t find the answer soon enough, we will have a written response document that is posted on Senturus.com.
And, of course, the next question that you’re all going to post, How do I get a copy of the presentation? Well, guess what?
We put that on our website. And if you pay attention to the chat window, look at that. I just gave you a link to it.
The other one will come in handy later, though you’ll be seeing that other URL later. So, click on the other URL and bookmark it just so you have it for later too.
The deck is available on Senturus.com, you want to go to the resources tab and then the Knowledge Center, or click on the link I just posted.
But the website, there’s all sorts of fun stuff.
A website, if you can’t tell, it is near the end of the year, I am just in a mood. I am just getting to that. We’re almost all to that last week of the year. Our agenda today, I will introduce myself.
We’re going to talk about query folding.
We’re going to talk about what can and cannot be folded.
How to tell if something has been folded using the indicators and the query plan and looking at all sorts of fun stuff. And of course, I’m going to demo all of this And then you’re going to stick around and you’re going to listen to me do all the marketing stuff where I go over the Senturus overview and additional resources.
Because after that, we’ll do the Q&A.
I’ve got to make, you listen to the other stuff, it’s part of the job, whether you like it or not.
So, who is this wonderful, weird person talking to you? Why it’s me, data scientists, consultant trainer.
My title is going to change in 2023, So you have to come to the next webinar to see my new title, as of 2023, because it’s almost here.
This will be my 26th year of data science, data warehousing, data analytics, whatever term digital you wish to call it.
My goodness, I’ve been doing it longer than some of you have been on this planet.
OK, Penny. I don’t want to be a VP, because then they’ll make me have to carry a budget, and then I’ll have to worry about money, and I don’t want to worry about money.
That’s no fun.
I just want to teach you all. I use Power BI, Tableau, Cognos, Hyperion. Actually, whatever two tool you can think of, in these last 20 something years, I’ve used them, I’m certified in Java, C++, SQL Server, etcetera, etcetera, That’s me.
We’re going to start with why.
Why are you here today? Why do you care about query folding? Why are you listening to me, ramble on.
It comes down to wanting to have better performance, wanting to have optimal queries, wanting to make happy users, know, those people that drive us nuts all the time, but that we have to keep around and make happy. So whether it’s when they load up reports, or when they open dashboards or whether they work with apps.
We want things to get on the screen faster.
We want things to show up better.
And what we’re going to talk about is how query folding gets you to that goal.
It is an important part of your data modeling.
Hey, it is an important part of things.
And especially when we look at our different types of table modes, whether they’re important versus direct versus hybrid, folding will improve the performance of these things.
Direct is one of those things.
Where, if you’re using direct queries, because you’ve got huge, huge data sources, anything you can do to fold, anything you can do to improve this is going to help now, before anybody asks.
Well, how much of an improvement might I get off of this?
Because it’s going to depend on so many different factors, it’s going to depend upon the size of the table, the complexity of the transformations.
There’s so many different things.
When we say there’s an improvement in performance, it’s relative to all those other things.
How big, how many, How much.
Any performance improvement is always welcome.
So if it’s five milliseconds faster, that’s still an improvement.
If it’s 30sec faster, that’s a direct correlation. And result that your users can see, and your users will be happier, which means you get your end of your bonus, which means you can go to Hawaii next year, and your spouse will stop getting on you about finally taking them away.
Hey, right, Right, Andrew.
You’re going to Hawaii next year.
Query folding is simply put is Power BI pushing as much back to the data source as possible versus processing this locally.
It’s the ability for Power Query to generate a single, simple query statement and push that statement back in native functions.
All right, pushing it back in native functions, that allows the source to do the processing.
Here’s the beauty.
All of this is built in.
There’s literally nothing you have to turn on. You don’t have to go check anything. You don’t have to start digging through menus. This is built-in functionality.
And it’s taking this built-in functionality.
It’s looking at the M that is generated by Power Query.
And it’s attempting to fold it.
And the folding occurs when we use native functions and things along those lines.
And this becomes important when you’re using Power Query to do your data transformations.
When you are using Power Query, two, remove columns, filter down rows, merge columns, our goal is to make sure that we’re using transformations.
That can get translated into native, sequel of our data source.
We’re talking about, how do I build my transformations more efficiently so that the query that gets created can be converted to a native script and handled by the data source versus being processed locally within Power Query?
There’s your summarization of what query folding is.
Just some quick definitions, just so we know what we’re talking about here.
Again, it’s the process of taking all these queries, taking all of these M scripts, pushing them back to the data source.
There are certain things that can and cannot happen in Power Query.
Any of you who’ve used Power Query, you’re aware that there are certain transformations that cannot be done, because you can’t affect a live table.
So there are certain things that you have to have import tables for, and import tables or tables that are loaded into memory.
And there are different transformations, different DAX functions, different M functions, that can be done against import tables versus direct query tables. Direct query tables are tables that are loaded from the source. Now, think about that for a second.
If there’s a transformation that I’m trying to do, that is not a native SQL function, it’s got to read that query, perform that function locally, return the results.
Folding helps get rid of that overhead.
Then we start thinking and talking about things like incremental refreshes, OK, incremental refreshes are efficient in terms of utilization, duration and things like that.
But when you do an incremental refresh, you’ll get a warning if it determines that something can’t be folded.
So you’re going to see all this, so don’t, don’t stress out, you’re going to see all this today.
But if you’re doing incremental refreshes and the incremental refresh doesn’t go back to the source data, then in some ways, the goal of an incremental refresh is defeated.
Because the mashup engine would then have to get all of the source roes figure out what filters and transformations then determine the incremental changes, etcetera, OK.
All right. There’s like 60 of you here. Like 45% of you are paying attention.
Hopefully, if there’s anything so far, I’ve said, that’s confusing. You. Let’s get those questions asked.
Let’s make sure we’re all doing swell.
I will not lose anybody. This is not necessarily an easy topic to understand.
It is a pretty technical topic.
So thank you to those of you who responded Penny and Danielle and Rosario. Thank you.
Now, when we fold, folding may occur for an entire set of steps.
So, Dennis’, excellent question, Dennis asked, if query folding can be applied to files, import it from SharePoint.
It’s a matter of the M script, Dennis, it’s a matter of what the M script is sending back.
If the M script is using certain functions, it will fold them.
And that’s what you’re going to see when we start looking at, how do you tell if something is folded or not.
So, there are things that are built into this whole world, there are certain functions that will absolutely, always fold.
There are other things that will never fold OK, Dennis.
So you’ll see, you’ll be able to tell, did this fold or not?
Is this a native function or not?
And what we might see is we might see that at query is partially folded or fully folded.
When it’s partially folded, then the engine has to compensate by doing the transformations itself.
So you’re striving to fold as much as possible. Now, what am I talking about? What, what is this query that I’m talking about?
Here’s what we’re talking about, the M queries that you would see inside of Power Query.
So, when we use Git data, and we load data in, we’re automatically using access data functions, all right?
And these are functions that you would see in the M that connect to our source in the native language. So, Dennis, to your question, there are data functions for SharePoint. There are data functions for Excel. There are data functions for SQL.
So those data functions, those get data, functions are in the native language, and they fault.
And basically, what you see here is a select statement.
SQL.database, that’s our function schema, that’s our Get Data function.
So, these are all native functions that are going to fold.
It’s the transformations that we do that we’ve got to watch out for it.
How do you know what data functions you’re going to use?
There is an entire list of them now, I already put that into the chat window. That was the first one that I pushed out there.
So, let me show you this too
Here’s the full list.
Access Data Functions and this was updated as of October 10th.
So you can see Adobe Analytics, Azure, Cubes, Exchange Folder Contacts, Oh, Data Feeds, Salesforce, and, hey, Dennis.
There you go, SharePoint.contents, SharePoint.files, SharePoint.tables.
So these functions, we’ll absolutely fold.
SQL Database, Sybase, Teradata, etcetera.
These are data functions. These are functions that are folding.
These are functions that are handled at the source.
All right, it’s anything after that that we’re concerned about. It’s anything after that that we want to pay attention to.
Because what we’re going to see after these data functions is 1 of 3 outputs.
We’re either going to see full folding. And that’s where every transformation we’ve done has been able to be translated back into a native query command. And everything is happening back at the data source.
This will use the minimal amount of the Power Query engine.
And this is our goal.
More realistically, we’re going to get partial query folding.
This is where a few of our transformations can get pushed back. Some, however, have to take place in the Power Query engine.
These are the ones we want to watch out for.
These are the ones we want to look at. And these are the ones where we want to ask ourselves.
Is there an alternate native command that I could use instead? And that’s what I’m going to show you in the demo today, is, hey, here’s how I normally would do this. Oh, look, this doesn’t unfold, What could I use instead?
The more that we can do of that, the better off we’re going to be.
Then, we have an no query folding situation.
If we’ve got a situation where nothing is folded?
If we’ve got a situation where nothing is folded, here’s where we want to start thinking. Maybe I should push this all back. Maybe I should be doing some of this amazing ETL.
Maybe I should be doing some of this somewhere else.
Maybe this is something that I need to do in a different tool.
Maybe I want to do this upstream if my, if my transformations are so complex that I’m getting no query falling ever, they cannot translate this at all to the native.
Now, this is usually because the transformations aren’t supported, or the connector isn’t supported.
So, Nelsen, to your question, snowflakes shouldn’t.
So, you’re talking snowflake, the technology, not necessarily snowflake, as in a database. Snowflake, I’m going to assume.
This could be a potentially, yeah, that’s what I figured.
So, this could be a potential situation where the connector doesn’t support fold it, OK, and off the top of my head, I don’t have an answer. I don’t know if a Snowflake connector will support folding or not.
But, that is exactly what we’re talking about here. Yeah.
You would find it on that page that I that I posted a second ago as terms of what data functions are supported.
OK, I believe that there is a list.
If I can find you, a list on the query folding stuff from MS where there is a list of connectors.
Yeah, I’m going to, So I’ll put that I’ll put a link to that in before we, before we finish up today, OK?
But that is exactly what I’m talking about when you get a no query folding, most of the cases it’s because the connector doesn’t support it.
All right, Now, there are some transformations that I’ll always fold.
When you’re in Power Query, these will always fall. We’ve got Paul Lynde in the Center square. I mean, we’ve got expansion to achieve joins, You know, the hard part about getting old?
Very few people get that joke anymore.
No, they don’t remember the Center Square.
I could say Whoopi Goldberg and the Center Square that at least covers a few more of you people.
Paul, in the Center Square, but thank you, Andrew. Somebody’s laughing at my bad jokes. This is the last one of the year gang.
This is where I can pull out my entire year’s worth of material.
No, it’s Thursday, I never quite get the hang of Thursdays.
Everybody knows that these will always fold.
These are things that are always safe to do in Power Query.
Getting rid of columns, renaming columns, non fuzzy merging, you should not have issues any relational data source.
They can have a single select statement, where we’re using things like, where’s group by? Join.
Any of these, So, filter uses a where clause grouping in summarizing uses a group by expanding columns uses and join, Non fuzzy uses a joy, a union all when we’re putting together foldable queries on the same source. Ah, what was that I just said?
Oh, hmm, ding!
If I am using the same source, and I’m doing things like a union all, if I’m doing things like simple logic in a custom column from the same source, like order date, I can use an order date function.
There’s a Power Query date.year.
For example, pivoted and pivot, as long as I’m using the same source for everything, these things will fold.
So what kind of data sources are we talking about?
Oh, data feeds like SharePoint, Exchange, Active Directory.
These functions, these sources.
What doesn’t fold?
Flat files, CSVs, things like that blobs web sources if you’re using blobs to source your Power BI reports Yes.
I’d be a little worried if you’re using blobs or globs.
Flat files web sources. Hey, I can see how you might be using those.
Just need to be careful with them.
We need to see how much is getting folded, how much transformation we’re really doing. What’s the performance impact, etcetera, etcetera. See, here’s the thing. Again, I can’t give you, oh, it’s 42%, or it’s this, or that.
These are those types where you really want someone like us to help you, to work through it, to walk through, to do a true assessment, to help you figure out, Hey, how do we get better performance? Hey, what can we do at the source? You’ve got blobs.
Vivian just asked if there’s any code that takes an SQL files from SharePoint, but the data is from the same Oracle database.
I would wager that that should fold just fine Vivian, because here, we’re still using standard relational database with SharePoint, get data functions, functions that shouldn’t cause a problem with the folding engine.
However, here’s things that will prevent you from folding.
If I’m trying to do merged queries from different sources if I’m trying to do unions’ from different sources.
Or if I’m trying to do complex logic, like date, dot to text, date dot to text does not fold, because there’s no equivalent function in the source.
At the end of the day, what this is going to ask you to do this, this is going to ask you to really be familiar with the language of your source database.
For example, there are different functions in SQL versus Oracle, one of which I’m going to show you in the demo.
It doesn’t exist in SQL, but it does exist in Oracle.
So, knowing that helps you figure out when you go to do a transformation. So, for all these questions that are coming in, I want to be very clear.
Normally, the JIT data functions have no problems, It’s the transformations that we do on the data, and it’s the transformations that were questioning and saying: Should I be doing this upstream? Should I be putting index columns upstream in the source?
Should I have a better ETL process that’s loading this into a proper data warehouse, or data lake, and pulling it from there after it’s been cleansed in a more efficient tool?
Or is there a Native SQL function that I can use that will make things better?
All right, how do we tell?
OK, here’s another old people joke, Know when to fold them?
Because using Power Query Editor, we’re going to know what we’re going to see is when we look at the steps, when we look at the steps, if we see this.
Yeah, If we see this View native query, then that means this is being folded.
If this is grayed out, then the query cannot that step or a step before.
It cannot be folded, OK?
This does not show up for all connector type style, going back to nelsons question.
If you don’t see this, then it could be 1 of 2 things.
It could be that the connector doesn’t support this, or the query can be folded If I’m all the way up here at the top and I’m not seeing view Native query at my first step, then that’s probably an issue with the connector.
If I’m down here at renamed columns and I’m not seeing it, then one of my ladder steps is not being folded, and I would just keep working backwards until I see this option not grayed out.
Benjamin, to your question, would there ever be a situation where you wouldn’t want to fold?
I can’t think of one off the top of my head, because again this is built-in functionality.
This isn’t something you really have control over unless you intentionally chose functions that couldn’t be folded.
But uh I can’t really think of a situation where you wouldn’t want it to be faster where you wouldn’t want to use his native language as possible. The real question Benjamin, is how much of an impact is my transformation Causey?
Is this causing me a 32nd delay when somebody loads of a dashboard? Where is this causing me a 10 millisecond delay when somebody loads up a dashboard?
That’s what we’re talking about. That’s what we’re looking at.
Is this transformation simple enough that it can be done in Power BI, that I don’t have to spend hours trying to figure out if it could be translated to a native query?
That’s what we want to look at.
Now, there are query diagnostics.
And you can use the query diagnostics to see non SQL connectors.
All right, You aren’t going to see the same level of detail.
But you will at least be able to see if it’s folded.
Vivian says: I don’t have any control over the DW tables. Are there alternatives to adding an Index? That’s where you’re going to have to look up the language for, the data source you’re using.
And you’re going to have to look, is there a native function, And there might not be, if there’s no native function, we’re going to have to see what the impact is happening here in the Power Query Engine.
All right. We know when to fold them.
So again, if the option is grayed out, not all steps can be folded.
However, some can be folded and we’re going to use that option to see where the sequence stops.
Or, and we’ve got indicators.
Yeah, There are step diagnostic indicators.
These indicators will tell us if something is folding, not folding, might fold, opaque, unknown, the indicators are non sequential, the indicators are going to help us see what’s happening.
When we look at a step, there’ll be an indicator if it doesn’t unfold. If everything folds, we’re just going to see this first one at the top.
If something suddenly says, Nope, not full.
Then, we’re going to see this might be 10 steps down, which means that everything up to that step has folded.
The might fall, the opaque and the unknown are much less common.
These indicators are only likely to appear if you’re doing ODBC or data connections.
What it means is, hey, this might fold. I won’t be sure until runtime.
Opaque, it’s inconclusive for some reason.
Maybe there’s a true constant table. Maybe the connector isn’t supported.
Nelson, this is one you might see an Opaque or an unknown.
Here I might see an unknown if I’m coming against something that is a record, a List, a primitive.
These are the ones that are going to tell you, if you’ve got something that’s a non supported connector, the two primary ones that the majority of you are going to see folding, not fold it.
When we see these, we want to look at the query plan.
The query plan is going to show us, what steps are folding.
The query plan is going to show us what’s going on. And we’re going to look at those indicators. We’re going to look at the query plan that’s being generated. And we’re going to determine if there are steps that we can implement to change this.
What we’re going to see is this, and we’re going to see the actual sequel we’re going to see what is the SQL being generated.
Here is an example of where everything is folded.
Every single one of these is folded, and we’re go to view details. We would see the SQL that’s getting sent and we would see the native language, and we would see that this is the optimized translation of RM query.
So we’re going to see this.
And with that, let’s see it.
Let’s do it. Let’s do this altogether here.
OK, so what I’m going to do, Because I’m coming here to my power apps.
And I’m going to create.
A new Dataflow.
Create a brand new data flow.
I already have one that I was working on for this for this webinar. So no, I’m not going to use this one. I’m going to use a new Dataflow.
They’re taught by webinar Dataflow.
Look at all of these things I can connect to.
Somebody gave me a new and an aha, Pretend like this is exciting, no, you don’t want my feedback.
Somebody pretended like this is exciting now.
Nelson, Snowflake is listed, OK.
Snowflake is listed as a data source.
It’s not say it’s all necessarily going to fold.
But it’s out there, which gives me high hopes that the get data functions, we’ll fold.
It gives me high ups.
I’ve got, I’ve going to have high hopes.
Thank you, Rosario and Andrew, by the way, you each get a cookie.
Let’s go to SQL Server database.
You’re a friend of mine, Adventure Works.
We all love our adventure works.
I’m going to log in, I use my super secret password here.
And there’s all my tables.
My God, things actually worked, So I’m going to pick a few tables just to make things good. I’m just going to grab a couple of things here.
Header or details, salesperson’s, region.
Sounds good to me. Let’s go to transform data.
Here’s what I did.
Look, there’s that little indicator. Oh, I forgot to start that up.
Look, there’s my little indicator right there.
Here’s what I’m going to do.
I’m actually going to create a new blank query.
I’m going to write them myself, Copy, paste, Suck.
I’m sane, Go to this database, go to this schema.
Give me this table.
Only give me these columns, and filter the rows to where the total do let me zoom in on this, so you can see it better.
Where the total due is greater than one thousand.
And I want the bottom five.
So I’m doing a keep bottom rows.
And I’m saying, give me the bottom five rows.
As you can see, I should not have gone into art.
So I’m writing my own query here, basically, and don’t be an idiot, Actually change this to the right connection.
Thursday, at the end of the year, people give me a break. I?
So I just created this new query.
These are my bottom five rows. These are my bottom five order dates.
These are only where the total due is over a thousand dollars.
And look at that, this step right here.
Right there, not folding.
This means that the kept bottom rows step is done in the query engine and not at my source.
Everything else up to there is cool.
That first indicator is telling me, Hey, you’re good.
You’re good, everythings folding.
But when I get to this step, it’s not folding.
Now, before I go on any further, some of you may be saying, hey, I’ve never seen those indicators before. Or, hey, I’ve never seen that pop out before.
Option’s global options, turn these on.
These two right here.
Enable query folding indicators, Show script, instep call out.
That probably just answered some future questions right there. Hey, I’ve ever seen those, going to turn them on. That is the only thing you have to turn on when it comes to query folding.
The functionality is built it. See, that requires you to turn those two things on.
So that gives me this indicator.
And it gives me the script fly out.
So when I hover over each of these, I see what it’s actually doing.
I see exactly what it’s doing.
So that bottom row step, not folding. And if I right click it.
Oh, no, it is grayed out.
Oh darn, what do I do?
But if I go up one step, Oh, look, View Data, source query, not grayed out.
So I know that everything up to there, everything up to there is folded.
So, Rosario, you have to enable those indicators, OK?
You have to enable those indicators.
Options, global options.
Enable query folding indicators.
No, So the code, this is what I was expecting. The questions these indicators are in Power Query online.
The indicators show up in Power Query online, not in Power BI Desktop.
The functionality is still there.
The indicators and the view data source query is still there, the indicator. That’s why I went where I went, gang.
That’s why I went where I went.
So if I look at the query plan for this step.
So I right clicked, and I looked at the query plan.
Here’s where I see that last one is causing my problem.
Notice, there’s no view details on here.
I can see the details for my first two steps.
Oh, look, select From where.
That’s everything up to that kept the bottom rows.
The kept bottom rows is doing a full scan. And that full scan is happening in the Power Query mashup engine.
If this was something that was going to impact our performance, if this is something that was going to impact our performance, maybe instead we want to do something different.
So I’m going to come back in here, and I’m going to delete this step.
OK, I do let I select, I selected, I deleted my kept rows step. Now, my whole query is folded.
But I still only want to see the last five, OK?
So here’s what I’m going to do.
I’m going to take my Sales Order ID, and I’m going to sort it descended.
Oh, look at that.
I’ve got a sorted step.
Still fall then, Sort is a native command. No problem.
Now, what I can do?
I can take this You can take this right here, Keep top rows, and I’m going to say keep the top five rows.
Those are the same exact results I had when I did a capped bottom row.
Those are the exact same steps, our results.
But look at my query now.
OK, I’m now folding.
And when I look at this, and I look at that first off, oh, look, It’s not grayed out.
I’ve got an order buy, and I’ve got, on top, top is a Native SQL function.
Top goes back to the native source.
This is handled by my source, not via my query engine.
How nifty is that gang pretend like that is nifty? You all know how hard it is to make these things exciting, gosh, darn it, heck.
Thank you, Penny. Thank you, Vivian!
Here’s what I was talking about earlier.
If any of you are on Oracle, did you know that Oracle has a bottom function?
So if this was the Oracle instead of sequel, my bottom would have actually folded?
Ah, yeah, Oracle has a bottom function, SQL does not, SQL has a top function.
So when I change it to kept top Rows.
And now I say, show me the native query.
Show me the query plan.
And it’s all being done in a single select statement.
I don’t have six different steps anymore.
I have to get data. Can it make a connection?
So here’s my make a connection step.
Here is my single select statement.
That’s what we’re trying to get to gain.
Native query, single select, pushing it all back to the source.
And all it meant all I had to do.
All I had to do in this case was replace the cap to bottom with a sort cap top, ta da.
How do you know which ones know your source?
Know what functions. It’s time to pull out your dust off your old SQL for smarties book.
Ed, For those of you who’ve never read SQL for smarties, Joe Saulteaux is the author of that.
That’s one of those great books that’s been around for decades, that’s the kind of thing where we’re talking about, you need to know, oh, my sources, Oracle, Oracle has a bottom function that’ll fold.
Remember, sometimes, there may not be a native equivalent.
That’s when we have to look at and go, what’s the performance impact?
Is this such a complex calculation, that it’s going to cost me 30sec when somebody loads this report up?
When somebody goes to access this dataset, is that 30sec going to give me an unhappy end user?
Should I do this calculation back in the source, in my ETL?
If I’m being perfectly honest and realistic in this dataset, given the size of this dataset, would that kept bottom rows impacted any of my end users? No, probably not.
It’s a millisecond difference.
But that’s this dataset.
And that’s this function.
So Patty, is that a native function?
If so, the answer should be yes. Penny asked if the or Oracle list ag function. As long as it’s a native function, it should fold.
Because again, let me ask. Let me ask the question this way. Patty, let me ask you a question.
Could I, in Toad write a select statement that uses the list ague function and get back the results?
Then it should fold.
That’s what we’re shooting for.
Could I put this in a select statement?
It should fall with no problem.
If you can put in a select, we’re good.
All right, to know, they always are worried that I’m going to finish too early or too late. But look at this. It’s 252.
I know what I’m dealing with kids.
To summarize, it’s built-in functionality.
It helps us examine and understand and optimize our queries.
It’s going to give us overall performance improvements, and it should be used whenever possible.
Take a look at the query plan. Take a look at the indicators, take a look at these things.
Thank you, Patty. We’ll see you later.
You know, maybe in 2023, I’ll actually turn on my webcam.
Leverage the indicators, leverage what’s going on, use it, and, as always, talk to us, talk to us.
We can help you reduce the total cost of ownership.
We can help you with the report sharing strategies. We can help make sure you’ve got the right tools.
We can help you get all this into an Azure data lake or anything else, heck. Heck, we can help with your fin ops in your reservations. That’s right. We can do it all. Gosh, darn it. And, where can you find all this stuff? You can provide hundreds of free resources on our website.
We have been committed to sharing our expertise for, ever, over a decade on the website.
OK, go to Senturus.com/resources, you’re going to find all sorts of product demos, upcoming events. Kitty, I am not ignoring your question. Let me get through this stuff and I will answer it.
Our upcoming events, for those of you who are still Cognos people: What’s new in Cognos? 11.2.4? I’ll be in January.
Then, January 26th.
I’m back at it. I’m going to be doing a dashboard comparison. I’m not doing the 19th. I’m doing the 26th. On the 26 by Comparing Dashboards.
We’ll have an info on our website next week for you to register.
If your mind is otherwise worried about the holidays coming up, hey, don’t worry about it, we’ll get you an e-mail.
I will e-mail you.
Andrew. Thank you very much.
It is a difficult topic to explain.
So hearing that you called it the best explanation really makes me happy. Thank you.
Hey, a little background on us. For those of you who are new to Senturus, we concentrate on BI modernizations and migrations across the entire stack.
We can do power BI, Cognos Tableaux, Python, Azure proprietary software for bimodal BI.
Migrations, we shine in hybrid environments.
If you are moving from one to another, if you’re trying to make decisions about what to do, this is what we’ve been doing.
We’ve been doing it for 21 years, 1300 plus clients, 3000 projects. Our team is big enough to meet all of your needs, yet, small enough to give you a personal attention. As you’ve seen today, I know each and every one of these folks I’ve been talking to, I’ve worked with them for years. Hey, that’s what we give you a Senturus, as this personalized attention.
We call you out in the webinars, because, gosh, Gali, it’s fun.
If you would like to be part of this Madcap team, we’re looking for a managing consultant and a Microsoft BI consultant.
Go to send Senturus.com why some Senturus careers, or Send you.
Send us your resume, jobs. It’s in Senturus.com.
Also, our fin ops consultant, we’ve got a cloud cost management practice.
Come be part of.our new FInOps team.
Also, take a look in the chat window again. Our managing director, Scott Felten, put in a nice little calendar link.
We can talk to you about query folding. We can talk to you about optimization. We can talk to you about performance. Look at that chat Window Kids.
OK, it’s right there. There’s a link.
Scott’s calendar is always open.. Scott has no life.
We’ve told Scott to get a life, doesn’t listen.
Q and A time.
I think there’s only one question I’m missing out on and that is yours Kitty.
Question on blob, we use Synapse to inject data as parquet files into a data lake. my gut instinct in my natural reaction KT is that is not going to default.
I don’t have 100% answer on that, but based on what I know of what can and can’t fold, I’m going to say that’s not going to fold.
So that may be something that you want to, we can help you with, that something that, but the question is, if it’s in a data lake, see OK now.
If it’s in a data lake and I can send a select statement to the data lake and I can use a standard native select statement yeah It’s going to depend on that connector.
It really is that is honest to God kitty. That’s the kind of thing that I would say hey let us walk through it with you.
Let us help you figure that out and see what the select statements generated.
Because I’m really try to figure out if you could send it a select statement, it should fold.
Hey, if there’s anything else you want to know, send it to [email protected], we’ll set up a free consultation.
There we go. Merry Christmas, Kwanzaa CA, wherever you celebrate, whatever you want, happy holidays, Mary, whatever. Ladies and gentlemen, we are done.
Get the heck out of here.
Have a wonderful, remaining 2022. I will see you again in January 2023. Thank you all very, very much for giving me your time today.
I hope you all had fun. I hope you all enjoyed yourself.
As the last slide says, thank you.
Thank you all. Good. I’m glad that demo made sense to everybody.