>> Learn how to go from Nowt to query in 10 minutes or
less with Azure Arc enabled SQL Managed Instance,
this week on Data Exposed.
[MUSIC]
>> Hi, I'm Anna Hoffman and welcome to
this episode of Data Exposed MVP Edition.
Today I'm joined by Rob.
Rob, thanks so much for joining us today.
Can you kick us off by telling us a little bit about what you do?
>> Sure. Thank you so much for having me.
My name is Rob and I live in the UK.
These days, I basically help people make things.
I do a lot of work with bicep Creating Azure Infrastructure.
That's what I do for work.
Outside of that, I'm
a dual MVP and I love talking about new technology.
>> Awesome. That's what we're going to be talking about today.
We are going to be timing you out from Nowt to Query.
I got to pause right there and just ask you,
what does Nowt mean?
>> Nowt is a Northern UK word that means nothing.
If you say, do you have something? No, I have nowt.
>> Awesome. We're going to be talking about how to go
from nowt to query with Azure Arc,
enabled SQL Managed Instance.
This is something I haven't seen a lot of,
I'd love if you could just take us
through whatever it is that you want to show us.
>> Awesome. I'd love to do that.
We're going to start in our favorite data editing.
Azure Data Studio, I love
Azure Data Studio for those who don't know,
it's a cross-platform data, editing, administering solution.
Because I have the Azure Arc extension,
you can see down here that what I've got is
some Azure Arc controllers defined in my Azure Data Studio.
Some of them are up in the Cloud.
We're only going to work with Ben-Indirect.
This is a Kubernetes cluster that is running on my machine.
As you can see, it says no instances available.
If we right-click, we can then click on "Manage."
That's going to connect to our Data Controller and on our cluster.
We can go "New instance."
It's a good button to press,
all from within Azure Data Studio.
It gives us two choices,
Azure SQL Managed Instance or PostgreSQL Hyperscale.
I don't know much Postgres,
I'm going to pick an Azure SQL Managed Instance and hit "Select."
It says, okay, we just need to check some things.
Do you accept the Eula?
Well, yes, please. Thank you very much.
Then it makes sure that we have the required tools installed,
so kubectl and Azure CLI
and I click "Next" and it asks for some information.
Which Azure Arc controller are we going to
be putting this instance on and we'll give it a name.
I'm going to call it bw.
You can decide if it's Ben Viceman or Buck Woody, it's up to you.
We will have a admin username,
and then we will create
a password and I need to put this password a few times,
and it's really hard to do when you're talking.
But we'll put our password in and then you would say,
okay, how would you like your instance configured?
I'll have one replica and I'll pick my storage class.
Where would I like to put my storage?
Like asking your sign admin,
which LAN you're going to have for your SQL host.
Then we'll say how many cores,
we'll have a request of two and a limit of two.
This is only a little height of the box,
so we'll give it six gigs of RAM and a limit of six gigs.
Then we can click this "Deploy" button.
What that's going to do is, it's going to open up
a Jupiter notebook and
everything is going to be prefilled and as you can see,
it will automatically start running.
>> Cool.
>> It's awesome, isn't it? It's as quick as that.
We filled in a few boxes in the way we want.
If we look at our cluster,
we're going to use this tool called Lens, it's a free tool,
it's absolutely fantastic for working with Kubernetes clusters.
When we can see that here, bw-0
because there's only one replica, is starting,
and we've got three containers in our port,
and they're orange at the moment because they're being created.
Two of them have already been created.
>> Wow. This is cool.
I haven't seen any of this before.
It's very cool to see how easy it is
to click through and then have notebook.
>> It is super, super easy.
Whilst that's just spinning up,
what it's doing there is just bringing up
a SQL container and
making all connections through to our data controller.
Let's just have a very quick overview
of what Azure Arc enabled services are for really.
Because of this problem,
our data services are living everywhere.
They're in all sorts of various Clouds,
or they're in datacenters that
we control or third parties control.
We've got all these different types of SQL all over the place.
As I used to be a production DBA,
the problem with this is that when you come
to needing to manage one of those instances,
you're going to reach your hand into the toolbox and
hope you don't cut it and find the right tool for the job.
Where are all these instances,
how do I make sure that I can administer them?
Where are we monitoring them?
Where's our alerting coming from?
But with the Azure Arc enabled data services,
we can have evergreen SQL, so always up-to-date anywhere.
It doesn't matter, we don't mind where it lives.
We can use tools that we're comfortable with, Azure Data Studio,
for example, to create and administer our instances,
and we have a single pane of all of our instances in Azure portal.
It's super good, to really neat.
The thing that we already had because I said, Nowt.
Really it wasn't quite Nowt because we have the data controller.
The data controller is the thing that
enables us to create our instances,
and it also holds all of our dashboards and metrics built-in.
Because Azure Arc-enabled data services
comes with dashboards built-in,
comes with logs and our metrics all available,
and a lot of other services are done.
This is all controlled by our data controller.
I reckon though this means that,
well, look we've got three containers that are green,
so I think they're all good to go.
If we check our logs of our Data Controller,
we can see down at the bottom it says,
there we are, StatefulSet bw is healthy,
so I think we're good to go.
If we jump back in to Azure Data Studio,
we can see that this particular notebook is finished,
so we'll get rid of that.
We could save it to rerun it.
If we refresh our data controller,
it's going to show us that now we have an instance called bw.
When we click on that,
it's going to give me my endpoint.
This is going to be my SQL connection into my Managed Instance.
What I'm going to do is I'm going
to edit this connection and I put in
this new instance and once more with the password.
I have double-click, remember.
I'm going to just connect,
just like it was any other instance and we'll click "Connect",
and that's done a connection.
It's just a SQL instance.
Now I've got a notebook here just to show you,
let's make that a bit smaller and will connect to our instance,
let's hope it's that one.
Maybe it wasn't that one.
Let's try this one.
We're connected.
We're not connected.
See, I can't speak, I didn't write password.
I still have the connection string there,
so we can run our query.
What's our server called? What's our host called?
bw-0, isn't one replica.
Wonder what version it is. We see it
comes up as, if this would open for me.
It comes up as Microsoft Azure SQL Managed Instance,
Azure Arc edition 15.
You can see this is just looking like a SQL Instance.
We can run T-SQL against it,
we can create a database,
I've given a way who the bw is here.
We can see that our database is being created.
Now we can just create a table,
put some data into it.
Sure enough, 100,000 rows.
Ben says what's happening,
because he often says that.
In my reckoning that's probably
about 10 minutes and we've gone from nothing,
we had a data controller but don't tell anybody, to
a SQL Server 2019 managed instance,
created a database, put a table on it,
as quickly as that,
just using Azure Data Studio.
>> Wow, that's pretty amazing Rob,
this has been really cool for me to see,
and I'm sure for our viewers, folks,
who haven't seen this before or maybe
things have changed since they've seen it last.
Thanks so much for showing us this.
As we close out, do you have one piece of
advice for folks as they get started with this?
>> Getting started with managed instance
on Azure Arc-enabled data services
is go and look at the Jumpstart website.
The Jumpstart website has got a lot of the code there to
be able to run through and deal with all of this.
My second piece of advice is if you're
looking at Kubernetes is to use the tool
called Lens because it
makes fabulously easy to see and understand what's happening,
certainly helps me to learn a lot.
>> Cool. Well, thanks so much Rob. This has been really useful.
We'll put some links in
the description for our viewers to go learn more.
Thanks again Rob for coming on the show.
Thanks to our viewers for tuning in, if you like this episode,
go ahead and give it a like, comment
and let us know what you think of
it and we hope to see you next time on Data Exposed.
>> Thank you very much.
[MUSIC]