I'm reading Joe Celko's SQL Programming Style ( http://www.amazon.com/exec/obidos/ASIN/0120887975/houseoffusion) and examining everything he says to see if I agree or not and how I can apply it. I'm also looking through my old docs and other sites. A good thing about upgrading an old site that had a LOT of people working on it is that you have a lot of great examples of what not to do. :)
For example: select * when joining 5 tables just to get a record count or a single row is bad. When it returns over 200 columns, it's worse. On Tue, Jan 21, 2014 at 12:28 PM, Michael Dinowitz < mdino...@houseoffusion.com> wrote: > I use an underscore for look-up tables in an MS SQL2008 DB. To me, a > look-up table is anything that will almost never change. Things like > _roles, _states, _ethnicity. According to one book, an underscore as a > prefix should not be allowed but in practice it does not seem to cause any > problems. > Has anyone seen any problems with this? I'm writing up a sql conventions > spec for a contract. > > Thanks > Michael > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/sql/message.cfm/messageid:3530 Subscription: http://www.houseoffusion.com/groups/sql/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/sql/unsubscribe.cfm
