Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase «««45678

Worst Practices - Objects Not Owned by DBO Expand / Collapse
Posted Thursday, July 16, 2009 12:35 PM

SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, October 20, 2014 1:11 PM
Points: 27, Visits: 475
No, you are missing the power of using schema. You should not put everything under dbo.

Post #754425
Posted Tuesday, December 15, 2009 9:09 AM



Group: General Forum Members
Last Login: Yesterday @ 10:30 PM
Points: 36,881, Visits: 33,717
I know this is an old article but I'm glad I found it. I agree 100% for homegrown stuff. Sure, if you have to follow a given naming convention to support a 3rd party app, your hands are pretty much tied. I also don't give a hoot about ANSI compliance because truly transparent code portability is a myth and not using the advanced extensions available in each "brand" of an RDBMS is like having a scientific calculator and only using the 4 basic functions.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #834578
« Prev Topic | Next Topic »

Add to briefcase «««45678

Permissions Expand / Collapse