Is there any truth to this: the placement of fields in a table relates to field access speed. So, frequently accessed fields should be placed in the beginning of the table while fields infrequently used can be placed toward the end.
TIA,
Barkingdog
Doubt if placing frequently accessed fields first have any sense. Maybe there are something when you are accessing fields by names in client application, but overhead (if any) is hardly noticeable.|||In general I don't believe this is true and in my experience this would be a micro optimisation and its highly likely there are 10's if not 100's of more impactful ways to impact the perf of your app...|||I agree with Euan. I do think that his is just nit-picking in performance optimization. Being on the battleground in my consultant work I always see that the most optimization regarding indexes and writing queries was not considered by the customers. *If* this *should* get you a performace gain, this should be that small you you probably will not feel the effect.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
