If you have a dedicated database server and the partition with the MySQL database fills up (or starts getting low), you can move your MySQL databases to a different location.

Let’s say you want to move the database to /home/mysql

There are times when you need MySQL to be able to bind to more than one address. In this particular occasion, I was running Nagios locally on the same system as Drupal, my content management system.

Installation of Microsoft SQL Server requires that it have certain permissions in order to run on the local system.  Some people choose to have it run under a Domain Account that has Administrative Access.  And at one point (especially SQL Server v6.5 and SQL Server v7.0) it was much easier to install if you used an Acount that had Administrative access (i.e., Local Administrator Group role).  I even believed at one point that using a Domain account made it easier for SQL Agent jobs to export data to remote file shares.

Murphy walks among us. You know Murphy, the famous "optimist" who helps make every bad situations even worse? Well, after a disaster has occurred is not the time to figure out how and where you need to recover your data. Sure, we practice (ok, hopefully we practice!) recovering our database(s) from tape or disk. And during our testing we restore it into a test database or, if we’re lucky enough, into a test server. Great, but how does the application connect to the recovered database if we’ve run into a massive hardware (server) failure?

There are a variety of ways to change your MySQL password.  One of the easiest is from the command line.  You can use a command like:

 mysqladmin -u root password yourrootsqlpassword

to change your password.  The above command changes the password of the acount root to yourrootsqlpassword.