We all know that AIM shows us fields sorted by field name, and up til now, I hadn't really cared about what was going on in the back end, although I'd seen people write some things about it.
With Derby, I wasn't using any backend tool so how AIM took care of things was its business.
But now I'm working with a big client with big data in MS SQL Server... and other people down the road are going to possibly be hitting this data with various reporting tools.
One of my tables is a total mess - its like a jigsaw puzzle of field names.
Frankly, someone down the road is going to be asking "what the hell was this designer thinking when he laid out these fields in this table".
All my life I've kinda laid out table structures with key fields "in the front" trailing off to less important fields at the end.
I'm contemplating manually creating an 85-field table just to order the fields in some semblance of logical order/structure, so that when viewing them (even in SMSS) it makes some kinda sense.
How have you guys handled this?
thx