OK, so now I'm going to talk about comp 283 which is applied database management. It's a second semester seven and a half credit module, so it's one of our half modules.

So what is it that we actually do in the applied database management module? Well, basically it's an exploration of the real life considerations when developing a database system. If you're developing a database in your University, work.

Then you don't worry about the hardware, it runs on. You don't worry about how much memories in that server, you don't worry about with that service located how it's backed up.

But if you're providing a database for a business.

Then all of these things are.

Things you have to consider.

In terms of the software, you might actually have a choice of.

The actual database management system that you use and the operating system on which that runs.

In terms of hardware.

Is obviously a physical computer, but that computer has.

Certain amount of memory memory is expensive. You don't want to spend money unnecessarily.

On resource is that you don't actually need.

It's a certain amount of disk storage required for your database, but not just for the database. What about the computer operating system?

What are my backups? What about?

Transaction logs and all the other.

Anne.

Files and data that gets generated.

That you need to keep.

If you've.

Bought a disk that's really only big enough. Your database you're going to run out of storage really quickly in your database is going to fail.

And finally.

What about where this hardware is located?

The environment in which it's located.

Is it a secure environment? Is this database?

Going to have important.

Data on it that needs to be kept secure, in which case having it on a server sitting on a desk in an open office is probably not a good idea.

What about the resource? Is it requires in order to run?

How much power does it need? Does it need special power installing or can you just plug it into a?

A normal 3 pin socket.

Does it require an air conditioned room or will it just operate in a normal environment? All of these things need to be considered for the hardware that you're going to be using.

And that's kind of the essence. If you like of this module that it isn't just about the database.

Itself.

The Sqlcode or whatever it is.

It's also about everything that goes into the database system, and then we're going to also look at.

The database systems themselves DBMS.

Particularly my SQL, we're going to get most of our examples from there, but we're going to contrast it with some other database systems.

Particularly Emma SQL.

And Oracle.

OK.

Looking at the structure of the module, when it runs for the.

Hold of the second semester.

It is a long thin half module.

There's one lecture per week.

And that covers these sorts of topics.

I'm looking at the kind of files to get correct with the database. Looking at the kind of disks or raid systems we can use with our databases.

Authentication works authorization so on.

We're looking at some security issues how we optimize our databases. Can we maintain integrity of our data and make sure our databases are efficient?

Anne.

How we look after the service. How we think about.

Know whether our database can survive having to be switched off for a certain amount of time, or do we need multiple servers?

These things are all things you can really need to consider if you're providing a database to a company.

The module also has 1. Two are practical per week.

It's 100% continuous assessment.

And.

In order to.

For that to work, there are three assignments.

There's basically a report and a presentation.

For each of these assignments by the whole group and you will be split up into groups.

The groups are given scenarios.

And they have to develop a database.

For each for that scenario.

Groups are not giving given exactly the same scenarios are different depending on the group.

And you choose how to interpret that scenario.

And then having given that initial report, you'll get feedback on that, and then we'll kind of move on looking at change that database knew issues arising and how we can cope with that.

OK, and that's coming to 8 three.