Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
USE [MASTER]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
USE [MASTER]
GO
CREATE PROCEDURE [dbo].[TOTALLY_NEW] @FISCAL_YEAR NVARCHAR(4) AS
BEGIN
PRINT 'HERE'
END
GO
select * from master..sysobjects <– returns one row!!!!!!
where name like 'tot%'
I’ve refreshed this list a dozen times..!!
I’ve tried disconnecting and reconnecting..
I’ve created all those other SP’s listed in the image before.
Here is a picture with more.
Per request, converting comment to answer:
Yes, you shouldn’t be creating user objects in master. The only time I ever do it is when I explicitly want to create a utility procedure that I can call from any database using that database’s context, which you have to do on purpose and doesn’t happen by accident – so I suspect you inadvertently marked your object as a system procedure. You do this using EXEC sp_MS_marksystemobject (or in older versions by having set EXEC sp_MS_upd_sysobj_category 1 – the latter might work in 2005 with 80 compatibility, not sure).