Worst Practices - Objects Not Owned by DBO

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Andy Warren » Worst Practices - Objects Not Owned by DBO

72 posts, Page 8 of 8

«««4 5 6 7 8

Worst Practices - Objects Not Owned by DBO

Rate Topic

Display Mode

Topic Options

Author

Message

jswong05

Posted Thursday, July 16, 2009 12:35 PM

SSC Rookie

Group: General Forum Members
Last Login: Monday, March 18, 2013 7:54 AM
Points: 27, Visits: 421

No, you are missing the power of using schema. You should not put everything under dbo.

Jason
http://dbace.us
Tongue

Post #754425

Jeff Moden

Posted Tuesday, December 15, 2009 9:09 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:01 PM
Points: 32,899, Visits: 26,779

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."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #834578

« Prev Topic | Next Topic »

72 posts, Page 8 of 8

«««4 5 6 7 8

Permissions