Baz wrote:
>>There shouldn't be any practical limit on the file size other than the
>>O/S and sql buffer memory limits (which are usually extremely high).
>>However, there is a more constraining limit of 1000 items in a single in
>>list that may affect you (you'd have to split it into multiple lists
>>with an OR condition between them).
>>
>>Note: I'm assuming you're using this for an occasional query. If this
>>list changes a lot and you're going to run lots of these queries then
>>the sql area is going to be strained which may adversely affect the
>>performance of your entire system (the standard argument for using
binds).
>
> As of now, I am not sure how often I will be using this. But I guess
> clearing out the buffer might help with the performance issue. Please
> correct me if I am wrong...
Well, it depends on what you mean by 'buffer'. I'm referring to the sql
area so you'd have to flush the shared pool (alter system ...). That's
something that you really just don't want to be doing. If you're going
to do this very frequently (hundreds or thousands of times a day) or you
have a small shared pool then you need to engineer this to use bind
variables. That means you'll need to use something other than SQL*Plus
as well since there's no method for using it's version of binds without
abusing the sql area to some extent.
--
Richard Kuhler
Received on Mon Oct 13 2003 - 12:28:51 CDT
