← Previous lessonFree lesson 2 of 3 · lesson 2 of 62Next lesson →

Unlock all 62 lessons of Everything about Database 2.0Full course ₹40,000 · paid

Price & syllabus
Free lesson · 20 min · no payment

Installing XAMPP, Creating a First MySQL Table and DBMS Components

A free lesson from Skill-Lync's Everything about Database 2.0 course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Module 1 - Downloading xampp, creating 1st table, components of DBMS”

What will you learn in this free Everything about Database 2.0 lesson?

The instructor shows how to download and install XAMPP, start Apache and MySQL on port 3306, and use phpMyAdmin to create a first database and table with two rows. The lesson then describes DBMS users such as the DBA, developers and end users, three levels of data abstraction, data independence and data models.

  • Installing XAMPP and starting Apache and MySQL
  • Creating a database, table and rows in phpMyAdmin
  • Roles of DBA, application programmer and end user
  • Logical and physical data independence

What comes after lesson 2?

The next free lesson is lesson 3, “What a DBMS Should Offer: ACID Properties and Databases vs File Systems” (24 min). Later in Skill-Lync's Everything about Database 2.0 course (paid): lesson 4, Module 1 - Types of DB, SQL vs NOSQL; lesson 5, Module 1 - CRUD operation example in MySQL, OLTP, OLAP; lesson 6, Module 2 - Database design, ER model, Entity, Attributes. The full course has 62 lessons (19 h 22 min of video); see the course overview or its price and syllabus.

Lesson transcript

Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.

Now, let me actually show you how we can directly work with the database, just like the single-tier architecture which I talked about. We can do that on our system, and that's exactly what I'm going to show you. You can simply type XAMPP, this is a software which we are going to download to work with the MySQL database management system. And the first link which we get is from apachefriends.org, and this is where you can actually download the latest version of Apache Friends. So, I'm going to download it for Windows, for a 64-bit Windows system, which is the one which I have.

Once it is downloaded, then I would run it, and it has a simple installer, and once it gets installed, you would simply be able to run the XAMPP server on your machine. Now, once you have XAMPP installed, you can simply open its control panel, and you would have, you know, Apache, MySQL, and other options. So, what I would do is, I would start Apache and MySQL. This is the database which we want to use. MySQL will, by default, start on the port 3306 of your machine.

So, make sure that this port is free for it to use. If you have any other software working on the port 3306, make sure to actually stop the software so that your MySQL server is able to work on this particular port. Now, your database is working, and we do have this Apache server which has started. Now, in your Chrome browser, you could actually simply go to localhost phpmyadmin, and this is where your phpmyadmin would open up. This server is on 127.0.0.1, which is the IP address of your localhost, and this is where you have your phpmyadmin software working with the MySQL database, which we have on our machine.

So, this is the dashboard, which we can use to directly work with the MySQL DBMS. For example, using this new word over here, I can actually create a new database. So, when we click on this, we can just add a test database, and I would click on create, and it says that, you know, we cannot create database test because that database exists. And I indeed had created a database called as test, so I would not do that again. Let's say I just want to create a dummy database, so I would call it dummy, and here I will be creating it.

Now, here, my dummy database got created. So, what is happening is that using this software, I'm directly able to work with my database, and I'm able to create my database. I'm able to actually, you know, create one or more tables because I directly got this option of creating table. So, I would write, let's say, first table, or I would name it this way, first table, and it is asking me, how many columns do you want? Let's say I just want two columns right now. So, now it actually created a table with two columns, but then it's asking me the names of the columns.

So, over here, I would type some dummy names. So, I would just write first, second, and maybe each column would have a type of wherecar. Wherecar is a simple string which we would use in a programming language, and what is going to be the length. Let's say for the first, I would put 20, and for the second also, I would put 20, and then I would simply save it. Now, we have our first table with two columns, first and second. If I want to check the data in these two, I can simply go to browse, and now we can see that there is no data over here because we do not have anything in our first and second columns.

If I want to insert some data, I can simply use the insert option over here, and I am able to insert some values. So, I would just write first row, and over here also, I would write first row. And probably, I can add a second row to the table, and here also, I would add a second row. And when I click on go, we have some processing happening. And when I go ahead and, you know, look up, browse the data, now I have my first row and second row within my first and second columns of the table, which is known as first table within my database of dummy.

Now, this is how I am directly able to work with the database using this software, and this is a single-tier architecture which we would use as developers to work on this. Now, other than phpMyAdmin, you can definitely use any other software like High Dsql or any other GUI-based software which helps you to work directly with the MySQL database, or if you are pretty savvy of the command line, you can simply open the MySQL command prompt on your system, whether you are working on Windows or Mac or Linux, and then you can simply actually just use the query language to create database and to work with data in MySQL as well.

But for ease and simplicity, I am going to teach you from this particular dashboard initially, and then we are going to learn how we could actually do querying on tables and on the entire database based on a query language, which is known as SQL. And you can see that, you know, phpMyAdmin also uses the SQL query language to query things in your data. So here, it actually queried using this particular statement of the SQL language to get me all of this data which is present in my table.

Now, how we can use that within our database management system and within our code is something which we are going to look ahead in our course. Now, what are the different components of a database management system? We would have a hardware which would have, you know, our entire database. We would then have a software by which we can actually work directly with the database. Obviously, our database system is not complete without actually having a data. Then we would have some procedures to work on that particular data so that we can get our relevant information.

We would have some algorithms working on that data, some storage mechanisms. And then we have, lastly, a data access language by which we will be able to access that entire data from the database management system from the hardware. Now, when I talk about hardware, I mean computer, hard disk, any input-output channels for the data or any physical component which is involved before any data is successfully stored in the memory. For example, if I'm running my SQL database management system on my personal computer, then my computer's hard disk as well as, you know, the entire keyboard and all the commands which I enter and my computer's RAM, ROM all become part of the database hardware.

The software component is actually the main component of database management system because that's the program which would control everything. That software, the DBMS software, is actually more like a wrapper around my physical database because that physical database is just stored in an interface, right? But I really need an easy-to-use channel to store, access, and update data. That is being facilitated by the database management system software. It is capable of understanding my data access language. It's capable of interpreting it into actual database commands to execute them on the database.

Also, when I talk about these procedures on the particular data which we want to do, this could include anything like the things which we did right now. We set up and installed a DBMS. We want to, let's say, log in or log out of a DBMS software. We want to manage the different databases within the DBMS software. We want to take backups. We want to generate reports. We want to do many things within with the data which we have. All that procedures would come facilitated by the database management system for me.

And that is one of the components within the DBMS. So you have facility of taking backups. You have facilities of generating reports. You have facility of importing and exporting database. Just everything what you want to do with the data, you would have it in a database management system software. And lastly, we are going to learn a database as access language. The most popular language for database access is structured query language, SQL. That would help us write all the commands to access, insert, update, delete data in the database.

And we are going to learn all of that. Now, remember the users of the DBMS are going to be either database administrators who directly manage the entire database management system. They are responsible for availability of database for all the time for your application. So let's say, you know, you actually open up Facebook, but then you don't see anything, you know, in your wall. Obviously, the database management system fail to provide to you the data. That should not happen, right? So the DBA is actually responsible for all of that, managing the availability of database, managing the licenses, managing user accounts, managing access, so that, you know, no other person is able to access your data of Facebook or of any other website.

Also, DBMS can be used by application programmer or software developer in general to access data from the database in the web application for the end user. Also, an end user is able to access data from the database in a channelized manner in the sense that if you want to follow people on social media, you are able to do that and make the change in the database of the web application. But you can't actually go ahead and, you know, batch follow people directly in the database because you are not allowed as an end user to do that, right?

Whatever Instagram or whatever. Any online facility would provide you with any feature. That is the only thing which you as an end user can do for using or manipulating data on the website. Also, you would be knowing that you generally signed an end user license which helps companies to take permission from you to use your data in a specified legal manner. And that is pretty important for you to accept before using their services so that they have the total control on the data and give you the control of your data as well.

We have been talking so much about data. So let's also talk about how data can be conceptually, representationally and physically stored. So first is the conceptual level in which we would actually probably just draw diagrams of, you know, how we would want to store data. So, for example, I have, you know, my college and I want to store data of students. Probably I can just draw in diagrams that, you know, probably I would want students to give their ID information, name, photograph, address information, the class in which they are enrolled, the subjects, their previous year's marks, etc.

You know, I would just list down these things, draw some diagrams, how I'm actually going to conceptually store the data of a student. Then comes the representational level in which my I would actually create tables to store my data. Now, here is where independence come. There is a logical data independence between these two. Conceptually, I can think of data in any way, but representationally, I would have it in tables. And if there is independence between these two ideas, even if my concept changes, my tables can remain same or would have very minimal change.

Similarly, how data is stored physically in a low-level storage detail on the machine, that is going to be totally different. How, what data structures are used to store that data and how to retrieve them. All of that is totally independent from my table structure, which I created. And this is known as physical data independence. It's just like actually creating a house. You draw a diagram of, you know, how your house would look and, you know, the blueprint of the plan of the house, all of that.

And then you would actually, you know, build the house using brick and mortar. But then, you know, what bricks are used, what mortar is used, all of that is going to be pretty independent than the design of the house, which you have created. Right. So remember that the conceptual level is actually the part of, you know, your entire database, the view of your entire database. Then the logical level or the representational level is where your data is stored and relationships between different data is established. And the physical level is how your data is actually stored, meaning the complex low-level data structures in detail.

So these are different levels of abstraction. You have the physical level and then you have a level of abstraction over there. You as a software engineer or software developer or full stack developer is not concerned about, you know, how data is put in the physical level by the database management system. Probably you are only concerned about, you know, how it is represented in the forms of table. And, you know, maybe let's say you you are working for a company and the manager is also not concerned about how tables are organized.

The manager is only concerned about the conceptual data of the user, which is supposed to be stored in the database and leaves all the rest in your shoulders that, you know, please make sure that it is done properly. But for them, there should be an abstraction of, you know, this is the conceptual data of the user and this is what we can do with the data. Now, when I talk about data abstraction, what is the meaning of abstraction? Just as I explained, abstraction means we are hiding the details which would be irrelevant for that particular user.

So the business owner does not need to know how you have actually implemented the data in the form of tables. You probably do not want to know how the DBMS is implementing the physical or low-level storage details. So all these levels of abstraction is taken care of by the DBMS. However, you want to show the data, whether it's a conceptual level, whether it's a representational level or even the physical level, the database is able to give you that option. And finally, you have your stored database directly on your machine or on your disk.

So we talk about independence, which is capacity to change something at one level of a database without having to change anything at the next levels. We talk about logical independence in which we want to change the conceptual schema without having to change any external schema or any application programs which are dealing with it. So let's say I want to change the way my tables are organized, etc. But then I am absolutely capable of making sure that my application program or conceptual level data is the same and I do not have to make any changes to that.

That amount of independence I do get using database management systems. Similarly, physical data independence in which we get the capacity to change the internal schema without worrying about the physical implementation of data structures which handle the data. So let's say the DBMS for optimization purposes decides to not store data in using a few data structures but using another data structure. We don't care about that because we know that even if the DBMS does change that, then our entire table structure is going to be the same and we don't have to actually make any changes just because database management system has decided to use another data structure to physically store the data.

This amount of independence is provided to us by a database management system. Now let's talk about models. Anyways, we are talking about the levels in the database management system, right? So one is a high level model in which we know how the users perceive data and we are going to study how we could actually design that model using entity relationship diagrams. Then we could also have a low level data model which would actually tell us how data is stored in the computer. We have already studied about a number of data structures which help us store data on in a computer.

We also know that there could be a representational model in which we would understand how end users understand and how data is organized. For example, in the form of tables. Now the main question is how do you choose a particular database model? There are some common and famous database models. One could be a graph based data model. One could be a document based data model. One is entity relationship based data model. Another could be hierarchical data model or network data model or object oriented data model.

For example, the hierarchical model could look something like this. You have your university data and that could be divided between different departments and different offices. Each department could also divide the data amongst various courses, about various teachers and about various students. Each course could also have different data for theory and laboratories. So this is how you would model a particular institute's data using the hierarchical model. You could also actually model it based on graphs. So graphs would have nodes in each of which would be representing a particular entity, let's say a particular student with the ID, name and age.

And each of the students might have some relationship between each other. For example, they would know each other or they would be member of common groups, etc. So this kind of graph model can also be used to actually model your data. You could also use a document model. It could be a simple JSON document in which you would have, let's say, you know, the execution time or a list of attributes just like this. So it could get to any complex level. You could have data in your document in a key value pair model.

You could also have it as an entity relationship model in which you have different entities. For example, this entity user over here and each entity might have its own attributes like this user has name. This user has ID. This user has an address and an age and different entities can be related to each other. So the user entity could also be related to, let's say, the seller entity in an e-commerce website domain and they would have a relationship between them. That's why this is called the entity relationship model.

So we have different models. How would we ever choose which model to use? Now, remember, these data models actually provide us with all the conceptual tools required for describing the design of our database at each level of data abstraction. For example, the relational data model helps us to build relationships between entities, make tables, work with them. And if we feel that our database is better created using tables and relationships between entities, we would use entity relationship model or simply a relational data model. Or if we think that our data should have facilities of functions of encapsulation of objects, identities and inheritance, et cetera, then we might go ahead and use an object oriented approach for storing data.

Or if we feel that, you know, our data is not very well organized, it is kind of semi-structured, I want flexibility in the structure of my data. So I would probably go ahead for using a document based model. So I would put my data in a JSON format or an XML format of document. So I could actually choose my data model based on my use case, how I want to use my data or how I would actually want to work on the data.

Want the rest of Everything about Database 2.0?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full Everything about Database 2.0 course

The remaining 59 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full Everything about Database 2.0 course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.