>> There's many things coming up for Azure Data Studio.
With me today I have Erin and
we'll learn all about that right now.
[MUSIC]
>> Hi Erin.
>> Hello, how are you?
>> Good. Now that we know a little bit more about
the identity of Azure Data Studio.
Where do you go now?
Can you tell us a little bit more about that?
>> A roadmap for what's coming?
>> Yeah.
>> Well, we're starting with focusing on just some fundamental.
A lot of feedback that we've gotten is related to
stability of Azure Data Studio consistency.
We're addressing a lot of things behind the scenes
that users may not see when they open up Azure Data Studio,
but there is a lot of work that's going on.
For example, within Azure Data Studio,
right now one of the things that we're focusing on
is the connection dialog.
The connection dialog changed in the December release,
we added some dialogue
related to encryption and server certificate.
Those used to be in a hidden Window,
we brought them more to the front.
That's one thing that has changed and we're continuing to improve
that connection experience because one thing that we've heard
from users a lot is that, they're not stable.
We recognize that,
we've been working on that.
There are changes in the January release that
again are not necessarily visible,
but are being done behind the scenes to improve that stability.
There's also some troubleshooting that we're
looking to bring in to Azure Data Studio,
so that when folks do encounter connection issues,
they're going to be able to understand what's going on with
a little less struggle on their side, a little bit easier.
Those are things related to that area.
We're also focusing on Object Explorer or OE.
For folks who are familiar with this tree view,
you've seen this before in all tools.
How do we navigate into what databases we have available to us?
This is another area where folks have had some challenges.
Again, we're working behind the scenes on that.
We are also introducing some more options.
We really want Azure Data Studio to
be an operational tool that folks
can use for their most basic activity.
We had recently introduced table designer.
When you go into the database and
you expand and you select a new table,
you now have the ability to create a table through the UI.
Previously you could only do this with T-SQL.
This makes creating objects for folks who are new to Azure,
who are new to SQL a little bit
easier because this can be done through the UI.
This was. Step 1.
We're continuing that where we're going to go into
security to make it easier for folks to add users.
Right now all we have is a refresh.
It would be really nice if you could go ahead and
create a new user in a UI,
just like you can in other tools.
We're working on adding that as well
for one of our future releases.
>> That will be nice. I've seen right now in the table it creates.
Like I see the script in the bottom.
Does it mean that, I create the table
using the UI and it gives me the script,
so I could keep that.
>> Exactly.
>> That's great.
>> Even as I add another column here,
you can see that script down at
the bottom gets updated immediately.
From here, I could just copy this script out,
with a Control C and paste that into a new Window and run it.
I have an icon up here.
I'll zoom in, so you can see this icon right here,
which will publish those changes for
me and just push those out automatically.
Sometimes when you're working in
a database is just easier to deploy that.
But for those of us who have worked with T-SQL for awhile,
we want to be able to have that script
or if we're trying to learn T-SQL,
we have that much more available now.
>> Yeah, so it's a perfect tool to get started now.
Like I could use this and say, I don't want to do this.
And when you see the script and
understand, oh, that's great, I love it.
>> Exactly.
>> That's great.
>> We will be doing that also for
creating users right under security.
One of the other big feedback items that we have
is the ability to filter within tables.
For example, right now
we can create a new table and we can refresh,
but there's no ability to filter it
down by a schema or by some amount of tech,
so we're going to be adding that in as well.
>> Great.
>> Yeah. We've heard that a lot from users.
Then the other thing that I want to make sure that folks are aware
of is GitHub repo for Azure Data Studio.
This code is available, so folks can contribute and make
changes and then those pull requests
get evaluated by the engineers,
but what most people are probably a little bit more
interested in is the issues list that we have.
These are open issues that we have and
we have the ability to sort obviously over here,
which ones newest, oldest most commented.
If I would sort by most commented,
we can see this issue that I mentioned, this query hangs.
That's an issue that we're actively working on.
Again, something behind the scenes
that will look like something new,
but improves the overall stability.
But different feature requests that folks have.
You can look at through
here and if there's something that you're like,
yes, this is definitely something I want to see.
Folks can go in and they can make a comment,
they can vote on that or if you
don't see something and you want to add a request,
you can go ahead and create a new request in here.
What we are really doing is looking at
these issues and requests
and using those to define where we are going next.
My request to folks who are
using Azure Data Studio is please share what you
want us to see and please look to see what
other requests are there and then up vote them,
provide comments to help us understand your use case,
because that gives us a better understanding of where
we need to continue to move with Azure Data Studio.
>> I love it. It's right in GitHub available,
the link will be provided.
It's all there. Now we know
what's coming up and we can help, we can participate.
>> Exactly.
>> To the future. I love it.
>> Yeah. Thank you.
>> Thank you for sharing all of that with us today.
>> No problem.
>> Looking forward to learn more about your project.
>> Thanks for having me.
[MUSIC]