My first question would be, what is your CLR function doing that could not be
done in SQL?
Second, if your resultset is small enough to be stored in memory ( INT =
4bytes x number of rows in table, ok pretty small ) generally speaking, it is
going to depend on what else going on on the server at the time. You must
agree, memory allocation is going to be pretty fast, much faster than disc
allocation. Why worry?
See my other reply for presizing tables ( we call these transient tables in
our shop ).
wBob
"DR" wrote:
Quote:
I have a CLR function thet returns IEnumberable (a table) and it has a
FillRow function. I am returning 10,000 integers from this function. Is
there any way that I can preallocate the resulting table or give SQL server
hint as to how many rows my function will return? It makes me cringe to
think that every time FillRow is called that sql may be doing some memory
allocation to make the resulting table bigger.
|
RE: I have a CLR function thet returns IEnumberable (a table) and it h -
11-21-2007
, 05:32 PM
Linear Mode
