Sorry about that. You are right the problem doesn't come from the Fulltext query, it's coming from the fact that the full text index field is returned as part of the resultset (and entity). The database column indexed is a Text column with KB of data on every row (thousands of row). A typical query returns thousands of rows.
Using version 2.0.00 - Sql Server 2005 - .NET 2 - SqlServerSpecific.NET.20
The effects of this are :
1) Saturated bandwitch
2) Painfull performance (because of amount of data that has to go over the wired to return the results)
I have tried unmapping my fulltext indexed field from the entity using the designer. (because I never need this column as part of a search result) The only time this column is needed into an entity is when I Create / Edit such an Entity. To overcome this I have created to separate Entities over the same table. One "Full" entity containing the field (for insert / update scenario of an Entity) and one "Short" entity of the same table without that "huge" field / column included.
My problem is that when I use the "Short" version of the entity that doesn't contain the field on which I want to Fulltext search I am unable to build a FieldFullTextSearchPredicate because I don't know how to build an IEntityField2 reference over a field that wasn't generated by the designer.
This words but is really slow
FullEntity :
-FirstName
-LastName
-Phone
-Address
-Content (Text - Lots of it)
predicate.Add(new FieldFullTextSearchPredicate(EntityFieldFactory.Create(FullEntity.content), FullTextSearchOperator.Contains, containsString));
This is what I would want to achieve : (filter on a field not included in the entity but that exists in the table)
ShortEntity :
-FirstName
-LastName
-Phone
-Address
predicate.Add(new FieldFullTextSearchPredicate(<can't find what goes here>, FullTextSearchOperator.Contains, containsString));
Hope this helps