►
From YouTube: Introduction to SQL Server on RHEL and Open Shift
Description
Hear from Prinicpal Program Manager at Microsoft, Travis Wright in this breakout session at Red Hat Summit 2017.
The next version of Microsoft SQL Server is coming to Linux and is already in preview. In this session, Program Managers from Microsoft will provide an introduction to SQL Server and how it runs on RHEL and Open Shift. For those that are not already familiar with SQL Server, a brief overview will be provided describing the capabilities and specifically what will be available on Linux. Deployment, configuration, high availability, storage, and performance/scale will be topics for a more technical drill in.
https://www.redhat.com/en/summit/2017/agenda/sessions
A
All
right
well
welcome
everyone
to
the
introduction
to
sequel
server
on
rel
&
OpenShift
session
I'm
Travis
Wright
I'm,
one
of
the
program
managers
on
the
sequel,
server
engineering
team
at
Microsoft
and
I'm
happy
to
be
here
at
Red,
Hat
summit
I
actually
came
to
red
hat
summit
last
year.
Great
event
was
the
first
time
that
we'd
sort
of
demoed
sequel
server
unreal
publicly
last
year
at
Red
Hat
summit
and
a
lots
happened
in
a
year.
We've
made
some
great
progress.
A
I'm
really
excited
to
be
able
to
demonstrate
to
you
guys
today
the
progress
we've
made
towards
getting
sequel
server
available
on
Linux,
so
I
thought
we'd
just
start
with
kind
of
a
quick
introduction
to
sequel
server.
I
know
not
everybody
from
the
Linux
world
is
familiar
with
sequel
server
since
well,
you
guys
haven't
had
it
for
all
these
years
right,
so
I
thought
we
just
kind
of
give
a
quick
overview
of
sequel
server.
What
the
value
prop
of
it
is
and
then
I'll
just
spend
the
rest
of
the
time.
A
Just
doing
demos
we'll
just
kind
of
walk
through
some
things
feel
free
to
ask
some
questions
as
we
go
along
the
way.
Is
it
going
to
be
an
action-packed
session,
because
we
only
have
45
minutes
normally
I
spend
like
an
hour
and
15
minutes
just
doing
an
intro.
So
I'll
put
a
lot
some
good
times
here.
So
let's
see
how
it
goes.
So,
let's
just
kind
of
dive
right
in
on
now.
A
If
you
kind
of
take
a
look
at
what's
happening
in
the
world
today,
a
lot
of
the
things
that
are
round
it's
like
whether
it's
the
stars
or
the
microorganisms
in
our
planet
or
biology.
All
these
things
are
being
sort
of
encapsulated
as
data
points
now,
and
it's
really
interesting
to
see
all
the
different
technology
technological
advancements
that
are
happening
because
of
our
ability
to
capture
data
and
reason
over
it.
A
It's
it's
just
amazing
to
be
able
to
think
about
sort
of
the
expansion
of
the
capacity
of
humans,
given
sequel
server
to
now
also
be
available
on
Linux
right.
So
I'm
excited
to
see,
what's
going
to
happen
with
this,
so
let's
kind
of
dive
right
in
here
sequel,
Server
2016
was
released
last
year
about
this
time,
and
so
the
donnaught
sequel
server
2016
for
the
last
couple
of
years
has
been
rated
by
Gartner
as
the
B
leader
in
the
database,
Magic
Quadrant
for
the
relational
database,
Magic
Quadrant,
and
not
only
that.
A
But
it's
also
the
only
database
that
is
in
the
leader
Quadrant
for
all
three
of
the
database,
related
Gartner
m
queues.
So
that's
the
our
DBMS,
where
we're
a
leader
and
the
BI
at
Magic
Quadrant
and
the
analytics
magic
wand
room.
So
a
couple
other
kind
of
interesting
points
about
this:
the
National
Institute
of
Standards
and
Technology.
They
have
the
really
fun
job
of
like
keeping
track
of
all
the
vulnerabilities
that
happen
out
there.
So
you
can
sort
of
envision
these
guys
sitting
there
and
every
time
they
hear
about
a
vulnerability.
A
They
like
write
a
one
on
the
chalkboard
right.
Super
super
fun,
job,
okay,
but
these
guys
keep
track
of
vulnerabilities
in
sequel
server.
For
the
last
seven
years,
it's
had
the
fewest
number
of
vulnerabilities
out
of
all
of
the
commercial
database
and
even
open
source
databases
in
the
market.
Today,
it's
also
the
highest
performing
data
warehouse,
so
we
publish
benchmarks
to
TPC,
it's
the
the
fastest.
We
hold
the
number
one
two
and
three
benchmarks
for
data
warehouse.
A
There's
just
one
license
everything
from
the
relational
database
to
BI
to
analysis,
services,
integration,
services,
they're
all
just
included,
there's
no
extra
cost
for
things
like
in-memory
OLTP,
it's
just
built
in
now.
We
also
have
done
something
interesting
recently
with
the
sequel,
server
2016
release
where
we've
acquired
a
company
called
revolution
analytics
they
are
experts
in
the
field
of
R
and
you
doing
analytics,
and
we
built
that
right
into
sequel
server,
and
we
just
announced
that
integral
server
2017
we're
expanding
this
notion
by
adding
Python
support
to
sequel
server.
A
So
you
can
run
our
scripts
or
Python
scripts
directly
inside
of
your
T
sequel,
queries
inside
a
sequel
server.
So
what
this
really
means
is
that
we
combine
the
best
of
your
traditional
database
type
workloads
as
well
as
analytics
into
one
database
engine
right.
So
it's
all
just
there
in
the
Box
ready
to
go,
and
this
type
of
solution
is
powering
some
interesting
things.
We
just
talked
about
right,
so
the
Sloan
Digital
Sky
Survey
is
out
there
in
its
scanning
universe
and
cataloging
all
the
stars
that
are
available.
It's
terabytes
and
terabytes
of
data.
A
You
know
stars
just
used
to
be
like
pretty
things
in
the
sky,
but
now
we
can
actually
codify
those
stars
and
everything
about
them
into
a
database
and
that's
driven
by
sequel.
Server,
sequel
server
is
being
used
to
do
cancer
research,
it's
being
used
to
increase
crop
yield,
so
there's
really
an
infinite
possibility
of
what
you
can
do
with
the
database.
That
HAP
offers
you
the
ability
to
store
any
type
of
data
using
any
programming
language,
and
it's
just
all
right
there.
Built-In
now
in
general,
businesses
are
embracing
choice.
A
There's
in
the
insert
this
modern
technology
world,
there's
just
a
diversity
of
technology
and
there's
more
and
more
every
day,
and
it
used
to
be
that
we
tried
to
think
of
things
like
you
know:
let's
we
have
a
Microsoft
stack
and
we
have
an
open
source
stack.
Well,
it's
not
like
that
anymore.
Really,
right!
A
There's
no
Microsoft
stack
anymore,
because
Microsoft
is
embracing
this
idea
of
choice
and
giving
customers
the
option
to
choose
whatever
technology
doesn't
make
sense
for
them,
and
so
now
there's
just
a
collection
of
different
technology,
and
you
can
pick
and
choose
whatever
makes
the
most
sense
for
you,
based
on
factors
like
cost
or
your
expertise
or
the
particular
technology,
and
so
on
and
Microsoft
is
all
about
enabling
that
type
of
choice
we
want
to.
Let
you
choose
to
program
in
any
language.
A
You
want
with
sequel
server,
so
we've
been
improving
the
drivers
for
every
programming
language
out
there.
We
want
to
be
able
to
store
any
type
of
data,
so
you
can
store
document
data
in
sequel
server.
You
can
store
binary
blob
data.
You
can
store
a
iot
type
data.
It
does
really
matter
any
type
of
data
it
can
be
stored
inside
a
sequel
server
and,
in
fact,
n
sequel,
server,
2017,
which
is
coming
out
later
this
year.
We
also
introduced
the
idea
of
being
able
to
store
graph
data
in
sequel
server.
A
You
really
have
don't
have
a
need
to
have
a
special
raph
database.
If
you
have
graph
type
data,
you
can
store
that
in
sequel,
server
and
query
it
and
store
it
using
graph
semantics
now
in
general,
Microsoft
is
embracing
this
idea
of
choice.
So,
as
you
know
about
a
third
of
the
virtual
machines
in
Azure
are
Linux
right.
Dotnet
is
now
running
on
Linux
and
Mac
OS,
it's
open
source
you've
got
R,
which
is
a
server.
A
The
Microsoft
provides
open
source
ready
to
go
so
that
all
these
things
that
Microsoft
is
doing-
and
in
fact
Microsoft
is
the
number
one
contributor
to
open
source
projects
on
github.
This
is
sort
of
the
new
Microsoft
right
and
sequel.
Server
on
Linux
is
just
another
step
in
that
direction
about
giving
customers
the
choice
of
where
they
want
to
run
their
sequel
server
database.
A
So
a
sequel,
server,
2017
we're
introducing
support
for
Linux
and
for
docker
containers,
as
I
mentioned,
we're,
adding
support
for
graph
databases,
we're
adding
support
for
executing
Python
in
your
database
and
we're
improving
the
performance
even
more
so
as
I
mentioned,
sequel
server
is
already
the
fastest
database
on
the
planet.
We're
making
it
even
faster
and
I'll
show
you
more
about
that
here
in
a
moment.
So
how
did
we
manage
to
bring
sequel
server
to
Linux?
It
really
didn't
take
that
long.
A
People
typically
think
all
we
must
have
like
had
some
poor
souls
that
were
over
in
some
building
in
the
corner
of
campus,
that
were,
you
know,
sort
of
transcribing
code
in
order
to
get
it
to
run
on
on
Linux.
But
that
wasn't
really
the
case
that
wasn't
the
approach
that
we
took.
What
we
actually
did
was
we
took.
Some
technology
has
been
in
sequel
server
for
a
long
time
called
the
sequel,
OS
and
a
sequel.
Os
is
a
layer
inside
of
sequel
server.
A
That's
been
there
since
sequel,
server
2005,
which
is
responsible
for
memory,
handling
for
processor,
scheduling
for
disk
and
network
I/o,
and
so
on
and
sequel
server
has
optimized
that
Hardware
interaction
because
it
has
a
specialized
workload
right.
So
we
don't
want
to
depend
on
a
general
purpose
operating
system
like
Windows
for
that,
so
we
brought
all
of
that
type
of
Hardware
management
inside
of
sequel
server
itself.
A
Now
Microsoft
Research
also
had
a
project
a
few
years
ago
called
drawbridge
and
drawbridge
was
a
project
that
was
intended
to
provide
process
isolation,
so
the
sort
of
like
a
container
right,
the
idea
being
that
we
could
be
able
to
run
processes
in
isolation
and
Azure
and
get
higher
density
for
a
compute
in
Azure.
Now
this
particular
project
was
sort
of
shelved
because
docker
was
coming
on
the
scene.
It
was
very
popular
and
so
like,
okay,
we
don't
need
to
know
you
did.
You
know,
compete
against
that.
A
Let's
just
go
with
docker
right
now,
but
we
took
that
project
and
we
learned
something
interesting
from
that,
which
is
that
they
were
able
to
map
all
of
the
API
calls
and
windows
down
to
about
50
application.
Binary
interface
calls
so
you
can
think
about
the
huge
surface
area
of
the
win32
api.
All
boiled
down
to
just
these
50
ABI
s.
So
we
did.
Is
we
combined
SOS
and
the
drawbridge
project
into
what
we
now
call
the
sequel
platform,
abstraction
layer
or
sequel
pal?
A
We
can
bypass
those
four
things
that
are
performance
critical,
so
the
result
of
this
is
that
we
now
have
the
relational
database
engine
running
on
top
of
sequel
pal,
and
we
didn't
have
to
rewrite
it
right.
It's
mostly
just
the
way.
It
was
so
that's
good
in
terms
of
code
quality,
because
every
time
you
go
and
rewrite
a
bunch
of
code,
you
know.
Undoubtedly
some
Engineer
is
going
to.
You
know
fat-fingers
something
and
end
up
with
a
bug.
A
We
fix
a
bug,
it's
fixed
on
both
platforms
anytime,
we
introduce
a
new
feature
like
sequel
graph.
It
just
shows
up
on
both
platforms.
In
fact,
sequel
graph
is
built
by
sequel,
server
engineers
that
do
all
their
development
and
testing
running
sequel
server
on
Windows,
but
it
just
works
on
sequel
server
on
Linux
as
well.
So
today
we
have
the
relational
database
engine
running
on
top
of
the
sequel
pal.
A
The
engineering
team
is
also
now
already
at
work
on
bringing
integration
services
to
run
on
top
of
sequel
pal
and
that
will
be
released
at
some
point
in
the
near
future
and
we're
also
bringing
our
services
on
top
of
the
sequel
pal
as
well
and
then,
depending
upon
customer
feedback,
we'll
bring
things
like
analysis,
services
and
reporting
services
as
well.
Now,
the
first
question
I
always
get
asked
after
I,
introduces
a
concept
of
like
a
sequel.
Pal
is
like
well
what
about
performance?
You
guys
introduced
a
new
layer
here.
A
What's
what's
the
impact,
so
we
just
what,
like
two
weeks
ago,
I
think
published
our
first
benchmark
for
sequel
server
on
Linux,
and
we
chose
to
partner
with
rel
and
with
HPE,
to
publish
this
benchmark,
and
the
first
benchmark
shows
that,
in
fact,
the
performance
of
sequel,
server
2017
on
rel
is
awesome.
It's
what
you
would
expect
from
sequel
server.
In
fact,
we
increase
the
performance
by
5
percent
and
decrease
the
cost
for
performance
by
6
percent,
and
this
is
on
comparable
hardware.
A
A
How
many
of
you
guys
thought
that
when
you
first
saw
this
lies
right,
yeah,
okay,
so
there's
one
subtle
thing
here:
that's
easy
to
sort
of
ignore,
which
is
that
this
test
is
a
comparison
of
sequel,
server,
2017
on
rel
versus
our
last
benchmark,
which
was
sequel
server
2016
on
Windows,
okay.
So
it's
not
the
sequel.
Server
rondrell
is
faster.
I'm
here
to
tell
you
that
it's
not
it's!
A
So
hopefully
you
guys
saw
that
there,
but
it's
really
exciting
to
see
and
we're
excited
to
be
partnering
with
Red,
Hat
and
HP
e
on
this
now
this
slide
is
a
bit
of
an
eye
chart,
so
I've
included
it
here
in
the
deck,
mostly
just
for
completeness,
and
people
can
refer
to
it
later.
But
the
ideal
is
sequel
server
2017
on
Linux.
Is
that
we're
going
to
deliver
the
database
engine
and
that
will
be
the
scope
of
the
the
first
release.
A
So
it
won't
include
things
like
integration,
services,
reporting
services,
analysis
services
and
some
of
these
kind
of
peripheral
services
around
the
database
engine
will
be
focused
primarily
on
the
database
engine.
Now
within
that
database
engine
there's
a
huge
feature
set
and
because
of
the
sequel
towel,
we're
able
to
deliver
almost
the
entire
feature
set,
so
things
like
in-memory,
OLTP
or
columnstore,
or
partitioning
or
json,
or
xml
or
graph,
they
all
just
work
on
sequel
server
on
Linux.
There
are
a
few
exceptions.
A
Things
like
file
table
doesn't
work
because
there's
some
dependencies
there
on
the
windows
file
system
that
we
have
not
been
able
to
implement
for
the
Linux
side.
Yet
some
things
like
poly
base
or
stretch
DB.
So
the
couple
features
that
aren't
there
yet
we'll
add
those
over
time.
There's
just
kind
of
another
list
of
things
that
you
can
take
a
look
at,
but
kind
of
the
key
things
to
take
away
here
is
that
we're
almost
done.
A
In
fact,
the
last
feature
we
have
to
do
is
Active
Directory
Integration
and
the
engineers
just
got
it
working
last
night
and
I'm
going
to
demo
it
to
you
today.
At
the
end
of
the
session-
and
hopefully
it
works
right,
but
that's
actually
the
last
feature
we
have
to
do
for
this
release
and
from
here
on
out
till
general
availability
it'll
just
be
all
about
stabilization
and
responding
to
customer
feedback,
so
we're
actually
pretty
much
done
with
this
first
release.
A
Okay,
so
a
couple
notes
on
some
key
feature
areas.
So
with
security
we
have
transparent
data
encryption.
This
allows
you
to
encrypt
your
data
at
rest,
whether
it's
you
know
an
operational
DB
or
it's
always.
It's
also
encrypted
at
the
time
that
you
back
it
up.
So
it's
always
back
backed
up
and
encrypted.
We
have
cell
level
encryption,
we've
got
always
encrypted,
which
is
an
interesting
feature
that
allows
the
client-side
application.
A
Then
we
also
have
access
control.
So
you
have
the
ability
to
log
in
with
sequel
logins,
as
I
mentioned,
to
be
able
to
log
in
with
Active
Directory
user
authentication
as
well.
We've
got
very
granular.
Role-Based
security
built
into
sequel
server,
that
same
functionality
exists
with
sequel.
Server
on
Windows
today
carries
over
to
sequel
server
on
Linux.
We
have
some
other
features
like
row-level
security,
dynamic
data
masking
which
allows
you
to
mask
data
when
it's
returned
by
sequel
server.
A
So
if
you
want
to
mask
a
social
security,
number
or
email
address
or
so
on,
and
we
also
have
fine-grained
auditing,
so
you
can
keep
track
of
every
change
that
happens
to
anything
in
the
database.
Now
the
area
of
high
availability
is
a
huge
area
for
sequel
server,
so
this
covers
everything
from
your
typical
VM
level.
High
availability,
if
you
want
to
be
able
to
vmotion
your
servers
around,
we
support
that
backup
and
restore
is
supported.
Of
course,
you
can
backup
your
database
on
sequel
server
on
Windows
and
they're
stored
on
sequel
to
run
Linux.
A
If
we
have
some
time,
I'll
show
you
a
demo
of
that
today
as
well,
then
we
move
into
some
other
areas.
Like
you
can
use
the
sequel
server
agent
to
do
log
shipping,
so
you
can
ship
the
log
off
to
a
remote
location
and
have
that
be
replayed
on
the
other
end.
So
that's
good
disaster
recovery
scenario
where
you
need
geo
redundancy
and
then
we
move
into
scenarios
like
failover
clustering
with
shared
storage.
So
it
failed
over
clustering
for
shared
storage
on
Windows.
A
You
would
use
Windows
Server,
failover
clustering
and
those
are
services
that
are
built
into
Windows.
So
what
are
you
doing?
Linux
eyes?
Well,
we
partnered
with
Red
Hat.
We
talked
to
a
bunch
of
customers
and
the
feedback
that
we
got
from
everybody.
It
was
like
Oh.
Pacemaker
is
the
way
to
go
on
Linux.
So
as
a
reference
implementation,
we've
built
our
high
availability
solutions
to
use
pacemakers
the
clustering
technology.
Now
the
design
on
Windows
is
very
integrated,
with
sequel
server
on
Linux,
because
there
are
multiple
high
availability
solutions
in
Linux
market.
A
We
designed
we
decided
to
take
a
more
open
approach
to
it
and
there
you
can
plug
in
lots
of
different
high
availability
solutions.
You
could
be
pacemaker,
could
be
zookeeper
and
we're
working
with
some
additional
partners.
It
will
offer
some
solutions
in
this
space
and
we'll
have
some
more
to
talk
about
that
later.
The
idea
is
to
have
a
more
open
architecture.
Allows
you
to
plug
in
whatever
high
availability
solution
makes
sense
for
you
now.
We
also
have
support
for
always-on
availability
groups,
always-on
availability
groups,
our
sequel
servers,
way
of
providing
high
availability
through
replication.
A
This
is
also
great
for
scaling
out
your
backups,
for
example.
So,
instead
of
doing
a
backup
on
your
primary,
you
could
actually
do
a
backup
off
of
one
of
your
read-only
secondaries,
and
this
was
also
interesting,
because
you
can
do
this
type
of
scale
out
in
a
cluster
list
with
people
Server
2017.
So
you
don't
have
to
have
a
cluster
if
you
just
want
to
do,
read
only
scale
out
and
get
some
redundancy
that
way
go
for
it
and
then
I
have
so
we
went
out
and
we
talked
to
customers
about
high
availability
scenarios.
A
I
kept
having
people
ask
me
like
well:
can
I
have
a
Windows
node
and
a
Linux
node
in
one
always-on
availability
group
I
was
like
dude,
that's
weird.
Why
would
you
do
that?
That's
just
that's
just
weird!
Why
and
then
I
got
to
talking
to
people
about
it
and
they
actually
came
up
with
some
interesting
scenarios
why
you
might
want
to
do
this
so
the
first
reason
was
sequel
server
on
Windows
migrations
to
sequel,
server
on
Linux,
with
minimal
downtime.
This
is
where
all
of
you
in
the
room
be
like
yeah.
A
Finally,
we
can
get
rid
of
those
Windows
servers
and
get
all
the
sequel
servers
over
on
Linux
by
having
high
availability
groups,
and
we
just
replicate
the
data
across
when
we
just
failover
and
we're
done
so.
We
like
okay,
that's
an
interesting
scenario,
so
we
went
and
built
it
and
it
works.
So
you
can
now
do
always-on
availability
groups
which
span
across
Windows
and
Linux
it's
weird,
but
if
your
goal
is
to
migrate,
you're
good
to
go,
go
for
it
now.
Another
scenario
that
people
think
about
here
is:
is
this
idea
of
operating
system
level?
A
Then
you
could
failover
from
one
OS
to
the
other
or
back
right.
So
it's
kind
of
an
interesting
idea.
This
OS
level
redundancy
see
there's
one
other
point
about
h:a.
Oh,
very
importantly,
this
type
of
configuration
with
Windows
and
Linux
and
one
availability
group
is
not
an
H,
a
solution
right
because
there's
no
cluster
manager
that
stands
Windows
and
Linux.
This
is
really
just
for
migrations
or
more
manual
failover
zin,
a
scenario
that
I
described
all
right.
So
then
people
asking
about
tools?
Ok,
so
what
are
we
doing
about
tools
so
sequel?
A
Individual
studio
code
and
I'll
show
you
guys
this
here
in
a
minute
and
that
allows
you
to
connect
to
sequel
servers,
whether
they
run
on
Windows
or
on
Linux,
and
execute
some
queries.
You
get
syntax
highlighting
and
intellisense
and
cool
features
like
peak
definition
and
so
on,
and
all
that's
just
built
individual
studio
code.
You
can
run
it
on
your
Mac
on
your
Linux
machine
or
on
Windows
connect
to
Linux
or
Windows
and
gives
you
lots
of
flexibility
that
way
it.
So
it's
really
great
for
developers
that
are
using
a
code,
editing
tool
like
that.
A
But
what
about
the
VBA?
You
know
they're,
not
necessarily
writing
code.
Every
day
they
just
need
a
tool
that
they
can
use
to
execute.
Some
queries,
maybe
set
up
an
always-on
availability
group
check
on
the
you
know,
state
of
a
few
things
set
up
some
logins
whatever
that
might
be.
So
for
that
scenario,
we're
now
working
on
a
new
cross-platform
database
admin,
GUI
tool
and
the
codename
for
this
project
is
carbon
and
we
will
be
releasing
it
here
pretty
soon
and
it
will
be
super
cool.
A
Extensions
is
already
up
on
github
and
the
carbon
project
is
already
on
github,
but
it's
private
right
now,
we'll
flip
it
to
public
once
we
make
the
first
release,
so
those
are
kind
of
the
tool
sets.
Now.
We've
also
been
doing
some
testing
with
third-party
tools,
like
JetBrains
data
grip
or
DB,
for
eclipse
all
those
different
tools
that
people
use
on
different
platforms.
They
just
connect
to
and
work
with,
sequel
server
on
Linux,
just
fine,
all
right,
whoo,
that's
the
end
of
the
slides.
You
guys
ready
for
some
demos
check
that
out.
A
Maybe
I
can
take
a
couple
questions
while
I'm
getting
set
up
for
demos.
Any
questions,
yes,
sir.
Yes,
the
question
is:
did
we
have
any
problems
with
forward
slash
back
slash
in
the
paths
for
files
and
so
on?
And
and
yes,
we
did
yeah,
so
we
had
to
work
through
all
those
things,
but
those
are
all
resolved
now
and
you
can
use
native
Linux
file
path,
syntax
in
your
T
sequel,
queries
and
even
in
sequel,
server
management
studio.
A
A
A
A
All
right
so
I've
got
a
local
VM
here,
I
wasn't
sure
about
the
network,
so
I
pulled
down
the
RPM
package
here
locally.
So
this
was
also
kind
of
an
interesting
demo
to
show
you
don't
have
to
necessarily
install
from
our
public
package
repo.
You
can
pull
it
down
and
copy
it
over
to
the
server
and
install
it
manually
right.
So
I
can
just
do
yum
install
MS,
equal
Y
boom.
Now,
when
you're
installing
this
from
a
from
the
public
packaged
repo.
A
Depending
on
your
network
connection
speed,
you
can
download
and
install
sequel
server
in
less
than
a
minute
just
like
that.
It
is
really
fast
how
many
people
have
installed
sequel
server
on
Windows
yeah
how's,
that
3.2
I
think
it
is
gigabyte
downloads,
and
then
you
know,
you've
got
I,
don't
even
know,
I
think
it's
like
42
clicks
or
something
like
that.
A
We
we
figured
out
how
many
clicks
it
was
gonna
do
is
sort
of
like
42
or
something
so,
but
you
know
you
can
see
here
that
it's
just
a
young
installation
experience
using
an
RPM
package.
It's
the
same
on
the
other
distributions
of
Linux.
You
can
use
the
package
managers
as
native
to
those
distribution,
so
that's
it.
A
You've
got
sequel
server
installed
now
and
the
next
step
that
you
do
is
you
run
ms
sequel,
comp
setup
so
we'll
just
go,
opt
and
the
sequel
bin
sequel
set
up
now
for
our
Windows
administrators
that
are
going
to
be
coming
over
to
run
sequel
server
on
Linux,
it's
going
to
happen.
We
wanted
to
make
them
feel
comfortable
when
they
came
over
to
here.
So
we
built
them
a
nice
command-line
wizard
because
ever
heard
of
a
command-line
wizards,
it's
really
cool.
A
You
can
go
in
here
and
you
can
answer
its
questions
like
yes,
I
accept
the
License
Agreement,
here's
my
password
okay,
now
it's
configuring
sequel,
server,
I'll
be
done
so
first
point
here
we
have
to
ask
for
the
license
acceptance.
We
tried
to
get
the
lawyers
to
say
that
it
was
okay
not
to,
but
it
just
is
right
so
and
we
have
to
ask
for
a
password
because
they
have
to
be
secured.
So
those
are
the
only
two
things
you
have
to
provide
to
install
sequel
server
on
Linux,
right
and
now
you're
done
so
now.
A
Everything
set
up
and
configured
ready
to
go
now.
You
might
be
like
that's
a
little
weird
having
like
a
wizard
type
experience
at
the
command-line
here,
but
don't
worry
because
we
have
it
all
set
up,
so
you
can
use
environment
variables
or
a
configuration
file.
So
I
can
come
in
here
and
I
can
do
something
like
accept.
A
Password
equals
UConn
hundred
and
then
I
can
run
em
s
equal
comm
setup
and
just
by
passing
those
environment
variables
on
the
same
command
line.
There
it'll
set
the
environment
variables,
the
the
sequel
server
engine
and
when
it
starts
up,
we'll
look
for
the
environment
variable
to
be
set
and
I'll
do
the
magical
things
and
I'll
just
come
up
and
run
so.
This
is
the
way
that
you
can
do
a
one-line,
install
and
configuration
of
sequel
server.
You
can
use
an
MS
sequel,
comm
file
as
well.
A
If
you
want
to
be
able
to
have
all
of
your
configuration
settings
stored
in
a
file,
you
just
drop
that
file
in
to
the
right
place,
run
MS,
Equal,
cost
setup
and
you've
got
sequel
server
up
and
going
so.
This
was,
you
know
the
way
the
Linux
people
do
it
right.
So
you've
got
your
Linux
way.
You've
got
your
windows
way,
you
sort
of
pick
your
way,
but
there
will
be
no
GUI
right.
There
are
no
next
buttons,
so
we're
going
to
try
to
make
it
as
linux
native
as
possible.
A
Alright!
So
now,
let's,
let's
take
a
look
at
a
couple.
Other
things
here
right
so
will
we
introduced
a
GUI
for
installing
sequel
server
on
links
unless
we
have
overwhelming
feedback
from
customers
know
if
you
know
feedback
from
customers
so
far
is
then
this
is
awesome.
This
is
exactly
what
it
should
be.
Thank
you
very
much
for
doing
it.
The
right
way,
Microsoft
and
we
will
not
be
building
a
GUI
for
Linux.
Right,
hopefully
already
agrees
with
that
notion,
but
ok
now
to
make
things
even
easier,
because
I
know
everybody
likes
easy.
A
We
have
published
a
image
of
sequel
server
on
rel
up
in
Azure
and
you
can
just
go
up
here.
Click.
This
click
create
and
it'll
go
through
and
ask
you
a
few
things
about
what
size
your
virtual
machine
should
be.
What
you
want
your
SSH
login
password
to
be
or
you're
going
to
use
your
you
know
your
keys
or
whatever.
So
just
ask
you
a
few
basic
questions
and
you'll
have
a
sequel,
server
running
on
rel
up
in
Azure
and
we'll
continue
to
improve
this
experience.
But
as
of
right
now
you
deploy
this
thing.
A
Sequel
server
will
be
pre-installed
in
it.
Then
you
just
run
in
a
sequel,
comp
setup,
passing
our
license
acceptance
and
your
si
password
and
you
have
a
sequel
server
running
in
in
row.
Now
we
did
an
interesting
thing
here
where
we
partnered
up
with
Red
Hat,
and
we
got
them
to
be
very
generous
and
offer
this
image
without
the
Red
Hat
subscription
premium
cost
associated
with
the
virtual
machines
you
deploy
using
this
image
up
until
general
availability.
A
So
you
can
go
up
there
and
you
can
play
around
with
this
and
and
use
this
without
the
additional
Red
Hat
subscription
premium
cost.
You
only
pay
for
compute
with
this
particular
VM
image,
so
give
that
a
try.
It's
the
easiest
way
to
get
going
with
sequel
server
on
rel.
If
you
have
an
add
your
subscription,
ok,
but
now
containers
they're
the
new
hot
thing
right
so.
A
We
have
published
I'm
going
to
show
you
this
real
quick,
so
we've
published
an
image
up
on
docker
hub.
It
is
an
abuti
based
image
and
you
can
see
that
it's
been
downloaded
where
we
at
now
nine
hundred
and
sixty-four
thousand
times
in
about
five
months.
So
it's
been
a
very
popular
way
for
a
sequel
server
to
be
acquired
and-
and
it's
just
so
easy
I
just
love
dr.
I,
only
I
pretty
much
only
work
with
docker.
Now
I,
don't
do
vm's
anymore.
A
Unless
I'm
doing
demos
like
this,
so
publishing
is
a
boon
fee
based
image
up
to
dr.house,
really
easy,
because
there's
no
license,
there's
no
lawyers.
It's
you
just
push
it
up
it
right,
but
with
the
with
rel,
we've
got
to
be
a
little
bit
more
careful
about
things.
So
I
can't
push
a
rel
based
image
up
to
docker
hub,
but
I
can
push
a
docker
file
up
to
my
github
repository.
A
So
if
you
go
to
my
github,
you
can
find
a
docker
file
that
will
show
you
how
to
build
a
rel
based
container
image
and
I've
got
basically
the
same
thing
here.
Let's
just
kind
of
pop.
This
up,
so
basically
all
this
does
is
it
goes
out
here
and
it
uses
your
subscription
manager
to
go
and
log
into
your
subscription
and
it'll.
You
know
update
the
packages,
it'll
install
sequel
server
and
it
will
follow
sequel
server
tools
and
then
it
will
start
the
sequel,
server
process
right
and
that's
it.
A
So
you
know
true
to
the
container
pattern.
When
people
server
runs
container,
it's
just
the
sequel
server
engine
process-
that's
all
it's
there
now
I
can
go
out
here
and
I
can
build
an
image.
So
I
can
do
doctor
build
oops
wrong.
One
doctor
build
all
right,
so
dr.
build
dot
boom.
I
already
have
all
the
images
built,
but
you
can
see
how
it
kind
of
works
there.
I
can
do
doctor
images.
A
A
Look
at
WWII
back.
This
is
worldwide
importers,
backup
database.
This
is
our
sample
database
that
we
provide
for
people
to
kind
of
play
around
with
it
has
all
of
the
most
advanced
features
of
sequel
server
running
inside
of
it,
and
what
I'm
going
to
do
is
I'm,
going
to
start
up
a
new
rail
based
container
and
we're
going
to
restore
that
back
up
to
that
container.
So
we'll
go
docker
run
II
except
EULA.
There's
that
license
acceptance
thing
again.
You
can
see
how,
like
things,
work,
consistently
right,
so
I've
got
the
environment.
A
A
88
e9
bin
slash
bash
okay,
so
now
we're
inside
the
container
and
we'll
you
know
go
into
the
backup
directory
inside
the
container
will
LS.
So
there's
our
backup
file,
the
backup
files
on
the
host.
But
it's
been
mapped
into
the
container.
So
now,
I
want
to
show
you
the
Visual
Studio
code
extension,
so
the
Visual
Studio
code,
extensions
access
by
opening
up
the
command
palette
and
you
type
sequel
and
you
can
see
all
the
different
commands
that
are
available.
So
in
this
case
I
want
to
connect
I'm
going
to
connect
a
local
host.
A
Okay,
so
down
here,
you
can
see
that
it's
connecting
we're
connected
now
to
localhost,
which
is
where
my
container
is
running.
Now,
if
I
run
this
command
here,
it
will
show
me
all
of
the
data
files
that
are
associated
with
this
backup,
and
you
can
see
that
in
fact,
these
backup
files
originated
on
Windows
right.
So
now,
what
we're
going
to
do
is
we're
going
to
restore
this
backup
to
Linux-
and
you
know
again,
keep
in
mind
is
this:
has
all
of
the
most
advanced
features
of
sequel
server
running
inside
of
it.
A
So
there
you
go
finishing
up
the
restore
right
now,
but
this
is
a
probably
the
easiest
way
to
migrate
from
sequel
server
on
Windows,
the
sequel
server
on
Linux.
You
just
do
a
backup
in
a
restore.
You
can
also
do
an
detach
and
attach
you
can
use
sequel
package
to
create
a
backup
file
or
a
DAC
pack
file
either
way
you
can
deploy
on
easily
from
sequel
server
on
Windows
the
sequel
server
links.
So
there
you
go,
it's
been
restored
now
what
I
want
to
show?
A
I've
got
docker
compose
setup
to
where
I
have
multiple
containers
involved
in
providing
an
image.
So
I've
got
the
voting
application,
which
is
a
Python
based
application.
I've
got
a
Redis
container
that
allows
the
user
to
just
you
know,
vote
on
dog
versus
cats.
The
vote
gets
stored
in
the
Redis
container.
Then
I
have
a
Java
worker
container
that
copies
the
vote
from
the
Redis
cache
DB
over
to
the
sequel
server
database
container,
which
in
this
case
is
running
in
a
sequel,
server,
rel
and
then
it'll
display
the
results
using
a
node
based
application.
A
Kill
that
last
container
and
we'll
just
do
docker
compose
up,
and
this
will
start
up
all
of
those
five
containers
all
simultaneously
and
the
containers
will
connect
up
to
the
corresponding
databases.
They
need
to
be
connected
to
you
and
once
we
do
that,
then
we
can
see
the
application
inside
of
the
browser
and
we
can
vote
on
dog
vs.
cats.
So,
while
we're
waiting
on
that
to
come,
quick
show
of
hands
dogs,
cats,
dogs
went
as
always
alright.
A
Okay,
so
here's
our
dogs
and
cats,
we're
going
to
vote
on
dogs
and
here's
our
dogs
right.
So
this
is
a
quick
example
to
show
you
how
sequel
server
can
run
in
a
container.
It
can
be
part
of
a
docker
composed
application.
It
works
with
Python
and
node
and
Java,
or
does
any
language
you
want
and
in
this
particular
case
I'm
using
the
for
JSON,
auto
functionality
and
sequel
server
to
actually
query
the
database
return
the
results
back
in
JSON
format
and
simply
pass
that
directly
through
to
the
front
end
where
it's
rendered
all
right.
A
A
Okay,
so
I've
already
got
my
project
up
there:
okay,
here's
my
day-trader
demo,
okay,
I,
don't
have
anything
in
it
now
I'm
going
to
replace
a
few
of
the
different
container
images
there
with
kind
of
most
recent
ones
for
JBoss.
So
this
is
a
the
day
trader
demo,
apps
kind
of
canonical
and
the
J
box
Java
world
right
and
now
I'm
going
to
simply
deploy
that
application
up
to
OpenShift.
A
This
will
push
my
application
up
there
and
you
can
see
that
now
everything's
kind
of
coming
in
there,
including
the
MS
sequel,
server
image
here,
so
just
given
the
time
I'm
probably
going
to
skip
over
this
part
of
the
demo.
But
the
idea
with
this
is
that
I
can
push
sequel
server
containers
as
part
of
an
application
up
into
open
ships
and
there's
lots
of
different
ways
of
doing
this.
This
is
just
one
particular
way.
This
project
is
available
up
on
my
github
as
well.
A
A
So
here
we
are
I'm
ssh
into
a
host
up
in
Azure
and
I
am
going
to
connect
over
to
a
sequel
server
instance.
Now,
in
this
particular
case,
you
can
see
that
I'm
ssh
into
this
machine
using
an
active
directory,
ID
travis,
@ad
demo
com.
So
this
machine
is
already
domain
joined.
It
is
a
Linux
machine,
obviously
because
I'm
SSH
into
it,
but
I'm
logged
in
using
an
Active
Directory
identity.
A
A
What
I
do
Oh
principles?
Probably
okay,
all
right,
so
there
you
can
see
the
ad
demo
Travis,
underneath
there
right.
So
this
is
that
now
a
login
that's
available
for
authenticating,
with
sequel
server,
so
we'll
quit
out
of
this
now
and
this
time,
when
I
connect
to
the
server
I'm,
not
going
to
use
the
sequel,
login
I'm
going
to
use
the
identity
that
I'm
logged
in
with.
Currently
there
you
go
I'm
connected
right,
so
just
like
that
I'm
able
to
authenticate
using
Active
Directory
identities
against
sequel
server
running
on
rel.
A
Okay,
so
the
road
ahead,
we
are
in
the
community
technology
preview
phase.
Now
we
just
released
CTP
2.0
in
the
middle
of
last
month.
That
is
our
production
ready
release.
We
have
customers
that
are
in
our
early
adoption
program
now
that
are
already
in
production,
using
sequel
server
on
Linux
and
we're
targeting
a
second
half
of
this
calendar
year
as
the
final
general
availability
release
with
sequel
server
on
Linux.
So,
as
I
mentioned,
we
have
this
early
adoption
program.
A
If
this
is
something
that's
interesting
to,
you
is
to
actually
start
using
sequel
server
on
Linux
in
production
prior
to
general
availability.
Please
sign
up
at
this
link
here
and
we
would
be
happy
to
support
you
in
that.
So
we
have
Microsoft
support
standing
by
they're,
fully
trained
ready
to
support
you,
24/7,
with
the
sequel,
server
engineering
team,
standing
behind
them
to
make
sure
that
your
applications
run
smoothly
in
production
and
for
the
preview
period.
A
There's
no
cost
to
doing
that,
and-
and
you
can
get
started
right
away-
the
only
thing
that's
required
as
an
NDA,
which
a
lot
of
companies
already
have
with
Microsoft
and
then.
Lastly,
these
are
all
the
things
that
I
demonstrated
to
you
and
and
more
you
can
go
and
grab
these
things
and
kind
of
try
them
out
for
yourself
and
with
that,
I
will
end
this
speed
session.