Transferred to new host - importing sql but not working
Permalink
I already transferred to a new host and I didn't read step by step (http://www.concrete5.org/documentation/installation/moving_a_site) until after I transferred :( so I can't login to the concrete5 dashboard anymore.
My question is: what if you didn't disable/clear cache? would that pose as an issue messing up the sql file?
I backed up sql and tried to import it in the new phpmyadmin but it's not working and coming out with an error:
Error
SQL query:
--
-- Database: `c5data`
--
CREATE DATABASE `c5data` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
MySQL said: Documentation
#1044 - Access denied for user 'newc5data'@'localhost' to database 'c5data'
My question is: what if you didn't disable/clear cache? would that pose as an issue messing up the sql file?
I backed up sql and tried to import it in the new phpmyadmin but it's not working and coming out with an error:
Error
SQL query:
--
-- Database: `c5data`
--
CREATE DATABASE `c5data` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
MySQL said: Documentation
#1044 - Access denied for user 'newc5data'@'localhost' to database 'c5data'
Thanks for the tips. The new data base and the old database have different names right now.
for some reason i'm unable to create the same database name on the new hosting because it automatically adds a name before the new database name, like "sitename_......"
So for some reason I still cannot import the exported old SQL file into the new database.. is it because the db file names are different? I didn't think that could affect it..
for some reason i'm unable to create the same database name on the new hosting because it automatically adds a name before the new database name, like "sitename_......"
So for some reason I still cannot import the exported old SQL file into the new database.. is it because the db file names are different? I didn't think that could affect it..
It may be that you exported the server rather than just the specific database.
If you can go back to the old server, make sure to click on the database name before you click Export. You should see something like Localhost > (database name) in the breadcrumb trail at the top of phpMyAdmin.
It shouldn't be a problem if your database is named differently, though. You just have to update /config/site.php with the new database name (and username and password if those have changed).
If you can go back to the old server, make sure to click on the database name before you click Export. You should see something like Localhost > (database name) in the breadcrumb trail at the top of phpMyAdmin.
It shouldn't be a problem if your database is named differently, though. You just have to update /config/site.php with the new database name (and username and password if those have changed).
Make sure your SQL user has the same user/pass, and that is is connected to the new database and has full privileges.
Make sure your database has the same name as your previous database.
If the database name or user login/pass are different then before, make sure to update your config/site.php file with the new attributes.
As far as I know, it shouldn't matter if you didn't empty your cache... it just takes longer to download/upload all those files!