 This was the good thing about a dynamic website is that once the site is running, it will keep on running. It does not require a lot of intervention and maintenance because as the data is loaded in the database, or if the data changes in the database that is reflected in the dynamic pages. But still you have to look at certain aspects of maintaining and keeping your website up to date. And what are those things? I will look at this over here. So you see that these are some of the things you have to be looking at, okay? And then of course, testing also, because there is no such thing as an unchanged or constant website in today's domain. The time of the static websites is gone. Even if it's a static website, it requires certain updates. It requires certain changes over the period of time. It is never ever completely static. There may be some of them, but that is not a rule. So let's look at this more detail. So managing your website from afar, from a distance, now usually it is the ISP who is performing their people are accessing the database and maintaining the website along with the database, which is of course, not with reference to the application. Remember that. Few people have full access to their website, few people, okay? And of course, when they maintain their websites, you may move your database back and forth between your computer and the computer of the ISP or the database service provider. Just like the HTML pages, just like the HTML pages, right? So if you are maintaining your own website, now there are two things over here. Number one is that you may be moving your database back and forth between your ISP or the database service provider and your computer. That works for small databases, for example, Microsoft Access. In other cases, what you might be doing is you might be accessing the database at the ISP. When the database is very large, it may not be movable. So you are making changes over their database by accessing your ISP for large databases like Oracle differences are there. So database housekeeping, DSP performs the routine backup, okay? It could be a daily, fine. But the thing is that there may be many, many cases, which I have listed over here in which you might be interested and you might be required and you might need to do the backup on your own, okay? Not leaving it on the ISP or the database service provider, ISP as in internet service provider. Now say, for example, you are a university and it is the registration time and the students are registering for the courses, adding and dropping courses, right? So in that case, it is not wise to wait for a whole day to make a backup while the system might crash for some reason. So looking at hourly, hourly backup, right? Or you may want to place the backup at a certain location. You would not like the backup to be with your ISP, the DSP, but you want the backup taken at your end and then locating that backup somewhere else for reliability reasons. That is one thing more. And of course, if you are taking the backup by, it says the guest book and you take the backup by moving the guest book, okay? And moving an empty database over there, that might create link failure. That might because somebody might access your website while you are performing this task. The best approach, the better approach is to point it to an under maintenance page and once you are through, then you point it back to the actual page. You have to be careful. Why careful? Because you don't want the disarray in your website to be notified to you by somebody else because once you are on the internet, your typing mistakes, your erroneous data, or whatever you have placed, that becomes public. And it is not good, it is not good to be notified of the errors, omissions and corrections by somebody else. So have a schedule for database maintenance. It could be a minor if it's okay with you or it could be overall. It depends upon your requirements, it depends upon your domain. Remember that this backup is sensitive. By which it involves people from the ISP, it involves people from the administration, from the database, from the web developer team, from the so many different people are there. So you have to be careful. And of course it could be a permanent fixture or it could be routine, it is up to you. So changing, when you make a change, improper minor changes can bring down a major system. There are many, many stories, the system down for hours, the system down for days and so on. Why? Because when the change was made, it was not tested. You have to be careful. And changes are always there. And in case of emergency, streamline the changes because in case of emergency, loop holes are left to be exploited later. You have to be careful. And finally, the person who makes the change is not the person who is testing the changes. That's all I have for you in this world. Thank you very much.