Only if the data already exists in another table. In that case you can create an INSERT on top of a SELECT.

INSERT mytable (col1, col2, col3, col4, col5, col6)
SELECT a, b, c, d, e, f
FROM anothertable
WHERE <some condition>

Right, then.

In light of that information, let me pose another question.

I need to dynamically insert 390 values into a table. I can easily group information by 12s and 30s.

Given that this operation is only going to happen twice a month, what's your in terms of performance?

Should I run a query to INSERT 30 values 12 times, or 12 values 30 times?

</g>

Are you asking if you can insert multiple rows in a single statement? Yes, you can if you use the VALUES syntax which can insert multiple rows. To do this, include multiple lists of column values, each enclosed within parentheses and separated by commas.

INSERT INTO mytable (col1, col2, col3, col4, col5, col6) VALUES 
(NULL , '1-04-2007 00:00:00', '0' , '0' , NULL, NULL), 
(NULL , '1-04-2007 00:00:00', '0' , '0' , NULL, NULL), 
(NULL , '1-04-2007 00:00:00', '0' , '0' , NULL, NULL), 
(NULL , '1-04-2007 00:00:00', '0' , '0' , NULL, NULL);

Be careful you aren't writing duplicate keys though.

Yes, I know that much. The question is, I can't insert 350 values at once (I tried).

So I'm wondering if there's a rule or any advice anyone has, since I'm to have to do multiple INSERTS, which is code-inefficient.

So, should I do 30 at once 12 times, or should I do 12 at once 30 times?

</g>

I've done a lot more than that. Which database are you using? What error message do you receive upon attempting your INSERT?

It's probably best to do your own testing on your own server with your own configuration. One person's benchmarks on a completely different system from yous won't mean much.