jonesboy21 (2/27/2015)
Does anybody see any fallacies to putting all lookup tables (static reference data) in their own schema?example: lkp.States
lkp = schema
States = table name
Nope. But I would suggest not naming the schema lkp. That doesn't mean much. I would change it to lookup. Makes it immediately and extremely clear what that schema is. Just remember that it will force you to put the schema on every query (which is a great habit to get into).
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/