4/20/2024 1:34:57 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
SalesLogix Table Index problem
Posted: 27 Oct 09 12:44 AM
|
We are getting problem for all vanilla SLX tables. We seems to have primary key set with naming convention PK_Tablename and then another unique index with naming convention XPKTableName.
Eg. On the ADDRESS table, we have a primary key named PK_ADDRESS, where ADDRESSID is the key column, and another unique index called XPKADDRESS, also unique, also on ADDRESSID
This will cause double the number of updates, as each index will need to be updated when the table is updated, inserted or deleted from.
Can someone please advice? We are on version 6.2.5
Thanks |
|
|
|
Re: SalesLogix Table Index problem
Posted: 27 Oct 09 1:18 AM
|
This is specially a problem with Updated database.
Older instances of SLX databases used different naming convention for Indexes. As you apply Upgrade bundles, newer (duplicate in definition) indexes get added.
You need to review the indexes and remove the ones that you don't want.
Also, as you keep on upgrading, you will notice some addtl indexes will be created, and/or some will be replaced by PK constraints, etc.
In general you should always keep an eye on your indexes, even out of the Box indexes may not be applicable for your implementation and/or usage pattern. You should always do DB Tuning and Add/Remove indexes as needed. And by the same token, keep an eye on indexes and statistics.....
|
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|