February 27, 2015 at 7:36 am
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
February 27, 2015 at 7:43 am
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/
March 9, 2015 at 7:01 am
I don't think it would cause issues, but I'm not clear on what problem it solves.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 9, 2015 at 12:14 pm
It would be better to put all virtually static lookup tables in their own file/filegroup and only backup that filegroup or do index maintenance when something changed.
As far as putting all lookup tables in their own lkp schema, that would make it obvious that a table was a lookup table but it's a whole lot like prefixing table names with "tbl_", which I don't care for at all. It would also separate lookup tables from their dependent tables and that can make life a real pain when you look at the tables in Object Explorer.
Personally, I'd dump the idea of using a separate schema for lookup tables.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply