Thread: shows me this error- You probably tried to upload too large file

Yes, your file is too large to import.

Email it to your hosting provider and have them do the import. If they won't do it for you or want to charge you to do it, change hosting providers fast!

Problem solved!

Dam this guy above me must have a web hosting company that's his solution to freaking everything.

Most servers have a file upload limit either change this in your php.ini file or if that isn't possible try cutting your SQL file into multiple files, look at the pattern it should be easy to tell the beginning and end of each SQL statement, just cut it in half and run them separately to get around this.

Why should this guy have to cut his SQL file in half? That's just stupid. Just because his hosting provider won't do the import? Get real, the guy needs a new hosting provider...and I didn't say which one, so he can go where ever he pleases. Don't jump to conclusions so fast.

Sending a SQL file to your web host to upload is just silly, will you be sending it as an attachment? It takes 2 seconds to split an SQL file. Switching web host providers is pretty drastic solution to uploading a large file.

(duplicated post when I clicked submit and nothing happened)

Once again, not true. It's not as easy as you say it is to split an SQL file. If you've never done it before, you wouldn't know that you can't actually just "split it in two" as you say.

You're going to split on the inserts but you can't just split the file like that. If you did and tried to import them, one would work (maybe if you did it right) and the other definitely wouldn't work. You'd need to know how to start and end each file you're going to import.

If your hosting provider won't import the file for you, you may not know how bad that is and they don't deserve your business. If they don't do that, then there are probably a lot of other things they aren't doing for you that they should. It's just an indicator.

INSERT INTO table_name
VALUES (value1, value2, value3,...)

That is an SQL INSERT statement your file will look like this

INSERT INTO table_name
VALUES (value1, value2, value3,...)
INSERT INTO table_name
VALUES (value1, value2, value3,...)
INSERT INTO table_name
VALUES (value1, value2, value3,...)
INSERT INTO table_name
VALUES (value1, value2, value3,...)

Just split them at the end of one statement like so

file 1
INSERT INTO table_name
VALUES (value1, value2, value3,...)
INSERT INTO table_name
VALUES (value1, value2, value3,...)

file 2
INSERT INTO table_name
VALUES (value1, value2, value3,...)
INSERT INTO table_name
VALUES (value1, value2, value3,...)


Not too difficult and there is nothing else you need, a SQL file contains just SQL statements and possibly comments which are not parsed but MySQL anyway. Not sure why this would be such a problem.

Some data is private and needs to be secure sending it to a random tech support guy at abchost might not be the best idea for security conscious developers. I personally like to keep my data between me and my database, but that's just me.

@James

Check your import file structure carefully. You simply cannot have just insert statements. It is more complex than that. You will need most, if not all, of the following structural parameters as well for each file if you decide to split it:

-CREATE TABLE IF NOT EXISTS `Table_Name_Here`
-PRIMARY KEY (`Table_Name_Here`)
-KEY `Name` (`Table_Name_Here`)
-SQL ENGINE TYPE=
-DEFAULT CHARSET=
-AUTO_INCREMENT=175

We wish you all the best with your import.

Why can you not have just an INSERT statement?

What the guy above is doing is also creating the tables if the tables already exist all you need is INSERT statements to fill in the data.

When you do an export of just data you are left with just inserts. You do not need to create the tables everytime.

He only needs the other information if the tables don't exist, besides what you wrote is still a statement just one that creates the table first if it does not exist. So again just look for the end of each statement, nothing needs to precede your statements.