Thanks you opc..

Garadin. I call you a magician. wonderful. works great.

Yes, This is one time load. task accomplished

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...

am the db_owner...

even i did renaming on other systems succesfully. i dont know what went erong this time....

Even restart did not help...still the same error....:crying:

Ninja..I tried clearing proc cache and that does not help..I might reboot in some time from now..

Nope..It did not work this way too...:(

Still the same error..

I have saved copy of the script.

I didnot understand manual deleting part. i have tried dropping and recreating , which does not worked.

I have tried executing

exec dbo.sproc_NR_EWMDupVIN...

it says the same error..

Invalid object name 'dbo.sproc_NR_EWMDupVIN'.

/****** Object: StoredProcedure [dbo].[sproc_NR_EWMDupVIN] Script Date: 03/02/2011 12:03:00 ******/

SET ANSI_NULLS OFF

GO

SET QUOTED_IDENTIFIER OFF

GO

Create PROCEDURE [dbo].[sproc_NR_EWMDupVIN]

AS

BEGIN

declare @AlertMasterID int

declare @ProcessingDate datetime

declare @DealerID int

declare @vin nchar(20)

declare @DupFinancedDate...

yes ..dbo is the owner

Mark-101232 .. You rock...I was struggling with pivot..and you gave a solution by not using PIVOT..Thanks a lot mark....

I understand your suggestion regarding not to use in t-sql. But few things which are out of our control makes us to use these inside t-sql.

I appreciate if you can...

Thanks all..Restoring the latest full backup from source fixed the issue.

TYPE: oPERATINGSYSTEM COMMAND(Cmdexec)

Run as: SQl server agent

Command: "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqllogship.exe" -Restore 02443D0C-6EE6-4139-B9B9-6E272E0324B8 -server EBFFwoe3

in view job history, error Message is..

Executed as user: EBFFwoe3\SYSTEM. The step failed.