All language subtitles for 01 - Studio databases- Postgres

- DaVInci Resolve 12 has
two types of databases

that you can install to
manage your projects.

We already looked in
the Essentials training

at the disk-based database,

which is the default database.

It's basically the one,
over the past two years,

that the Blackmagic team
has been migrating us

all towards using.

If you're just a single operator,

or just running a single
room of DaVinci Resolve,

the disk-based database,
great way of going.

But the moment you want
multiple installations

of DaVinci Resolve, sharing
a single central database,

you need to move to a PostgreSQL database,

an SQL database.

Now let's take a look
and see how you can tell

if you're running a disk-based
versus a SQL database.

We're in the Project Manager

and this is from the project

that we installed from
the exercise files movie.

And I'm gonna open up
the Database Manager,

and I've got one database
in here right now,

and how do I know,

is this a disk-based database

or a PostgreSQL database?

Well, the Host column will tell me

everything I need to know.

If I'm seeing something like
what I'm seeing right now,

which is user, slash, slash, slash.

What it's telling me is this
is a directory file path.

It's showing me what is the directory path

to get to where this database exists.

This is a disk-based database.

I can not share this database

with other DaVinci Resolve systems.

It lives only on my system and
only this local installation

of DaVinci Resolve can share it.

To create a PostgreSQL database,

what I'm gonna do is come down to Create,

and the first choice that I have to make

is the driver.

It's funny because the disk-based database

is what's the new default
for DaVinci Resolve

but when you go to create a new database,

the SQL database is the one
that automatically pops up.

So if you wanna create
a PostgreSQL database,

you just leave it right where it is.

So what am I gonna fill out in here?

Well, I'm gonna tell you what I'm not

gonna fill out first.

User and password,

I leave these to default all the time.

The fact is, if you lose this password,

and you forget this password,

go ahead, try emailing Blackmagic.

They will not be able to help
you recover this database,

which is why I always
leave it at its default.

If you're working in a big facility

and you have robust password management,

then yeah, go ahead and
protect your databases

by changing the password.

Otherwise, for the rest of us,

leaving it right where it is

is the thing to do.

So I'm gonna give this a label,

a human-readable name

that will pop up in this list

every time I pop into
the Database Manager.

Let's call this

Resolve12_Advanced_DeleteMe.

Notice that I'm only using alphanumerics

and an underscore.

You could also use a dash

but that's the only
characters available to you.

I also have to give it a database name

so in the actual Database
Manager that's hidden

deep in the nethers of
my operating system here,

this is actually gonna
be given a real name,

a database name.

It does not have to match
the human-readable label,

but I like to make it match

because it makes it much easier to find it

and recover it and restore it,

if I just know it's just basically

the lowercase version of
the human-readable labels.

So I'll call this
resolve12_advanced_deleteme,

all lowercase.

And then it's just a matter
of creating a new database.

It'll take a moment.

It'll do it and then it'll
give me a dialog box,

telling me that I was successful,

which I am.

So now I've got a second database up here

and notice the host.

The host is an IP address.

Now 127.0.0.1 is the local host.

It is this computer,

this Mackintosh HD back here.

We'll self-assign it this IP address.

This is a PostgreSQL database.

There is no file path.

One thing to keep in mind,

if you're running a PostgreSQL database,

the PostgreSQL database itself generally,

usually does not live within a user.

It lives outside of the user,

which means if you have an
automated backup routine

that is not backing up
your entire computer,

including the operating system,

then you're probably not
backing up your databases,

which can be very, very dangerous.

So what I highly recommend you do

is back up your databases
on a regular basis manually,

which we'll be looking
at in a couple minutes.

Now there are a couple
things that go along

with running a PostgreSQL
database that can be,

problems can pop up.

Sometimes you get disconnected
from the database,

sometimes the database stops running.

What do you do in those instances?

You pull up the Blackmagic
DaVinci Resolve 12

user manual and check out this chapter

on Managing Databases
and Database Servers.

There is a ton of useful
information in here,

including command lines
that will allow you

to manage your PostgreSQL database

on Mac, on Windows, on Linux.

You will get the commands you need

to know how to manage this server

so if you are running
multiple installations

of DaVinci Resolve,

all kind of looking at a
central database server,

I think you really need to
spend a little bit of time

and read this chapter.

There are a lot of really
nitty gritty details

you'll wanna understand.

And let's just recap real quickly

the two instances when you would want

to run a PostgreSQL database.

Instance number one is if
you have multiple rooms

that share a database.

They're just color correcting

and you want them to be able to open up

any project at any time,

then you're gonna want to run
a central database server.

The other instance is the
collaborative workflow.

So if you want an editor,
an assistant editor,

a colorist and an assistant colorist,

working on a single
project at the same time,

you're going to want to
run a PostgreSQL database.