Posted by Sir Four at 7:34pm Aug 24 '09"At work we're battling with this very issue, where we have unbounded IN clauses that are creating queries of 500 KB and well beyond (the query itself, not the result set!); the biggest one I've seen so far was very nearly 2 MB. When these queries get executed, the entire database server ceases doing anything else and focuses entirely on running that one query; other queries build up in a queue and wait around - our entire web app is completely useless for several minutes"
Has someone gotten fired for this??
Don't many databases put an upper limit on the number of values in an IN clause just for this reason?
Has someone gotten fired for this??
Don't many databases put an upper limit on the number of values in an IN clause just for this reason?
Re: The only way around it I've found - Sir Four