Are you certain about that?? (I remember learning in my Oracle classes that it does make a difference…)
why in heaven’s name would it even occur to you to move it?
I created my table with the fields in “Order of Importance”.
Now I think it would make them easier to work with if they - or some - were in “Order of Process Flow”.
For example, you have an “activation_code” before you would have a “temp_password”.
Likewise, you need a “salt” before you can create a “hash”.
It is a minor point, but detail matters!!!
Anyways, I think that the Left-to-Right Order of your columns does affect query speeds… (I think it is how the database stores the data and accesses it in “memory blocks”, but who knows?!)
Take it for what it’s worth, but it does look like there is/was a slight performance improvement - in Oracle only (from what I can tell) on UPDATES (and really, the only benefit was in rolling back a large number of updates), but the only result I can find on a search are from 2008, so I wouldn’t be able to verify whether the claims are accurate or not anymore. And even then, the performance difference was minimal and it only made a difference on large (100K+ row) updates.
The only other place where I’ve seen an order be affected was on a query dealing with memo/text fields, but that was classic asp and ADO, and TBH, I don’t believe that problem even exists anymore. It had nothing to do with the table or the performance, but rather how the ADO handled the values within the recordset returned.