Nadrek (1/24/2013)
Further, knowing about hardware allows you to have the option of choosing tradeoffs yourself - what's the native word size, and are there instructions that are much faster/slower, for instance. Not knowing about hardware means you cannot control those tradeoffs... and you may not even be aware of their existence.
The one that I have run into more than once is someone who used the MS Access Upsizing Wizard or from SQL just imported the tables into SQL out of the Access DB directly using the GUI. Then they wonder why it is a bloated mess. :pinch: By default, the text fields are created as NVarchar for an English only DB. You are essentially doubling the size of the data for no reason. What I'll generally do to make it easy is on me is use the upsizing wizard, script it out and then modify the script and re-import the data.
But there are so many things that I'll find a developer has done and ask "What in the h*** were they thinking?" I'm glad the development team is not within a couple of states of me. I'd be up on assault charges by now. :angry:
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.