March 2, 2011 at 11:33 am
Try it, but I have a bad feeling we're missing something stupid...
March 2, 2011 at 11:51 am
Even restart did not help...still the same error....:crying:
March 2, 2011 at 11:53 am
NewBeeSQL (3/2/2011)
Even restart did not help...still the same error....:crying:
Like I said, we're missing something real stupid.
Did you reset the permissions after creating the proc?
March 2, 2011 at 11:56 am
I just did a retest on my system and I can safely rename and un-rename the procs without any problems...
Whatever you did is most likely not a direct effect of the rename, but something else.
March 2, 2011 at 11:57 am
am the db_owner...
even i did renaming on other systems succesfully. i dont know what went erong this time....
March 2, 2011 at 11:57 am
Have you tried the restore path with reimport?
I'd try that with your latest backup and the current copy of prod, but on a test server. See if that solves it.
March 2, 2011 at 11:59 am
NewBeeSQL (3/2/2011)
am the db_owner...even i did renaming on other systems succesfully. i dont know what went erong this time....
Are you able to call other procs from the same query window that fails with the renamed one?
Tried refreshing the sp list in ssms to make sure the un-rename was successful?
March 2, 2011 at 12:00 pm
NewBeeSQL (3/2/2011)
am the db_owner...even i did renaming on other systems succesfully. i dont know what went erong this time....
I don't know how urgent this is for your company, but you can always call MS directly (200-300$) and they'll help you over the phone.
I'm heading out now so I can't provide help for a couple hours.
March 2, 2011 at 12:09 pm
Yeah Ninja, I fear you're right, we're missing something obvious and just not asking the right questions.
NewBee... can you do the following for me? I want to see what names your proc is listed as to the system:
select o.name from sysobjects o where type = 'p' and name like '%_NR_%'
Let's see what the system thinks these object's names are.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
March 2, 2011 at 12:16 pm
OMG.........
I figured it out.........The developer was writing stupid code inside proc which caused all these mess up.
if you see the proc which i sent in my initial mail..there is a line saying
SELECT @AlertMAsterID, dbo.sproc_NR_EWMDuplicateVIN.fk_DealerID,
he is using proc name instead of a function..When i commented this select, it works...............
Need to throw the developer out...............
March 2, 2011 at 12:25 pm
*facepalm*
I'd assumed the code worked before the whole namechange malfunction previously. Welp, that would certainly do it! Glad you figured it out.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply