• Jan Van der Eecken (5/7/2009)


    Sorry to disagree, but I don't see what's wrong with this, unless your collation sequence is case-sensitive, which in most cases is a mistake in the first place. What I do have a gripe with is that I want my code to look consistent, which Intellisense prevents me from doing if somewhere in history some developer made one single table name CamelCase, but all the other ones are as per coding standards (whatever those may be).

    Naming and case conventions should be consistant across the database, this includes all table, procedure, function, variable names and the code which is being written for the database

    If some developer has named a table CamelCase instead of CAMELCASE then they need re-education on how the system at that organisation works and the object should be renamed.