Re: Unable to Drop / Alter a Proc that Exists
- From: "Rubens" <rubensrose@xxxxxxxxxxx>
- Date: Thu, 10 Sep 2009 09:12:54 -0400
Nice catch Kalen, this was the issue (can't believe we missed this one!).
Thanks,
Rubens
"Kalen Delaney" <please_reply_on_newsgroups@xxxxxxxxxx> wrote in message news:14DC68AB-300B-4763-97CC-4951C9AA1CD7@xxxxxxxxxxxxxxxx
Who is the owner of the object? Sysobjects should have a column for owner, and if you look in sysusers you'll see who that corresponds to. Then you need to use the owner name to drop the object. It's recommended best practice to always include the object owner name when working with objects, even if the owner is dbo..
--
HTH
Kalen
----------------------------------------
Kalen Delaney
SQL Server MVP
www.SQLServerInternals.com
"Rubens" <rubensrose@xxxxxxxxxxx> wrote in message news:E64C3A1C-10A3-4700-8F79-ABE0D8E179C3@xxxxxxxxxxxxxxxxOne of our developers is trying to create a proc that is not visible in the GUI on a SQL 2000 server. He gets an error message saying the object already exists. Additionally, we cannot ALTER / DROP the proc either because we get an error message that says it does not exist in the system catalog. However, I can see the object listed in sysobjects of the database.
Can someone tell me how to solve this? We have the code for the proc so all we need to do is CREATE or ALTER it by whatever means possible.
Thanks,
Rubens
- References:
- Unable to Drop / Alter a Proc that Exists
- From: Rubens
- Re: Unable to Drop / Alter a Proc that Exists
- From: Kalen Delaney
- Unable to Drop / Alter a Proc that Exists
- Prev by Date: Re: Kimbo Asks: Separate Volume for SQL Transaction Log ?
- Next by Date: Data Recovery
- Previous by thread: Re: Unable to Drop / Alter a Proc that Exists
- Next by thread: SQL 2005/2008 Disk IO
- Index(es):
Relevant Pages
|
