Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Any corruption problems using compound indexes?
Message
 
 
To
17/05/2010 16:53:57
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows Server 2003
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01464942
Message ID:
01464943
Views:
52
>Hello,
>
>We are using compound indexes to improve our data access speed which has improved. We are sometime getting our indexes corrupted and don't know if it's related.
>Does anyone have any experience or knowledge about the "does and don'ts" of using compound indexes? Are they OK to use or are there reliability issues.
>
>Examples of indexes I'm using:
>
>*----- Views Defined for Compound Indexes
>INDEX ON STR(iCustomer_Masteriid) + ctrans_type + cTrans_No 					 TAG CDX_1
>INDEX ON STR(iCustomer_Masteriid) + ctrans_type + cTrans_No + STR(iapply_seq) + cRate_Table_Code TAG CDX_2
>
I don't see a problem with these indexes. Are you sure you don't create indexes with variable length? Are you using varchar fields (though in VFP7 you don't have them). The indexes themselves should not increase a chance of corruption.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform