Consequences of multiple queries sent to server?

[Jay Banks]

I asked this on asp.net, but haven't gotten exactly what I was wanting to know. I have some MySQL server scheduled maintenance done with a .bat file and an .sql file (done with Windows scheduler). I've also reworked it into asp.net script I was going to try and schedule (uses a loop).

The question is, either way I do it, it seems to pass all the queries to the server as fast as possible. Right now it doesn't seem to be a problem, but if things scaled up, I'm wondering if it might not become an issue.

Stored procedures is not really the answer I'm wanting to hear right now, either.

I'm just wondering if this is really a concern, and if it is, how do other people handle it? Obviously, some type of timers between queries comes to mind as a solution, but is there a better way?

Thanks,