All language subtitles for 1. SQL Basic Understanding

Hello, everyone, I'm what you do with your blood.

And today we are going to learn about some basics of sequel.

Even before grading, we need to understand this language, the basics of language, the purpose of

it.

So that is going to be the overview for today's lecture to start with.

You want to discuss about what is a school, what can a school do, we are going to give a brief introduction

to RDBMS, which we talked about in our previous lecture.

You're going to talk about a school and its process as a property that every database follows.

You're going to talk about the model and relationships.

This will give us a very brief idea about how exactly our database is being maintained, how we are

supposed to look at the data.

We get a brief idea about this.

And last but not the least, we are going to talk about database normalization.

Why is it necessary and what is the purpose of using normalization technique in our databases?

So to start with, what is a school?

It is basically stands for a structured query language as Google lets you access and manipulate databases.

So as we talk about database in our last lecture to access the database, we need to learn a language

or we need to talk to database for that as well as the language.

And what does this have school do is that it will help you access a database.

And if you want to change some records in it or you want to insert your records in it, then that also

is possible using this language.

As I have already mentioned, it is used to try to update, modify, delete or insert any new information

in database.

It is this kind of language for all the RDBMS is.

So that is relational database systems.

But there are various different systems available, such as my sequel and this is what I can say.

This information both Green and Tober, but they all use rescuable as the standard database language.

So as we know that there are so many platforms, the communication language still remains the same.

It's only a few syntactical changes which has to be done to your query.

Apart from that, the basic standard still remains the same if you want to access data on different

platforms.

So what can Esquibel do?

It allows users to access data in the relational database management systems, it allows to describe

the data.

So let's say I am new to a company and I want to know that how exactly the backend of this company works.

I can just get access to the database again myself.

Describe the data that how exactly it is being stored.

I can understand the structure of the data.

So it makes very, very much feasible as a newcomer to understand exactly how we are going to process

in this system, how we are going to process in the organization.

It allows the users to define the data in a database and manipulate the data.

Just as I've told you that let's say you are working in a banking organization and if you want to update

the account balance of any particular user, you can do that if you are using databases and if you are

using my sequence.

But if you are using a manual file structure, then that is going to be a tedious work.

Very hard to find the file of the user.

First, you have to manually see how much balance is left.

You have to add yourself and you have to update the final amount into the account balance, which is

a tedious work.

And this is where we are using database allows users to create and drop databases and tables.

Let's say there was some feature in my organization which is no more available and I want to drop that

day, but I can do that because I have access to do so and it still allows me to do so.

Apart from that, it will allow users to retrieve and sort of delete, create new DBAs, it can also

help users to create views, stored procedures, functions in a database.

Now, where are these stored procedures and functions used?

So what happens is that in the database, if there is one particular task that has to be done every

day.

So let's say every day we have to check that.

What was the status of my user the previous day at the end of the previous day?

So in that case, I will write an automated code in the form of stored procedures or functions, and

I will be.

Recording and be automating those transaction statements so that I don't have to manually do this operation

or work every day.

That's when we have to use stored procedures and function how to use.

We will definitely talk about it later because it has the powers to execute queries against a database

or more than one databases.

It can set permissions or tables procedures.

And we know this can be a scenario wherein one particular table is created, which I don't want anyone

else in this organization to see so I can create some permissions, some rights so that only I can access

that data and only I can modify that data.

So this is the part where we were talking about data security and data privacy.

So that's when you will be of great help to us.

Moving to next.

No, just as I told you, that sequel is standard language.

It is standard, but there are different versions of obscure language.

So to be compliant with the agency standard and standard is one of those standardization language,

which we will follow.

But again, the problem with that is that they all support the major commands, such as select update,

delete, insert, where these are very common commands which can be used all over the platforms on different

platforms in a similar manner.

It works out in a similar manner.

That would be one or two, maybe more than that, commands which are available only for a given database,

but in four different databases.

It might not be a.

To start with now, we have completed what the school does and what is the advantage of assuming no

introduction to RDBMS, a small introduction of the relation between Asuman and RDBMS, how these boys

are going to be a part of our course throughout.

I will give you a brief introduction for that.

I give you my chance for relational database management system.

It is the basis for rescuing and for all modern database systems such as that is my sequence over provided

by my Microsoft.

We have IBM DBE do we have Oracle, MySQL, which is an open software and Microsoft access for all this.

The base will remain the same.

That is secured for all the relational database systems.

The base will remain the same.

So if you are Master Eskew and you're very much my student in school, to use it on all different platforms

as well.

The data in RDBMS is stored in database objects called tables, as we have already discussed the data

that is being stored.

It is in the form of a payment to the Verizon data structure.

You will find your data within it in a structural format.

A table is a collection of related data entry, and it consists of columns and rules, which I've already

told you as columns are referred to as fields or attributes when the rules are Dabbous or records.

Moving to next Monday, a school process now we have understood that what is a school we have understood,

we have understood RDBMS not let us just try to force us to visualize it.

How does our school query is going to be performing inside the system?

So when you are giving an Esquibel command for any RDBMS, the system determines the best way to carry

out your request and sequel.

InGen figuring out how to interpret the task so it is as good as I am giving one command in my language

and there is some translator in between, that is some engine in between, which is translating this

command into another language, which is very much understandable by the other end of the system.

So let's say I'm talking to my friend.

I can speak only one language.

I'm speaking in that language.

There is a translator in between which is translating this language into the other languages, which

might which might then get interesting.

So that exactly is what is happening here.

Equal that giving giving some kind of command, which is very much user-friendly.

It is more of an English structured language.

So we understand the command.

But how do our database understand that so far that we have is different components.

We have query despatcher, we have optimization engines, we have classic query engine, we have a school

query engine, etc. There are many more, but we'll discuss a few in.

Just so what happens is once you have given your school query, it goes to the query language processor

there, it will pass and optimize the command that you have given to the database.

Now that optimized advised query will come to database engine.

This DBMS engine understands that exactly what information is required by the user, what it does,

it contains the physical database.

It retains all that information that I want and it will get back to us in the form of of you.

So this is the basic process that would be followed and this will be more or less the same for all the

platforms, let it be in the sequel, my sequel or Oracle or whatever.

So the process of what some are more or less remain the same.

But this is how our Gwenny is being translated to the physical database.

And from there we are getting back the data.

Moving to next, we have asset properties, so when we talk about databases, it is necessary that we

need to understand what asset properties are.

OK, so to start with a sense for a city, it makes sure that the entire transaction takes place at

once or doesn't happen.

So consider the bank example, your.

This example is very unique, and it would be very helpful for you to understand that what exactly these

properties mean.

So what is happening here is that.

We'll talk about every property one moment, so it is a mess.

So what is happening is that there are two ways either complete the transaction or just don't start

at all.

Just go back to the original of the original.

It was by this we mean that either the entire transaction takes place at once or doesn't happen at all.

Let's say there are five transactions to be carried, but there is some system failure after my third

transaction.

In this case, there are two things that are to be done.

Either execute two instructions and then commit your data, which is not possible because there was

a hardware failure.

So the one thing about that transaction, return and reward those three transactions also.

So again, the database will be back to the position where it was originally.

So hydrophilic has not stopped our data flows, has not the details in our system.

So which is a very good property of a database, which doesn't happen when you are using a file structure.

By this, we mean that either the entire transaction takes place at once or doesn't happen.

I don't that is normally that is transactions do not occur partially.

Each transaction is considered as one unit and either runs to completion or is not executed at dawn.

It involves following the operations.

A board and a board means if transaction and what changes made to databases are not visible.

Government means a transaction, changes made out of.

So basically, is this all or nothing rule, we will do one thing, we will try to understand the example

that is given to us now.

Consider that these two transactions consisting of the one and we have to use what we have to do is

we have to transfer 100 rupees from account to account.

Why?

So overall, my money, even if I runs 100 rupees, I have to have seven and piece in my bank.

OK, considering it isn't a very ideal situation that there are only two accounts in my bank and I have

700 or 500 with Mexico, 200 with my account, I have to transmit hundred would be some extra way.

My daughter still should remain seven hundred.

So now you're let's say if the transaction fails after completion of T1, but before completion of the

do so you had what is the purpose is that.

I have to transfer 100 rupees to account, to my knowledge, say my hands are deducted from account.

But just before it got added to account, why there was a hardware failure.

So now the system has to roll back everything and it has to get back to the original position that this

extra, again, had 500 rupees and we should have 200 rupees.

You will never see that it says 400 rupees because it got successful and then there was a hardware failure.

So why is that to do under?

This will never happen because this is again, inconsistency with data database does not allow.

So this 400, which got changed in X will again be reverted to 500 in case of failure.

But if everything goes right, then after deducting rupees from X second, I will have 100 rupees in

my account and after adding hundred to my account, I will have three hundred rupees in my bank account,

in my account, which means my controllers are going back to 700 rupees.

That means is consistent.

So that is what has been written here, this results in an inconsistent state that I told you that excess

water and minus two hundred rupees.

That is, if my transactions are going to get partially, that will not happen in any case.

Therefore, the transaction must be executed entirely in order to ensure correctness of the domestic.

So either completed a complete all the transactions or just do not complete anything or just not executed

anything, that's what Thomas Ities.

Next, we talk about consistency now consistency is the most important property, because when we are

dealing with some important bank related things or some organizational data, it is very much important

that all your updates are consistent throughout in all your tables.

So what consistency means that integrity constraints must be maintained so that the database is consistent

before and after the transaction.

It refers to the correctness of a database.

This is more like similar to a.

Now, what we're talking about are trying to focus yet is that the total amount, as I mentioned before

and after the transition, must be maintained.

So before my transition, my total was seven hundred rupees, five hundred and two hundred on my account.

So many people were 700 rupees after some transactions within the account.

My again today should not change, which shows me that my data is consistent.

And after 31 and people, my total is back to seven hundred and three hundred and Viacom, which shows

that my database is consistent.

Inconsistency would have occurred just in case, even complete, but they do face.

As a result, this transaction is incomplete overall, but right now, as you can see, we have a consistent

data in our demand, so we are good to go with consistency.

Next we have for discussion is isolation the third property of asset properties.

This property ensures that multiple transactions can occur concurrently without leading to the inconsistency

of databased transactions occur independently without interference.

Changes occurring in a particular transaction will not be visible to any other transaction until that

particular change in the transaction is returned to memory or has been committed.

This property ensures that the execution of transactions concurrently will result in a state that is

equivalent to a state that used these red excluded serially in some order.

We will go to the example.

But before that installation is the most important property considering the bank example.

Again, let's say that there is one account X and then there are two people, Y and Z.

Both want to transfer some amount to my ex account.

So in that case, what happens is that.

The execution of Y two, X and Z two X has to happen, even if it isn't happening concurrently, there

shouldn't be any Ghostery in the sense that when one transaction, when I was performing its action

of depositing some amount to account, it did not know that Z was doing the same thing at the same time.

But that should not change the consistency of my database.

In that case, all the operation should be working in isolation and Z should only come to know that

the Y has deposited once it is committed.

So the changes will only be a good enough final state in our database once it is committed so that Gammick

command is very much necessary for our transactions to be made available to other transactions.

So that's what we're trying to focus here on, going to the example, let's say we have X equal to 500

rupees per transaction fee and we have equal to 500 now considered to transaction fee and the could

supposed has been executed will our way.

OK, so that means it has been executed.

OTTOWAY Then the court starts as a result, interleaving of oppression takes place due to which the

court reads correct value of X, but incorrect value of life.

So what is happening here is that once you have read write X here, you have four even entropies.

Now your value got updated.

That does it get multiplied by hundreds.

So your ex has 50000.

Now what you will try to write that value into our account.

Look into my X value is right now fifty thousand at the same time.

What is happening.

My decoders is also trying to read the same data.

OK, so you're it was 500 even it was 500.

You're my value for exchanged which got up to 50000.

You're my value for y changed by was 500 rupees.

So it 500 rupees again back to transaction be it then.

Now at the same time it updated X to fifty thousand while my Z equals plus why was being performed with

500 plus 500 rupees.

So you're at this stage Vidas Decode does not know that X has been updated and hence it is using the

old value.

So what is happening here is that.

The team got this particular schedule, this particular transaction is reading the correct value of

X, but then it is reading the incorrect value of Y, and some can be computed as just take this example,

because X plus why is equal to 50 or.

I'm so sorry.

That is a mistake.

As white as I told you, it is 500 plus 500.

OK, and then.

It is trying to update that data, so you're the thing happens is that it will not be able to read by.

Because your wife was 500 rupees and Bill, then it came to the stage.

So both the transactions were not aware of the updates that were being made because they were not committed

until then.

So for ICO to read the proper data off, explain why it is mandatory that those chandy should commit

to using the database.

Once that is done, we can make sure that whatever transactions that are happening concurrently are

still happening correctly.

So that is what isolation is about.

So the basic focus of all the asset properties is that to make sure that there is no inconsistency in

our database.

That is the major motto of the asset property.

Hence, the transactions must take place in isolation and change should be only it should be visible

only after they have been made to the main memory.

So as I told you that it is necessary that whatever changes we are making to the database are supposed

to be updated, are supposed to be committed.

Only then if you are trying to read the data, then it is correct to read it.

And in that case we will.

There would be no inconsistency.

The final property of cities durability, not this property, ensures that once a transaction is completed

execution, the updates and modifications to the database are stored in and returned to desk.

Now, your desk by basically mean that the main memory and they persist even if the system failure.

So let's say I have a bank organization, all my operations are done at the end of the day and suddenly

all my comics are also completed.

Until then, that means I know already a bigger my database with the updated data, with the more defined

data.

But now what happens is that there is a system failure, not in spite of that durability.

Property will make sure that my database is not corrupted or it is not left off.

So that is where this property comes into the picture.

Even if there is a system failure, my database is safe to be accessed whenever I am retrieving it from

system, recovering from my failure.

So the acid properties in totality provide a mechanism to ensure correctness and consistency of database

innovations, that each transaction is a group of operations that act as a single unit produces consistent

results in isolation from other operations and updates that it makes a durable disorder.

So basically, the only focus of acid property is around the consistency of our database, which is

the need of the hour, because we cannot have our database inconsistent because that is the case, then

there is a lot of tedious work which is involved.

And again, we are not able to solve the problem, which we faced infrastructure, but everything is

being taken care of.

We are using a database.

Next, now, before visualizing before starting with celebrities, it is necessary that we visualize

how our database is and for that visualization of database we have to model.

Now, what does this eHarmony?

It is an entity, relational model.

It is a high level conceptual data model.

So exactly.

With this diagram, you can come to know that what our database looks like, what our data structures

we are storing, what is the relationship between them?

So this gives us a brief idea about our database.

So I'll model it is a high level conceptual data.

More than a year modeling helps you to analyze data requirements systematically to produce a very design

database.

So it is very much necessary in organizations.

Also, what happens is that initially an architecture is created that is a model is created using which

they form a database, because this is a this gives a rough idea that how exactly begins to our data

and how systematically or in which we can store our data.

So this is a very mandatory step whenever we are creating a new database.

So this becomes the first step to our modeling.

That is, the entity relation model represents real world entities and the relationship between them.

And in the later part of the video lecture for today, I will explain what exactly is and indeed what

is a relation, what are the attributes?

What are the associations?

So we are going to cover this.

But for now, this model, it just represents different aspects.

So let's say there is some company considering Amazon for us right now.

We have categories as it was it the Amazon Bantry or was it Amazon Prime, was it Amazon Fashion, whatever?

So we have this category section.

This is one table.

So one table is one entity for us.

And it is something related to a thing, a place on an even.

So it is generally why is this your diagram uses that because it is a best practice to complete your

modeling before implementing your database so that you come to know that if there is some missing attribute,

that is one missing column you can tell, then how do we relate them?

How do we access our database?

Also, if someday I want to check that, how do I relate these two things together?

How do I see these two things together?

I need to find out the relationship between them.

So from this, I come to know that there is some relation between both these entities.

Entity protect an entity particular's.

So more children, children, lezginka requirements systematically to produce a well designed database,

so it is considered a basic practice to complete your modeling before implementing a database.

So each diagram displays the relationships of entity set stored in a database basically just shows you

that how are two different events related to each other just by looking at the diagram?

So we can say that Ideograms helps you to explain the logical structure of database's, at first blush,

look and diagram looks very similar to the flowchart.

However, your diagram includes many specialized symbol.

And its meanings make them all unique.

So even the arrows that are being used here, they have a particular meaning to it, which helps us

understand that.

What kind of relation?

The sharing, is it one too many based on cardinality?

We will talk about it more later in the video.

For now, the diagram, it helps us understand the meaning of the relation between the tables.

The basic purpose of your diagram is to represent the entity, framework, infrastructure.

So this basically helps us understand then how our database will look once we have implemented and for

which we have to come up with a diagram which shows all individual entities, that is Esperanza's product

on this particular product, categories and categories in our case, for example.

And we need to show that how these different entities are related to each other.

Now we can see that color and categories are not directly related, but there could be a possibility

of indirect relation being built to them between them.

So that is where we need to make a very optimum EMR before implementing our database.

Now, there are a few facts about this morning that we are going to.

Learn about your model, it allows you to draw the database design, it is an easy to use graphical

tool for modeling data, as you know that it is a very much graphical design you will be able to see.

It is a graphical interface of your database.

It is widely used even to date and is being used and preferred to use for our database design.

It is a wide representation of the logical structure of database.

It helps you to identify the entities which exist in the system and the relationship between those entities.

So every time if I want to find out the relation between two different tables, I don't have to see

and see.

I checked the data individually.

For that, I can just come back to that model.

Therefore, the relationship between them and I can go ahead and write my queries.

The saves time.

This is why he had more than his required.

Now, there are different components of the program, just as I told you while we were talking about

the model relationship, DIGNAM, there are three main components.

One is entities, attributes and relationships.

So, as you can see, God and a person, these are entities.

So basically in your database, how it will look at this person that is, let's say customer or graduates

that will be on one table.

God will be another, David.

So these are these are basically tables to us, individual things, event places whatsoever next morning

to attribute water attributes.

Exactly.

So I didn't do nothing but Gollum's, which I had already mentioned.

So now Transaction's is an individual.

This transaction's has different attributes, transaction number.

We have amount we have right now.

What are these attributes?

These attributes together define the entity.

So let's consider this example.

You are my entity was a graduate student.

Let's say one of my attributes is name.

And under that we have as Jack.

So I know that name is the attribute which is defining my identity.

So that becomes my attribute in DiGRA, attribute defines an entity, entity alone can be enough to

understand what exactly the downlink data has in it.

So that becomes attributes for use, which is basically defining your entities.

Next is we now know that there are some entities, we have some attributes that define those entities.

There could be multiple such entities.

Then there has to be relationships which connects to different entities.

Let's say if God and entity, these are two different entities and the relationship between them possibly

could be this car belongs to Jack or probably some other person.

So there is some relation between that which can be represented using some relationship cardinality.

As I told you that.

What is the relationship between them so mandatory?

One is basically one, which is one.

That means there is a one to one relationship.

This car belongs to Jack.

Jack has this gun.

So that is just one to one relationship.

One too many, Jack has many guards, all these cars belong to Jack.

So that is one to many relationship Jack is just one person, his association with different gods is

many.

That is one too many.

Then we have option and one that means there's a possibility Jack has just one God or Jack has more

than one God.

Then we have optional many, which means that there could be a possibility of having more than one.

So that becomes the option of many.

Next, and also there are particular symbols, as for many anyone, this is the way we need to connect

the entities.

This is the way we need to connect for many, many, many relationships.

This is for optional one.

This is for optional.

So basically, for many, this is any presentation.

And if it is optional, you have to circle before it.

Now we will learn about the best practices for developing effective ideogram, because if your ear diagram

goes wrong, your database is going to give you wrong output.

So it's better that you have a very precise, correct ear diagram that you for which initially the first

most important point is eliminated and needed entities or relationships so that it can never happen.

The two entities are repeated.

That should never happen.

That is the first thing you need to have everything as unique in your Digo, let it be entities or let

it be relationships.

It has to be a unique relationship.

You need to make sure that all your entities and relationships are properly labor.

Of course, this is very much required because what happens is that if you don't know exactly what this

entity is, you have not labor, then you will never understand.

Then how is this related to the other entities?

So it is very important that you name those entities and you also label the relationships as you label

them, which kind of relationship it shares with others.

This will help you understand when you implement your database using the same program.

There may be various valid approaches to an area, you need to make sure that your diagram supports

all the data you need to store.

So basically your diagram is a dummy database.

Then you need to check that whatever data you are designing to store are being stored in the same format

you had thought of, and not that any one of the attribute is being missed.

You should assure that each and the only appears a single time in the air at this point also matches

with the very first point.

When we are talking about eliminating redundant entities, it should never happen that a single entity

is being reported more than once.

If a single entity that is concern, for example, customer needs is written twice in your database,

that definitely is redundant data and does not require an instant relation.

Could have been built with the same paper.

No name, every relationship and an attribute that represented on that diagram, so labeling is another

important thing, never going into relationships to each other.

Obviously, there is always a relationship between two and entities.

Two relationships are never related to entities are related.

You should use colours to highlight important portions of the aerogel so that what happens is when you

are presenting some diagrams to somebody else, it should effectively show that which part you are focusing

the most.

But that also at the same time, you need to make sure that you haven't missed out on any of that.

So these are two best practices you can use before implementing a database, which will give you an

effective result when you see your database storing the data the way you want to do it.

Now, you have, let's say, created you have created a database, now comes is we have to normalize

the database.

So this normalization is also taken care of when you are creating an illegal.

But how do you understand that normalization and where it is required that we need to understand?

So what is this data?

Normalization data database normalization is a process of efficiently organized data in a database.

Normalization takes care of redundancy.

It eliminates data dependencies.

So just as it as it is written, eliminating redundant data, for example, storing the same data more

than one day.

This is redundant that we are depending on every individual able to store every information.

This makes our table more inconsistent, more prone to inconsistency.

To avoid this, we have to take off every redundant data and have to make every call Lambro record and

attribute unique.

In our database, we have to ensure that data dependencies makes sense.

It should not also not happen that there are two different people who are related to each other, but

there is no common factor relating them.

So that should also not happen.

There should be a connection between them.

Both these reasons are worthy goal is to reduce the amount of space a database consumes and ensure that

data is logically stored.

Nomination consists of a series of guidelines that help you in creating a good database structures.

So it is not that you have to explore on normalization, but there are some rules set in a database

like one and two and three.

And if only three enough is enough on the one and if you will come, then what exactly you need to do

to your database or to your model to make it more normalized under doing.

There are certain rules that you can follow who identify what kind of changes you need to make before

you are taking them to make it more normalized and more structured.

So what happens is that if your data is redundant, you are just using a DeMain memory.

And the main memory utilization, we have to ensure that we have eliminated all the redundant data.

Normalization guidelines, guidelines are divided into normal forms, just as I told you about one and

two and three, and think of a form as the format or the way or the structure is laid out.

You have to basically follow those rules mentioned and that every normal form and you have to follow

that.

And do you make the changes in the database to make it normalized?

The aim of this normalization is to organize the database structure so that it complies with the rules

of force.

Normal form, then second normal.

And finally, the third.

So basically, it will make your more structure.

And for that structural aim to achieve, we have to normalize it with the ruleset set that has been

given by database's.

Now, in our calls, we are generally we are going to use my Cequent, there are many such platforms

available, such as there is a mass access, there is a sequence of it.

We also had SharePoint, which is another form of database, or we have Hive, but then basically we

are going to use for our cause.

It is an open secret database.

It was developed by a Swedish company.

It is pronounced as my sequel's or my school, though we were compatible with.

It is my sequel supporting many different platforms use, including Microsoft Windows.

This is also available for Linux, Unix, Mac Books, the Mac OS, Macintosh, and the major thing is

that it has both the versions.

It has what our requirement since we are going to cover majority of the basics for us, the basics of

secure and that is of that is a free version is enough.

So I would suggest that before we start with the next lecture, you download and set up your mind sequel

server, which is available for free.

And along with the sequence where you would also see that there is some dummy data which we will be

using in our actual structure.

They already have some tables provided to us which will be using to understand the basics.

Equal queries or even help will seek help of the same database to understand the assets and liabilities

of sequel query language.

To get back to my school, it is a very fast minded, started multiuser and is also very robust if you

in a very correct manner.

My school is basically used for operational databases.

If you think that your data is moving towards big data, that there's a lot of data is being inserted

into your table, then you probably might have to migrate from high school to a bigger server until

and unless you have updated the server capacities or memories.

But for our Ilocos, we need not do anything of that as we are going to learn of our basics, of a skill

for which every version of my speech should be very much okay to do.

No, the advantages I have already BPU about the basic advantages of my school.

Other advantages are that it has many features, stored procedures, you you can make functions.

You can also schedule your jobs that you are creating on an everyday basis or monthly basis the way

you prefer to.

It gives a very high performance based on data storage, high availability and scalability and flexibility.

It runs on anything, as I told you, that it is also linked with the Microsoft platform.

So it is quite flexible enough or it has a robust transactional support data, warehouse strength,

strong data protection, the security or DOMS as in the ground, and revoke access that is available

within my school, which will help you understand, understand the data security.

But it is very easy to manage and it is an open source.

So with 24/7 support, you can visit my secret dotcom just in case.

If you have some issues in downloading, you can definitely contact them also to the lowest total cost

of ownership.

Generally it happens.

And if you want to learn in school, my school is the best way to start with as it gives you an overall

idea of how the data is, it gives you an idea in the data domain.

So it is a very good step in your career.

If you're starting with a school, you may start with my school as it is a stricter form of standard

sequence which will help you create optimum and good performing school grades.

So, yes, I would like to thank you for attending this lecture arranged by Youngbloods that just a

few more courses.

Thank you.