Most modern web applications today interact with databases, usually with a language called SQL. Lucky for us, this language is quite easy to learn. In this article, we are going to start with some basic SQL queries and use them to interact with a MySQL database.

MySQL is one of the most popular Relational Database Management Systems and there are many web designers / developers who want to enter the world of the databases because majority of the websites these days stores the content of their pages as well as many other things like logins etc. inside of them. From this series you will learn what databases are and how to use and interact with MySQL Database Management System using phpMyAdmin as well as SQL statements via any sort of interface.

This Tutorial shows you how to set up an automated Import/Export in SQL server 2000.

This enables you to download/upload data from/to your live websites at set times of the day without having to manually run it yourself.

This is a good option for running during the early hours to bring live data from your website down to your local machine to provide a backup.

Most users concentrate on MySQL's databases and tables — after all, that's where most of the action takes place — and they don't usually look deeper to understand how it handles access privileges, passwords, and security. This approach is usually more than adequate for most development activities — unless you happen to be a database administrator whose job involves setting up and securing the databases against unauthorized usage or malicious mischief.

With that in mind, this chapter examines the MySQL access control system and throws some light on the MySQL grant tables. These tables, which are an integral part of the server's security system, offer database administrators a great deal of power and flexibility in deciding the rules that govern access to the system. Additionally, this chapter also discusses the management of user accounts and passwords in the MySQL access control system, explaining how passwords (especially the all-important root password) can be modified and how to reset a lost superuser password.

"SQL Injection" is subset of the an unverified/unsanitized user input vulnerability ("buffer overflows" are a different subset), and the idea is to convince the application to run SQL code that was not intended. If the application is creating SQL strings naively on the fly and then running them, it's straightforward to create some real surprises.

We'll note that this was a somewhat winding road with more than one wrong turn, and others with more experience will certainly have different -- and better -- approaches. But the fact that [we] were successful does suggest that we were not entirely misguided.

There have been other papers on SQL injection, including some that are much more detailed, but this one shows the rationale of discovery as much as the process of exploitation.

If you ever wanted to start using the open source MySQL server application on your computer, this article is for you. It will show you how to obtain, install, configure, and test the MySQL server on your system, whether you are running UNIX or Windows.

One of the nicer things about MySQL is the fact that it’s an open-source application licensed under the General Public License (GPL); users are encouraged to download, modify, and use it free of charge. This open licensing policy has played an important role in MySQL’s widespread acceptance and popularity in the developer community; according to statistics published on the MySQL web site, MySQL is in use at more than 4 million sites worldwide, with more than 25,000 copies of the MySQL database server downloaded every day!

Lately, database security issues have been flooding the media and Internet news-wires. First with the Slammer worm and most recently criminals accessing over 8 million credit card numbers.

So [I] sit back and say to myself, "Did the sysadmins fall asleep behind the wheel?" As the internet has boomed and we've increased our reliance on the convenience and relative low cost of web-enabled information systems, we have become lazy in our implementation of basic security practices.

A utility like mysqldump is very useful for backing up MySQL data and table schema. However, backups are usually made only once a day or at some other regular interval. If data is lost on your system several hours after the last backup is completed, you may not be able to recover it. There are a few methods by which you can continuously protect data. One method that you can use to be able to recover interim data is to use binary logs. A binary log will record all SQL transactions on a server as they are executed. Some administrators try to minimize any logging because of concerns about server performance. However, on average, binary logging will slow a server by only one percent. In return, though, it allows for up to the minute data recovery.

This book is for the long-time MySQL user who wants to know "what's new" in version 5. The short answer is "stored procedures, triggers, views, and information schema". The long answer is the MySQL 5.0 New Features series, and this [tutorial] is the third in that series.

What I'm hoping to do is make this look like a hands-on session where you, as if you're working it out yourself on your keyboard, can walk through the sample problems. To do this, I'll go through each little item, building up slowly. By the end, I'll be showing larger views that do something useful, as well as some things that you might have thought were tough.

This 67 page guide is for long-time MySQL users who want to know "what's new" in version 5. The short answer is "stored procedures, triggers, views, information_schema". The long answer is the MySQL 5.0 New Features series, and this book is the first in the series.