in reply to Re^2: A database table size issue
in thread A database table size issue

Use the server resources rather that the client's.
Really? Why? Typically, the number of servers is far less than the number of clients. Using server resources that benefit one client hurt all the clients.

I'm not saying that in this case the task should be done on the client (we've no idea about the task, nor about the setup), but I disagree with the blanket "use server resources rather than the clients". In way too many cases that isn't scalable to do without thinking.

Replies are listed 'Best First'.
Re^4: A database table size issue
by nikosv (Deacon) on May 01, 2012 at 16:24 UTC

    I set to write about why you should be using the dbms's power or resources instead of the client's,mainly because of query optimization,execution plan caching,parallel query execution,set based operations instead of procedural row by row,etc, but then I've noticed the OP's remark Re^2: A database table size issue,which acts as straightforward reply to your question :

    Thanks for the suggestion. The script was really slow when I processed the table row by row. I took your advice and rewrote the SQL to let the DB to handle part of the processing. The script now runs much faster than before

    So I have no futher comments
[reply]
      So I have no futher comments
      That's fine, and I already acknowledged that the OPs situation might very well call for processing on the server side.

      That does not mean I agree with the blanket statement -- just because it's the right idea sometimes, 50% of the time, or even 90% of the time, it doesn't mean it's the right thing to do all the time.

[reply]

In Section Seekers of Perl Wisdom