on 02-03-2010 2:42 AM
Hi There, we are considering implementing a new structure in our products table (MDM5.5) that uses considerably more fields than those which we currently have deployed, we are looking at 200 fields in this table. Is anyone aware of a limit on the number of fields in the products table before we start to run into performance/stability issues etc etc?
Hello Adam,
There is no specific limit to the number of fields.
In terms of performance problems stemming from immense volumes, it is more a combination of multiple parameters: the width of schema (number of fields), number and usage of languages, number of records in main, existence of high volume lookup tables, data profile, property settings (extensive usage of keyword index, sort index etc). of course, there are other factors: business process, landscape design, proper sizing, user's profile and intensity of their work in MDM etc...
Having 200 fields in the main table certainly is considered as high number but it will not necessarily be a problem.
Can you please provide some ballpark figures as to the other parameters (number of records in main, number of multilingual fields and number of languages etc)?
I would suggest also a Data Model Review in order to validate that the business requirements can not be modeled better and the custom structure follows the best practices .
Best regards,
Hedda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.