If your account type includes MySQL databases, then log in to your Web Hosting Plus Control Panel and select “MySQL Databases”, in the “Web Tools” section.
The database name will be the same as the username.
If your account type includes MySQL databases, then log in to your Web Hosting Plus Control Panel and select “MySQL Databases”, in the “Web Tools” section.
The database name will be the same as the username.
1. Using the backup tool from the Web Tools section.
2. Using phpMyAdmin web interface
3. Using command line through shell access
4. Using MySQL Workbench
(1) Using our backup tool
Log into your Web Hosting Plus Control Panel and click on Web Tools. Click to configure MySQL Databases and click ‘Now’ under backup database. Save this file to your local machine.
(2) Using phpMyAdmin
Log into your Web Hosting Plus Control Panel and click on Web Tools. Click to configure MySQL Databases and choose the database that you want to manage. This will start phpMyAdmin. PhpMyAdmin can export your entire database by selecting the “Export” page.
1. Select all tables
2. Select “Structure and data”
3. Select “Add drop table”
4. Select “Enclose table and field names with backquotes”
5. Select “Save as file”
6. Then click “Go” button
You will be prompted to save the dump file on your computer.
(3) Using MySQL command line tools
To use MySQL command line tools, you will need SSH access to be enabled on your hosting account. You can perform backup using the following command:
mysqldump -h servername -u username -p –add-drop-table –create-options –skip-add-locks -e –set-charset –disable-keys -Q databasename > databasedump.sql
To backup and compress your dump file:
mysqldump -h servername -u username -p –add-drop-table –create-options -e –set-charset –skip-add-locks –disable-keys -Q databasename | gzip > databasedump.sql.gz
The commands above will create the dump file in your current directory. You can download this backup file using scp or ftp for your archival purposes. If you perform this command in the public_html directory (or if you move the file into the public_html directory), you will be able to download this file from the web.
(4) You can download MySQL Workbench from http://wb.mysql.com – this will allow you to connect to the MySQL process on the server directly and create a local backup of the data.
There are numerous ways to upload a MySQL database, we would strongly recommend trying methods 2 and 3.
Method 1 – phpMyAdmin
You may use phpMyAdmin to load your database by using the Import link to upload a .sql file or by pasting the SQL script into a query window and executing it. For the latter method -
1. Login to phpMyAdmin with a MySQL user that has been given DBA rights to the MySQL database you wish to load.
2. Then click on the SQL tab.
3. Paste the SQL script content into the text area, and click Go.
If the SQL script contains a lot of data, you might still get away with this by pasting it bit by bit. If the data is simply too large, see the other sections.
Method 2 – Web Hosting Plus control panel restore
In the Web Hosting Plus control panel go to the MySQL Databases page.
On this page is the text “To restore a database which you’ve previously backed up, click here.”
If you follow the link, you can upload a larger SQL file than would be possible in phpMyAdmin.
If the SQL file is very large, please consider one of the other methods below
Method 3 – MySQL Administrator
MySQL offer free software to manage, backup and restore MySQL databases.
The software can restore very large files, and also comes packaged with MySQL Query Browser, which can be used a faster alternative to phpMyAdmin
You can download the software at http://dev.mysql.com/downloads/gui-tools/5.0.html
Method 4 – MySQL command line client
This requires you to have SSH Access, which may or may not be available on your particular package.
Due to the limitations imposed by PHP, phpMyAdmin is unable to load a large MySQL dump data.
You can upload the MySQL dump file created by mysqldump –opt -Q dbname to your home directory, and then execute the MySQL client to load it.
To load your sql dump using MySQL, you can use the following command:
mysql -h mysqlhost -u mysqlusername -p databasename < dumpfile.sql
or
cat dumpfile | mysql -h mysqlhost -u mysqlusername -p databasename
Where:
mysqlhost – The name of the server where your MySQL database is located. You can find this out from the Control Panel in the MySQL Database area.
mysqlusername – Your MySQL User name as created through the Control Panel.
databasename – This is the name of your database
dumpfile.sql – The file created by mysqldump
MySQL Workbench is a GUI for MySQL – it can be downloaded from http://wb.mysql.com. It provides a complete set of drag-and-drop tools to visually build, analyze and manage queries.
Plus, the integrated environment provides:
Query Toolbar to easily create and execute queries and navigate query history
Script Editor giving you control to manually create or edit SQL statements
Results Window so you can also easily compare and work with multiple queries
Object Browser enabling you to manage your databases, bookmarks, and history using a Web Browser like interface
Database Explorer where you can select tables and fields to query, as well as create and delete tables
Table Editor allows you easily create, modify and delete tables
Inline Help giving you instant help access to selected objects, parameters, and functions
The MySQL service for your site runs on the same server as your website, so use your domain (or the IP of your webserver) as the hostname, port 3306, your database name as the username and the corresponding database password as the password.
PHP will run all files with the following extensions by default:
.php
.php3
.php4
.php5
.php4 files will run under PHP4, .php5 files will run under PHP5 by default. .php files will run under the default PHP version (5).
A cookie is a simple name-value pair stored by a browser, often a session ID.
The main purpose of cookies is to identify users and possibly prepare customised web pages for them. When you connect to a web site using cookies, you may be asked to fill out a form providing information such as your name and interests.
This information is packaged into a cookie and sent to your web browser which stores it for later use. The next time you go to the same web site, your browser will send the cookie to the web server. The server can use this information to present you with custom web pages. So, for example, instead of seeing just a generic welcome page you might see a welcome page with your name on it.
Your FTP account may be locked, for more information, consult the article on FTP locking. All accounts are locked by default for security reasons.
Firstly, ensure that you are using a good FTP client – we recommend FileZilla. Some FTP clients make it very difficult to find the settings that you need to change.
Secondly, check your settings. These can be found in your Web Hosting Plus Control Panel, but are typically:-
Server: ftp.yourdomain.com
Username: yourdomain.com
Password: your Web Hosting Plus Control Panel password for that domain.
Ports:- Default
Depending on your FTP client’s settings, you may have more options. Common ones include SFTP (which should be off), and Passive/Active transfers (which should be set to Passive).
Additionally, check your firewall (Norton, ZoneAlarm, AVG Internet Security, etc) – try switching it off and attempt to connect – if it works then the issue lies with your firewall and not with our services.
Finally, take a look at any errors that you see when connecting. A common one is “530 Login Incorrect” – this suggests that your username or password is incorrect. Other errors are fairly descriptive, and a quick Google search will often reveal solutions.
If you’ve installed Ruby on Rails manually, or are using an installation from a previous web host, you may find that your Rails pages do not display – instead showing a “404 Not Found” error message.
This is caused by a missing or incorrect .htaccess file in Ruby’s public folder. This file tells the web server how to correctly understand Rails paths.
Fortunately, this is easy to fix, as we have created a simple script you can run to generate the correct .htaccess for Ruby on Rails. If your Ruby installation is in the somedirectory folder under your home directory, then you would connect by SSH and do:-
[yoursite.com@web224 ~]$ cd somedirectory/public
[yoursite.com@web224 public]$ /usr/local/bin/create_rails_htaccess.pl > .htaccess
The create_rails_htaccess.pl script simply outputs a correct .htaccess file, so you can modify the command as you wish (for example, appending it to your existing .htaccess).
This applies to Windows Hosting accounts only.
You will need to use a DSNless connection which can be achieved by using code with the following VBscript:
set rsEvents = Server.CreateObject(“ADODB.Recordset”)
rsEvents.ActiveConnection = “Driver={MySQL ODBC 5.1 Driver}; DATABASE=databasename;USER=username; PASSWORD=password; Server=127.0.0.1″
…or the following JScript:
var rsEvents = Server.CreateObject(“ADODB.Recordset”);
rsEvents.ActiveConnection = “Driver={MySQL ODBC 5.1 Driver}; DATABASE=databasename;USER=username; PASSWORD=password; Server=127.0.0.1″;