Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Inserting record with non-blank memo fileds is slow
Message
From
25/10/1998 02:22:23
 
 
To
24/10/1998 08:23:25
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00150117
Message ID:
00150265
Views:
24
>>VFP 5.0a + SP3 + SQL Server 6.5
>>
>>I must have done something very wrong. A remote view with a memo field and a few other fields. If I add a new record with the memo field filled, it takes some 5 minutes to TABLEUPDATE() and I can see the intens hard disk activity of the server. However:
>>1) If I add a new record leaving the memo field blank, it is fast.
>>2) If I edit an exsiting record with or without memo contents, it is fast.
>>
>>Chen
>
>
>If your table is dynamic, then your primary key index should be Non Clustered.
>If your table is Static (such as reference Tables) then your primary key index should be Clustered.

Thanks for the reply Nabil,

I use surrogate keys exclusively and I never make the primary key index to be clustered, instead, most of time I reserve the clustered index for the 'real key'. If the clustered index is the point then I fail to undersatand why the inserting speed differs so greatly between a record with filled memo field and a record with a blank memo field. It is instant to insert for later case.

Chen
Chen Nan
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform