This is my reference: http://www.sqlservercentral.com/columnists/awarren/worstpracticesobjects notownedbydbo.asp
I agree in that you should always specify the database owner in queries. I usually always specify the database name such as: Database.dbo.TableName I generally connect to a database server with a single datasource. I then cross databases using the full database name. Either way, I have not yet had a need to specify different object owners. Not to discount the practice, however. M!ke -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 2:04 PM To: CF-Talk Subject: RE: SQL Server User Problems > All objects "should" be owned by dbo. That is a best practice. If they > are owned by other owners, it can lead to bad things as well as > confusing code. I disagree with your assertion that using the dbo alias for ownership is a "best practice". There is nothing wrong with allowing specific logins to own objects, as long as you're aware that you're doing this. In fact, I'll go a step farther and say that if there's any best practice in this, it's to explicitly state table ownership in your queries. Of course, there are plenty of people who might disagree with me: http://www.sqlservercentral.com/columnists/awarren/worstpracticesobjects noto wnedbydbo.asp Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:207091 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
