InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 05:58:18 GMT20http://www.sqlservercentral.com/Forums/Topic513-33-1.aspxGood introductory article. Will you be doing a follow-up article? I'd like to see one on using the T-SQL templates which aid in quickly creating standardised SP's.ThanksPhill CarterSun, 29 Sep 2002 21:58:00 GMTphilcarthttp://www.sqlservercentral.com/Forums/Topic513-33-1.aspxOkay- that works. Thanks a lot. Fri, 24 May 2002 07:17:00 GMTnsearlehttp://www.sqlservercentral.com/Forums/Topic513-33-1.aspxBest practice is to have all objects owned by dbo. You can either create them and later change the owner, or you have to be the dbo (db owner) of the database. You can accomplish that either by connecting with any login that has sysadmin rights, or by setting up an alias for your login to dbo.AndyFri, 24 May 2002 07:16:00 GMTAndy Warrenhttp://www.sqlservercentral.com/Forums/Topic513-33-1.aspxGreat article, but I'm having problems with who the owner should be in the CREATE PROCEDURE line.When I try to enter my own username as the owner, it shows an error message, and won't let me save the procedure. I have also tried 'dbo_user' with the same result. I've read elsewhere that the owner of the stored procedure should be the same as the owner of the objects it uses in order to avoid 'broken ownership chains'- whatever that is! Who should the user be? Fri, 24 May 2002 07:06:00 GMTnsearlehttp://www.sqlservercentral.com/Forums/Topic513-33-1.aspxComments posted to this topic are about the content posted at <A HREF=http://www.sqlservercentral.com/columnists/sburke/introductiontostoredprocedures.asp>http://www.sqlservercentral.com/columnists/sburke/introductiontostoredprocedures.asp</A>Thu, 05 Jul 2001 00:00:00 GMTSean Burke