Is there a good reason why the customer and item tables have a clustered index on a timestamp column?
Surely this column will get updated every time any row is updated and thus cause the row to be moved, and due to the cluster key changing cause all the non-clustered indexes to require updating as well. This strikes me as highly inefficient.
Ian
Does anyone from the RMS product team monitor this newsgroup?
I would have expected a response by now; as this "fault" would probably cause a serious performance hit on a busy system.
Ian
They may monitor, but rarely post. The Technical support team monitors and will post occasionally.
If you consider this a bug you could enter a support incident to report it and IF tech support agrees that it's a bug report you would not be charged for the incident.
Probably the easiest way to get on the radar is to enter a Global Suggestion from Customer Source (or Partner Source) - those definately get to the product team, but there's no guarantee how they will prioritize it.
There haven't been any changes to the database since the upgrade from 1.1 to
1.2. I wouldn't expect to see any database changes until 1.4 at the earliest...They may monitor, but rarely post. The Technical support team monitors and will post occasionally.
If you consider this a bug you could enter a support incident to report it and IF tech support agrees that it's a bug report you would not be charged for the incident.
Probably the easiest way to get on the radar is to enter a Global Suggestion from Customer Source (or Partner Source) - those definately get to the product team, but there's no guarantee how they will prioritize it.
There haven't been any changes to the database since the upgrade from 1.1 to
1.2. I wouldn't expect to see any database changes until 1.4 at the earliest...BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.