WEBVTT

00:00:00.000 --> 00:00:02.445
>> Bob Ward wrote a new book called

00:00:02.445 --> 00:00:04.620
SQL Server Revealed and he's here to

00:00:04.620 --> 00:00:06.990
tell us all about it
today on Data Exposed.

00:00:06.990 --> 00:00:17.700
[MUSIC]

00:00:17.700 --> 00:00:20.640
>> Hi, and welcome to another
episode of Data Exposed.

00:00:20.640 --> 00:00:22.560
I'm your host, Jeroen,
and today we have

00:00:22.560 --> 00:00:25.695
a very special guest
SQL royalty, Bob Ward.

00:00:25.695 --> 00:00:26.805
>> SQL royalty, I don't know.

00:00:26.805 --> 00:00:28.440
I'm not sure if I heard
that one before but yeah,

00:00:28.440 --> 00:00:29.790
thanks, Jeroen. Great to be here.

00:00:29.790 --> 00:00:32.130
>> Yeah. So rumor is
you wrote another book.

00:00:32.130 --> 00:00:34.170
I know you had a book
on SQL Server on Linux.

00:00:34.170 --> 00:00:35.910
I read it, I have it.

00:00:35.910 --> 00:00:37.905
It's signed by you even,
thank you for that.

00:00:37.905 --> 00:00:38.865
>> You're welcome.

00:00:38.865 --> 00:00:41.475
>> So the rumor is on the
street, there's another one.

00:00:41.475 --> 00:00:43.390
>> There is another one.
Can you believe that.

00:00:43.390 --> 00:00:45.690
You'd think after the
abuse of writing one,

00:00:45.690 --> 00:00:47.780
you wouldn't do
another one but I did.

00:00:47.780 --> 00:00:49.220
I wrote the first one,

00:00:49.220 --> 00:00:51.800
it was a hard project.
I enjoyed doing it.

00:00:51.800 --> 00:00:53.750
It was a labor of love, and I got

00:00:53.750 --> 00:00:55.760
done and I told my wife and my boys,

00:00:55.760 --> 00:00:56.810
I'm like, "I'm not doing any more of

00:00:56.810 --> 00:00:57.860
these. They're so hard to do."

00:00:57.860 --> 00:00:58.545
>> All right.

00:00:58.545 --> 00:01:00.470
>> I don't know, I just got
the itch to do another one.

00:01:00.470 --> 00:01:02.030
>> So a couple of years
later you're back at it?

00:01:02.030 --> 00:01:03.805
>> Actually, a back-to-back.

00:01:03.805 --> 00:01:05.720
I wrote the Linux one
and that came out

00:01:05.720 --> 00:01:08.360
last year and almost like
a month or two later,

00:01:08.360 --> 00:01:09.380
I'm starting the next one.

00:01:09.380 --> 00:01:11.930
>> So you said to yourself,
and to your wife,

00:01:11.930 --> 00:01:13.580
and your family, "I'm never going to

00:01:13.580 --> 00:01:15.380
do this again." The next
morning you start again.

00:01:15.380 --> 00:01:17.345
>> The next morning I
start cranking it out.

00:01:17.345 --> 00:01:19.250
There's this product, you
may have heard of it,

00:01:19.250 --> 00:01:22.385
called SQL Server 2019.
Never heard of this, right?

00:01:22.385 --> 00:01:22.705
>> No.

00:01:22.705 --> 00:01:26.300
>> So we have just announced
that at Ignite last year,

00:01:26.300 --> 00:01:28.130
and that's when the book
Linux had come out.

00:01:28.130 --> 00:01:29.315
It was then, around that time.

00:01:29.315 --> 00:01:29.705
>> Yeah.

00:01:29.705 --> 00:01:31.195
>> So I thought to myself,

00:01:31.195 --> 00:01:32.990
"I wonder if I should
write a book about 19."

00:01:32.990 --> 00:01:34.640
It's lot of work I've been doing over

00:01:34.640 --> 00:01:36.680
the last year, and
that was the journey.

00:01:36.680 --> 00:01:40.390
So the book is called SQL
Server 2019 Revealed.

00:01:40.390 --> 00:01:42.660
Reveal, is that a cool name?

00:01:42.660 --> 00:01:43.680
>> That is a very cool name.

00:01:43.680 --> 00:01:45.945
As a matter of fact, I
tried searching for it.

00:01:45.945 --> 00:01:47.775
>> Oh, you tried.You found it.

00:01:47.775 --> 00:01:48.420
>> Is this it?

00:01:48.420 --> 00:01:50.640
>> That is it, yes.

00:01:50.640 --> 00:01:51.750
That is the book, I know.

00:01:51.750 --> 00:01:53.925
It's a catchy name, I realize.

00:01:53.925 --> 00:01:57.510
I think the word reveal just
means behind the scenes.

00:01:57.510 --> 00:01:58.035
>> Okay.

00:01:58.035 --> 00:02:00.080
>> Because, Jeroen, one of the
things that was fun doing this

00:02:00.080 --> 00:02:02.495
as I interviewed a lot of
people in the engineering team.

00:02:02.495 --> 00:02:04.130
This book is really written for

00:02:04.130 --> 00:02:06.500
the SQL community but it's
powered by the engineering team.

00:02:06.500 --> 00:02:09.290
So what you have here is a series
of chapters that are really

00:02:09.290 --> 00:02:12.905
stories about
functionality in SQL 19,

00:02:12.905 --> 00:02:14.270
about the engineering team.

00:02:14.270 --> 00:02:16.370
So for example, I might
have a feature on

00:02:16.370 --> 00:02:17.450
performance and I would talk to

00:02:17.450 --> 00:02:19.130
Pedro Lopes about
what the work he did,

00:02:19.130 --> 00:02:21.740
and why did you do it,
and when did it start.

00:02:21.740 --> 00:02:23.915
I like history a little bit.

00:02:23.915 --> 00:02:24.200
>> Okay.

00:02:24.200 --> 00:02:26.195
>> So I spent the first
chapter talking to

00:02:26.195 --> 00:02:28.640
Slava Oaks and Travis Wright
about how did this all start,

00:02:28.640 --> 00:02:30.530
why did you-all start this madness.

00:02:30.530 --> 00:02:32.870
So there's some fun
stories in there as well.

00:02:32.870 --> 00:02:33.335
>> Cool.

00:02:33.335 --> 00:02:34.460
>> It's very conversational, I'm

00:02:34.460 --> 00:02:36.785
a conversational person,
and you'll find that.

00:02:36.785 --> 00:02:38.740
But it's also got a lot
of demos and examples.

00:02:38.740 --> 00:02:42.485
Almost every chapter has examples
on GitHub for you to read,

00:02:42.485 --> 00:02:43.760
try it out, read,

00:02:43.760 --> 00:02:45.290
try it out, all sorts of things.

00:02:45.290 --> 00:02:46.880
>> Good balance
between understanding,

00:02:46.880 --> 00:02:49.250
what's going on, why did we
do this, how did we did it.

00:02:49.250 --> 00:02:49.745
>> Correct.

00:02:49.745 --> 00:02:50.495
>> Who did it?

00:02:50.495 --> 00:02:50.780
>> Yeah.

00:02:50.780 --> 00:02:52.970
>> Right? Highlighting those
people as well and then learning

00:02:52.970 --> 00:02:55.730
about how it works and
doing it to yourself.

00:02:55.730 --> 00:02:59.595
So Big Data Clusters,
did it make it in?

00:02:59.595 --> 00:03:00.780
>> Big Data Clusters made it

00:03:00.780 --> 00:03:02.370
in and I did a really
unique approach there.

00:03:02.370 --> 00:03:04.670
Big Data Clusters is one of the
biggest things we did in 19.

00:03:04.670 --> 00:03:05.000
>> Sure.

00:03:05.000 --> 00:03:07.460
>> But what I chose to do is put
that at the end of the book.

00:03:07.460 --> 00:03:08.760
There's a couple reasons why.

00:03:08.760 --> 00:03:10.280
One is I'm writing the book

00:03:10.280 --> 00:03:12.230
during the preview of
SQL Server, right?

00:03:12.230 --> 00:03:12.650
>> Okay.

00:03:12.650 --> 00:03:14.135
>> Big Data Clusters was really

00:03:14.135 --> 00:03:16.040
a big thing we did
during the release.

00:03:16.040 --> 00:03:17.600
So I want to make sure in the book,

00:03:17.600 --> 00:03:20.735
I got almost everything
about it that's up to date.

00:03:20.735 --> 00:03:22.040
So one of the cool
things I learned about

00:03:22.040 --> 00:03:23.540
this book is it literally

00:03:23.540 --> 00:03:26.480
does reflect everything that's
in the release of SQL Server 19,

00:03:26.480 --> 00:03:28.880
yet I was able to write
it during the preview.

00:03:28.880 --> 00:03:30.650
The other reason to put
Big Data Clusters at

00:03:30.650 --> 00:03:32.240
the end is that it encompasses

00:03:32.240 --> 00:03:35.870
what Containers, Linux,
Kubernetes, PolyBase,

00:03:35.870 --> 00:03:37.085
so what I do is, in the book,

00:03:37.085 --> 00:03:38.510
I teach you those concepts in

00:03:38.510 --> 00:03:41.180
the book and so then you
learn about those basics,

00:03:41.180 --> 00:03:43.580
and then you get the Big Data
Clusters, you get all that now.

00:03:43.580 --> 00:03:45.710
So you understand how to put
it all together in a solution.

00:03:45.710 --> 00:03:46.970
>> Okay. It's set up starting

00:03:46.970 --> 00:03:48.760
with the whole thing
in the beginning,

00:03:48.760 --> 00:03:50.550
and then decompose it,
you start building it.

00:03:50.550 --> 00:03:52.725
>> I build it up, and
it end with a bang.

00:03:52.725 --> 00:03:54.120
>> It's like a cliffhanger, maybe.

00:03:54.120 --> 00:03:55.650
>> A little bit of a cliff,
yeah. I can't think that

00:03:55.650 --> 00:03:57.345
someone looking at it. That's right.

00:03:57.345 --> 00:03:58.110
>> The end of the last phase.

00:03:58.110 --> 00:03:58.935
>> Absolutely.

00:03:58.935 --> 00:04:00.495
>> Aren't there any dirty secrets?

00:04:00.495 --> 00:04:03.225
>> No, there's nothing like that.

00:04:03.225 --> 00:04:04.290
>> But it's reveal, right?

00:04:04.290 --> 00:04:05.780
>> It's reveal but there
are some fun stories of

00:04:05.780 --> 00:04:08.400
behind the scenes of
why we did something,

00:04:09.020 --> 00:04:11.250
always encrypted, let's
pick on that one.

00:04:11.250 --> 00:04:14.130
It's a security model we
have and then encryption.

00:04:14.130 --> 00:04:15.360
Well I went back to the team and

00:04:15.360 --> 00:04:16.560
said, "Where did this start from?"

00:04:16.560 --> 00:04:18.180
As it turns out, I'm
starting Microsoft research.

00:04:18.180 --> 00:04:19.940
I don't think anybody
knows that and I got

00:04:19.940 --> 00:04:22.040
a chance to interview the
Microsoft researcher.

00:04:22.040 --> 00:04:22.460
>> Cool.

00:04:22.460 --> 00:04:23.540
>> You pick on Polybase,

00:04:23.540 --> 00:04:25.230
I went back and
e-mailed David DeWitt,

00:04:25.230 --> 00:04:26.560
one of the original founders of this,

00:04:26.560 --> 00:04:29.275
and I found him at MIT and I
said, "Why did you do this?"

00:04:29.275 --> 00:04:31.015
So I put that stuff in the book.

00:04:31.015 --> 00:04:33.305
That's like the nuggets I
think people enjoy reading.

00:04:33.305 --> 00:04:35.840
I did that on Linux and
I did in this book too.

00:04:35.840 --> 00:04:37.550
>> Wow. So this is going to

00:04:37.550 --> 00:04:39.675
be in time for the
holidays, hopefully?

00:04:39.675 --> 00:04:42.180
>> It's in pre-order right now as we

00:04:42.180 --> 00:04:45.405
speak and I hope to have
this thing out soon,

00:04:45.405 --> 00:04:47.805
very, very soon, definitely
before the holidays.

00:04:47.805 --> 00:04:49.500
Usually, they come form

00:04:49.500 --> 00:04:52.230
an e-books earlier than
the printed versions.

00:04:52.230 --> 00:04:54.840
Like the Linux book,
it's fairly long.

00:04:54.840 --> 00:04:57.225
I think it's almost like 500 pages.

00:04:57.225 --> 00:04:58.875
>> The Linux book was pretty.

00:04:58.875 --> 00:05:01.200
>> It was pretty thick.
Now this book by the way,

00:05:01.200 --> 00:05:03.935
Jeroen, is everything
that's new in 19.

00:05:03.935 --> 00:05:06.290
You need some fundamental
knowledge of SQL, I think,

00:05:06.290 --> 00:05:08.360
to pick it up but it is end-to-end.

00:05:08.360 --> 00:05:11.000
It covers everything in the release,

00:05:11.000 --> 00:05:14.000
from performance to
security to availability,

00:05:14.000 --> 00:05:15.530
the Linux, containers,
Big Data Clusters,

00:05:15.530 --> 00:05:16.880
you name it. I've
got it all in there.

00:05:16.880 --> 00:05:20.540
>> Because you mixed it with
stories and background,

00:05:20.540 --> 00:05:25.130
it doesn't feel to me
like I've not read it.

00:05:25.130 --> 00:05:27.710
>> Yes of course, yeah. I can't
wait for you to read it, though.

00:05:27.710 --> 00:05:29.660
>> Yeah. So it doesn't sound to me

00:05:29.660 --> 00:05:32.480
like a dry list of features,
like "Oh, we can do.

00:05:32.480 --> 00:05:33.995
We can do this, and
this is how you do it."

00:05:33.995 --> 00:05:35.630
Because you have this interaction

00:05:35.630 --> 00:05:37.705
with the people on
the interviews now.

00:05:37.705 --> 00:05:39.360
>> The other thing I did not mention,

00:05:39.360 --> 00:05:41.255
you might find it, is not
just listing features.

00:05:41.255 --> 00:05:43.550
I do it from a challenge
solution perspective.

00:05:43.550 --> 00:05:44.210
>> Okay.

00:05:44.210 --> 00:05:45.950
>> Okay, here's your challenge that

00:05:45.950 --> 00:05:47.750
you have today and here's why 19

00:05:47.750 --> 00:05:49.430
has things together to give you

00:05:49.430 --> 00:05:51.590
a solution, like
intelligent performance.

00:05:51.590 --> 00:05:53.825
You don't want to change your
app, you want to get faster.

00:05:53.825 --> 00:05:55.070
That's a challenge
you have or I don't

00:05:55.070 --> 00:05:56.360
want to do an expensive tuning,

00:05:56.360 --> 00:05:58.020
how does SQL 19 solve that?

00:05:58.020 --> 00:05:59.550
Then the cool thing is I'll put in

00:05:59.550 --> 00:06:01.640
maybe screenshots of how
it looks when you run

00:06:01.640 --> 00:06:05.870
it or give you an exercise to
confirm to put it all together.

00:06:05.870 --> 00:06:07.160
>> Awesome. So yeah,

00:06:07.160 --> 00:06:08.780
I cannot wait to get my hands on it.

00:06:08.780 --> 00:06:10.805
>> Thank you. It was
exciting to write.

00:06:10.805 --> 00:06:13.415
>> Yeah, I can see
that. So okay, cool.

00:06:13.415 --> 00:06:16.940
So everything that you need to
know about SQL Server 2019,

00:06:16.940 --> 00:06:18.440
the way it's built,

00:06:18.440 --> 00:06:19.520
the why it was built,

00:06:19.520 --> 00:06:20.825
by whom it was built,

00:06:20.825 --> 00:06:23.225
everything is in this one book

00:06:23.225 --> 00:06:25.310
called SQL Server
2019 Revealed. Right?

00:06:25.310 --> 00:06:27.205
>> Absolutely, Jeroen. Yeah.
I'm excited to see it come out.

00:06:27.205 --> 00:06:29.010
>> Perfect. So with that,

00:06:29.010 --> 00:06:30.615
thank you, Bob, for being here.

00:06:30.615 --> 00:06:31.200
>> Thanks for having me.

00:06:31.200 --> 00:06:34.250
>> It's exciting to have you
and thank you for watching.

00:06:34.250 --> 00:06:36.080
Please like and
subscribe to the video,

00:06:36.080 --> 00:06:39.870
comment, and hope to see
you next time. Thanks.