Ok, so how is the varchar field defined? If it is over that limit you
mentioned earlier (1000 or so?) then that's the problem. Basically, SQL
Server would be complaining only when the data to index actually was too
big.
Assuming that was the problem I think you could define "formula" column
in the table and base it on the varchar field that was too long (so,
"short_field = left(long_field, 500)"), and then try to use the short
field in you index. That way the index would never encounter anything
too long and, depending on the data in that column, you might not even
experience a performance difference using the shorter index.
(I've never done that before in real use but I was just able to define a
table and index that way.)
Mark
-----Original Message-----
From: Scott Weikert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 30, 2007 3:21 PM
To: CF-Talk
Subject: Re: SQL insert issue with indexes
Gaulin, Mark wrote:
> There must be other indexes on this table that include the text
fields.
> Check in SQL Enterprise Manager.
>
Did. There's four fields:
The main identity field (PK)
Two int fields referencing IDs in other tables (with indexes, but no
foreign key/relationships set up) One varchar field.
So yeah, the PK field has an index on it as well besides the two int
fields, but that's it.
The indexes are set up as follows:
PK field is clustered
Other two int fields are neither unique or clustered
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Upgrade to Adobe ColdFusion MX7
Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs
http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268107
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
