Frror: 4000 max string literal in Expression for datareader component

Hi, I have a datareader component of which i am dynamically setting its sqlcommand statement with expression (click the background of dataflow > properties > expressions). Now my sql select statement has about 600 fields so that makes my expression statment "select field1, field2, .....from table1 where field2 >=" + @.[User::dateforfield2] but when i evalute the expresssion (which is right), i get the error: A string literal in the expression exceeds the maximum allowed length of 4000 character and i think its because of the fields in my select statment causing my string literal to grow more than 4000 characters. Is there any way to increase the max string literal for expressions. Please help.

No there isn't unfortunately. This is a problem and will hopefully be fixed later.

Ask for it to be corrected here: http://lab.msdn.microsoft.com/productfeedback/default.aspx

Its more likely to happen if customers request it and there are good detailed scenarios why it is needed.

-Jamie

Free - Text Indexing

I am looking at a problem about intense CPU processing during a Background
Free Text reindexing. This happens about every 5 minutes (scheduled).
The key problem, is we are looking at putting the free text element onto
another hard disk controller to minimise. Would putting the Free-Text onto
another hard disk controller be sufficient or does it need to be associated
with another CPU.
This is on SQL 2000 Enterprise
Any advice would be helpful
--
Jack Vamvas
___________________________________
Advertise your IT vacancies for free at - http://www.ITjobfeed.comJack,
What does your disk I/O look like? Is it higher that it should be? If not,
then adding another disk and controller probably won't solve your problem
(although it is a good idea anyway to isolate full text catalogs). If CPU is
your bottleneck and there are no other influencing issues such as bad
indexes, etc., then adding another server exclusively for full text indexing
is probably the solution.
Full text catalogs are notoriously resource intensive on SQL 2K. Supposely,
SQL 2005 has improved the performance significantly, but I haven't verified
it myself. Maybe upgrading to 2005 should be in the plan as well.
-- Bill
"Tom" <DEL_TO_REPLY@.del.com> wrote in message
news:Z7OdnXKLyrVGPJvbnZ2dnUVZ8sOonZ2d@.bt.com...
>I am looking at a problem about intense CPU processing during a Background
>Free Text reindexing. This happens about every 5 minutes (scheduled).
> The key problem, is we are looking at putting the free text element onto
> another hard disk controller to minimise. Would putting the Free-Text onto
> another hard disk controller be sufficient or does it need to be
> associated with another CPU.
> This is on SQL 2000 Enterprise
> Any advice would be helpful
> --
> Jack Vamvas
> ___________________________________
> Advertise your IT vacancies for free at - http://www.ITjobfeed.com
>
>