►
From YouTube: 2020 10 27 Database Team Weekly
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Next
week
will
be
the
actual
official
incident
review
and
I'm
I'm
still
getting
familiar
with
the
process.
I
wasn't
familiar
with
it
before
until
I
talked
to
dave
yesterday
afternoon
I
was
the
one
to
put
it
on
the
agenda
and
he
said
to
keep
it
there
and
we
will
use
today's
as
information
gathering
and
then
continue
that
throughout
the
week
with
asynchronous
conversations
and
then
have
a
follow-up
next
week.
A
So
unless
there
are
any
questions
move
on
to
the
next
item
so
thursday
we
will
go
through
the
retro.
For
some
reason,
the
bot
didn't
create
our
issue
this
week
or
this
milestone.
So
I
will
go
and
create
it
later
on
today.
I'm
not
sure
what
happened
there.
I
think
that's
the
second
time
it
skipped
over
this
team,
but
not
a
big
deal.
It's
pretty
easy
to
create
so
I'll.
Take
care
of
that
quick
update
on
the
database
lab
enterprise
edition
procurement.
There
is
no
update
on
progress.
A
A
A
I
don't
know
I'm
assuming
yes,
that
we
would
lose
access
to
database
lab
at
that
point
in
time,
but
if
we
get
that
close,
then
start
having
actually
before
that
we
we
have
a
meeting
with
nick
tomorrow.
It's
just
the
regular
sink
meeting,
and
that's
something
that
I
can
just
ask
him.
C
A
A
C
A
And
that's
it
for
items
from
last
week
and
we
did
not
set
up
any
goals
for
last
week
or
we
didn't
explicitly
call
them
out.
So
let's
talk
about
what
we're
going
to
do
for
this
week.
One
question
how's
the
audit
event
swap
going.
D
D
That
should
be
ready,
hopefully
today
or
tomorrow,
for
reviews.
So
I
think
we
should
have
all
the
helpers
wrapped
up
this
week.
That's
my
goal
for
this
week
is:
have
that
all
wrapped
up
this
week
and
be
able
to
create
the
actual
migration?
Probably
next.
A
D
I
haven't
worked
on
that
because
of
the
audit
event
stuff.
I
did
create
separate
issues
for
some
of
the
bigger
ones
that
we
probably
want
to
tackle
the
the
column
type
differences
that
could
pose
a
problem.
D
Probably
some
of
that
work
might
be
overlapping
with
the
changes
to
the
primary
key
columns,
because
we
have
that
same
problem
in
the
schema
differences
that
we
have
different
integer
types
for
the
primary
key.
So
if
we
come
up
with
a
solution
for
one
it
will
solve
the
other.
D
As
far
as
changing
the
the
text
length,
which
is
kind
of
the
other
bigger
issue,
I
don't
think
we
really
have
come
up
with
a
really
a
clear
plan
on
how
to
tackle
that.
First,
it's
it's
just
going
to
be
a.
It
would
be
a
large
migration-
and
I
think,
especially
since
it's
impacting
like
cia
built
in
some
of
the
really
large
tables,
not
sure
how
realistic
it
is
that
we
would
tackle
that
right.
D
C
Yeah,
so
this
is
about
following
up
with
the
incident
review
and
any
any
fixes
coming
out
of
that,
and
presumably
should
also
add
more
ways
to
observe
that
re-indexing
to
happen.
So
maybe
report
some
metrics
and
those
an
issue
for
that
in
the
milestone
and
in
terms
of
re-enabling
that
I
I
don't
want
to
do
this
on
the
next
weekend,
because
I'm
not
next
week-
and
I
don't
have
time
it's
probably
the
weekend
after
or
later.
C
A
B
B
Let's
have
this
as
my
actual
yeah,
okay.
B
B
A
Okay,
there's
nothing
else,
so
I
brought
up
the
quarterly
okrs
last
week
and
I
haven't
gotten
any
pushback,
so
I
will
assume
that
what
I've
put
in
there
is
okay.
E
I
have
one
of
them
if
you
have
time
sure
that's
the
next
quarterly
target
for
the
from
the
aptx
query.
You
know
basically
we're
in
the
next
quarter,
so
we
have
to
figure
out
what
we
want
to
try
and
what
we're
about
to
next
quarter,
so
to
figure
out
what
we
want
to
target
or
aim
for.
I
had
set
99.9,
I
think
just
99.9
before
which
are
already
meeting
just
basically
saying
you
know
what
we're
good,
but
we
want
to
make
sure
we
keep
it
this
way.
E
What
what
does?
What
are
folks
thoughts
on
the
target
for
the
aptx
query?
Should
we
try
and
aim
for
like
99.99?
What's
that,
like
you
know,
as
I
I'm
curious,
what
your
thoughts
are.
B
I
would
like
to
check
the
dashboard
so
what
we
get,
because
we
got
some
now
that
we
have
data
and
see
how
things
are,
what
instances
are
reporting
back
to
us.
E
Yeah
yeah,
that
makes
makes
sense
and
we
can
go
async
on
this
too.
I
just
figured
since
we
had
a
couple
of
some
time.
We
could
chat
about
it
if
we
made
sense
but
open
up
an
issue.
E
D
E
Would
obviously
require
a
code
change
to,
I
think,
get
it
back.
I
believe,
but
maybe
not
actually,
I'm
not
quite
sure
how
the
query
all
works,
but
that's
that's
a
good
option
as
well.
B
B
So
we
are
constantly
getting
a
98.9
for
the
past
three
weeks
out
of
three
thousand
three
thousand
instances
or
six
thousand
in
previous
week
so
yeah.
Maybe
we
have
to
investigate.
B
But
there
were
very
few
instances
only
seven,
but
after
that,
after
we
got
a
lot
of
instances.
We
are
at
a
98.9
and
there
were.
There
are
also
some
instance
reporting
errors,
reporting
crazy
numbers
for
the
query
objects
which
I
have
removed
from
the
dashboard.
But
those
are
four
instances
that
really
report
above
one
100.
E
All
right:
well,
actually
we
so
we
actually
do
have
some
work
out
for
us
here.
We'll
do
a
friend
figure
out
what's
causing
it,
but
maybe
we
leave
it
at
should
we
should
we
lower
it?
I
think
it's
at
99.9
right
now,
but
I
I'll
open
up
an
issue
and
we
can,
I
think,
a
little
bit
more.
It's
probably
worth
a
little
more
thought
than
a
ad.
C
B
So
from
what
I
can
see
from
the
dashboard,
we
have
the
enterprise
edition
ones
are
reporting
lower
numbers,
so
I
can
see
that
the
versions
that
have
a
dashi
report
below
98,
so
some
this
is
something
we
may
want
to
check.
E
Yeah
interesting,
I
wonder
if
it
you
know
correlates
with
instant
size.
D
C
A
You
so
how
do
we
read
those
peaks
and
valleys
so
across
the
bottom?
There's
versions
of
instances?
That's
not
by
date,
though,.
B
B
B
It's
what
the
instance
is
reported
for
that
week,
I'm
sure
you
can
see.
For
the
week
of
28th
of
september,
we
had
6
000
instances,
reporting
data.
While
for
5th
of
october
we
only
have
3
000..
Oh
maybe
we
should
refresh
this.
B
B
B
So
yeah,
if
we
want
to
drill
down
on
that,
maybe
we
can
start
introducing
also
the
memory
those
instances
have
and
use
additional
dimensions
there
or
the
cpu
or
the
size
or
whatever.
B
Oh,
those
are
raw
data,
so
it's
they're
all
id,
so
it's
just
for
exporting.
If
you
wanted
to
export
everything.
B
B
A
So
josh
on
your
question
about,
should
we
change
anything
you're?
Just
I
guess:
what's
the
request,
are
you
you
want
to
change
the
dashboard
or
is
there
work
behind
the
dashboard
that,
like
these
metrics
indicate,
we
need
to
do
something
to
make
some
changes.