December 9, 2009 at 12:41 pm
Hi
SOme one can provide advantages and disadvantages in implementing Schemas in prod environment.
December 9, 2009 at 12:49 pm
They separate tables into logical groups or application subsets that can be used as security boundaries if implemented correctly. Some might say that having to schema qualify everything would be a disadvantage, but it is already a recommended best practice, so it forces developers to follow better coding practices out of the gate which is always a plus in my book.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
December 9, 2009 at 12:57 pm
Some reading on the subject:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 9, 2009 at 1:21 pm
Yes, i agree with you, it is best practice, But my concern is there was any administrative over head implementing too many like 10 -15 different schemas in production environment it self.
Do you see this kind of approch is overkill on the system or on the security point of view.or any other which i do not think of.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply