Column-order an access speed?

Hot Topic

stored procedure
rs:about the Scope parameter of a aggregate function
Importing Tables with Identity properties (uisng Import wizard)
Storing the ErrorDescription on DFT -> Flat file error output
Programmatically extending the project tree
~* Allowing Users to select the Fields to be displayed in report *~
SQL Impesonate Logon Problem
Sample app for C#/SQL2005 DAL
execute sql task to set output parameter of type integer
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.FN_NIVELCOMPETENCIACARGO", or the name is ambiguo

SQL Server

DTS Mail task breaks after SQL 2005 uninstall/install
How run SSIS package from MsAccess?
Recordset Destination with Foreach Loop Container - finding indexes
how to append windows login name to table name
Howto suppress FETCH output
SCD component in SQL2005
Autosize reportviewer control
How to sort that does not include duplicates in display?
Can not open SQL Management Studio
SSIS issues

Column-order an access speed?

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

Answer this question

Column-order an access speed?

  • Sri Harsha Kasi

    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...

  • Greg Baxter

    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
    ---

  • MadhavG

    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.
  • Column-order an access speed?
Answer this question