InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 22:36:26 GMT20http://www.sqlservercentral.com/Forums/Topic795248-149-1.aspxLooking at that procedure in 2000 there is the following:[quote]-- NOTE: THE IMPLEMENTATION (ie. using trace bit 1717) IS *VERY* LIKELY TO CHANGE, -- SO DONT EVEN *THINK* ABOUT USING THIS TRACE BIT DIRECTLY!!! if @pSeqMode = 1 --- Undocu trace 1717. Now MSShipped bit will be set auto at Create time.[/quote]So I would be tempted to say when using SSMS make sure you select the correct database, that is the DB you want to create the SP within My guess would be that setting this trace bit also effects other system internals and would be something you would not want to alter.Fri, 02 Oct 2009 15:27:25 GMTbitbucket-25253http://www.sqlservercentral.com/Forums/Topic795248-149-1.aspxI have a sql 2005 sp2 box right here, I created a sproc and it appeared under programability/stored procedures.. not under system stored procedures..can you give me an example of your create script and tell me how you're running it?Fri, 02 Oct 2009 15:04:00 GMTtorpkevhttp://www.sqlservercentral.com/Forums/Topic795248-149-1.aspxHello,We're using SQL Server 2005 SP2. Recently, any new procs that we've created under Master, are visible only under the System Stored Procedures folder. With 2000, we could use EXEC master.dbo.sp_MS_upd_sysobj_category 2 to disable this function. How can do the same for 2005?Thank you,JGTue, 29 Sep 2009 09:43:09 GMTJohn Garcia