March 9, 2010 at 6:53 am
Hi,
I apologize for the generalness of this question, but I am totally stumped b/c I have never seen this before....
Our App Developer (I'm the DBA) has updated a stored proc on our live production server. Updating the SP fixes a bug and allows end users to scroll our site without issue. However, "something" is reverting the stored proc back to the old version with the bug.
We are using SQL Server 2008, we use log shipping from our live server (the issue) to our reporting server. I know this is extremely general, but has anyone ever seen this? Does anyone have any thoughts as to what could be causing this?
I literally saw the fixed code yesterday and the site was working and I came in this morning and the code had reverted back to the old version and the site isn't working.
Could it be a job? A maintenance plan? The log shipping? I realize I'm not providing any details of great substance, but I'm not even sure where to look as I've never seen this before.
Any help is much appreciated.
Thanks,
MW
March 9, 2010 at 7:04 am
In the appropriate database, run this query, it may help you in narrowing down when this happens. You may need to setup a server side trace to track changes to the database, or you could setup DDL triggers to do this as well.
select
name,
type_desc,
create_date,
modify_date
from
sys.procedures
where
name = '< your procedure name >';
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply