Jeff Moden (5/25/2014)
Eirikur Eiriksson (5/24/2014)
Must say that I'm slightly puzzled. I have read my post over and over but I cannot find neither any implicit nor explicit suggestions of ignoring good coding or working practices. And most certainly, if that is the impression left by my post, it is not the intention. Could someone help me out here if that is the case?😎
It was this... particularly the bolded part...
[font="Arial Black"]Start by getting something working[/font], test it against the requirements and improve if needed. This way, you can hopefully avoid another pitfall which is premature optimization.
Same here. It had the feeling of 'just get something working, no matter how bad, no matter how hard to maintain. It can always be fixed later'. In my experience, the 'fix it later' part never happens.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability