You should go to http://www.mysql.com and look around for a package called MyODBC. It will allow you to connect your Windows machine to our MySQL server via ODBC.

NOTE: Outside connections are not allowed to dc1-mysql-02.kattare.com.

The basic syntax is as follows:

mysqldump -h <hostname> -u <username> -p --opt <database> -r backup-file.sql

There is a "Change Password" link in the phpMyAdmin software available at:

https://www.kattare.com/sqladmin/

Just select your server, log in, and it should be on the main screen in the list of links.

Alternatively, via the command line interface:

set password=password("yourpassword");

You are not logged in. [log in]

You are not logged in. [log in]

FAQ entry generously donated by Chris Beels.

This tutorial assumes you are already running a Tomcat context, and perhaps even have used JDBC to get connected to your MySQL. You're looking for a faster, more robust option, and you've come to the right place.

Tomcat provides an excellent example here but we've provided some kattare-specific pointers here as the connection section of the server.xml is significantly different.

When you signed up for Kattare, you received a MySQL account email that looked like this:

Database Server: SERVER_NAME
Database Login: LOGIN
Database Password: PASSWORD
Database Name: DB_NAME

Make the following changes to the Tomcat docs example
- change the username and password from "javauser/javapass" to your "LOGIN/PASSWORD"
- change the URL parameter to jdbc:mysql://SERVER_NAME:3306/DB_NAME?autoReconnect=true

Restart Tomcat with the new server.xml and web.xml changes from the docs, and you should be good to go.

Here is the basic syntax:

mysql -h <hostname> -u <username> -p <database> < <backupfile.sql>

You can also do:

mysql -h <hostname> -u <username> -p <database>
create database <database>
use <database>
source <backupfile.sql>

We ask that it be kept to 30 or less. Under high load to the MySQL server we may be forced to kill connections numbering over 30. We don't want to have to do this anymore than you would want it to happen, but it's necessary to keep MySQL running smoothly for everyone.

If you find that you are needing more connections than that, on the order of 31-500 connections, please talk to us about a dedicated server.

You are not logged in. [log in]

There are two possibilities:

The first is that your connections have been idle for 8 hours or more. In which case MySQL automatically kills them off.

The second is that you are using more than 30 simultaneous connections. In which case MySQL will randomly pick connections to kill.

You are not logged in. [log in]

You are not logged in. [log in]