SQL

And so there's no requirement for them to...

They don't have to know SQL.

They don't have to know Python.

They don't have to know command line interfaces.

Expect the unexpected.

if your incident response plan requires tuning and adjusting, something happened in the planning process because realistically, we should always be thinking differently and expecting things that no one else is thinking about when you think the origins of SQL injects.

Well, who would have thought that code or input fields are supposed to do something different than what they normally do? It's just something that you have to, it's a muscle that we have, know what you don't know.

All right.

It's a foundation model, right? So it's going to understand most probably any language.

I would say, you know, SQL like queries, SQL queries would be a good place to start.

I'm sure it could read Python or just plain language it right.

Hey, there's there, you know, this database is in here.

are.

Focused primarily on SQL Server and performance, but lately I've been flirting with a database called Mongo.

Wow.

Yeah.

How come? We've seen a pretty big resurgence of Mongo.

Really? And kind of the NoSQL elements of that have become very interesting to our customers for rapid application development, being able to iterate fast and change an application without kind of the rigidness that a relational database might have.

Is that an AI-driven thing or other factors? That's

what all the marketing folks tell us, yes.

Fabric data warehouse integration with fabric user data functions.

So what this is simply allowing us to do is we can extend T-SQL Python logic.

We can create T-SQL external functions that map to Python functions hosted in Fabric user data functions.

We can call them from familiar SQL statements such as select, insert, update, and the execution is delegated automatically.

When that external function is invoked, the data warehouse passes the execution to the user data function and returns the result in SQL.

So different scenarios that this enables.

This is some of the examples that Microsoft has.

Yeah.

Data analysts have traditionally lived behind dashboards, reports, and SQL queries.

But in an AI-powered world where technical skills are becoming increasingly democratized, the biggest competitive advantage may no longer be building insights, it may be influencing decisions.

Today's guest believes the future of analytics isn't in the back office.

I knew how to make some ifs and Excel equations do something for me.

But I didn't do it because I wanted to understand cash versus accrual, X lookup versus V lookup versus whatever formulas are out there.

At the end of the day, I was a nerd when it came to Excel and then SQL, then Python, then dbt, because those were just the tools I had at the moment, because I was trying to tell the C levels and the VP levels, hey, I see something as a numbers nerd.

We need to change how we operate as an organization.

And I can't just tell you because you've been in the business 10, 20, 30 years.

The purpose of this, and you'll see this query here and what this query looks like.

If you don't know SQL, don't worry.

We'll get into that in a second.

But the query essentially is what is going to determine who is in the audience.

And one of the things that we're going to do here is we're going to create a new query.

And the reason that we're going to create this new query is because we want to create our own individual query as well for Q4.

And that's where generate with SQL comes in.

Now, one of or with the AI comes in.

In other words, do we use, just I'm going to use Salesforce as an example.

Do we use SQL queries? Do we use some sort of like export or extraction of the data? That comes from Salesforce through some other delivery method.

We use some go-between tool.

We use an ETL tool or something like that.

when not necessarily with this version, but with earlier iterations, the Google Sheet one, the Salesforce reports, all of that, we did find issues, like I said, and we had to dig into why.

Sometimes it was the process of how we ran the query.

We're like, oh, sure, the SQL query is not quite the same as the Salesforce report because of this thing or that thing.

And sometimes it was the data itself, which you wouldn't necessarily find if you're comparing one set of results against another.

77.

SQL's 50-Year Reign Here's why SQL is still relevant today dive into the detailed history of SQL's rise and reign over the past 50 years.

THEY REMAINED RELEVANT BY LISTENING AND ADAPTING TO THE MARKET.

78.