If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

a procedure that it calls gets modified and it will go invalid. Check for all objects that had a last_ddl_Time of the day it went invalid for a starting point. You can also query sys.dependancy$ to check dependancies for that object.

Originally posted by bazza Surely a network glitch could invalidate an object. If that object in database x was in some connected via a db link to another object in database y, and the network between the two went down.

That sounds more like a guess. If that were the case whenever a remote database shutdown it would invalidate every object that depends on it. This is definitely not the case.

Thanks for the replies guys, another suggestion from one of our developers was that someone created a TEMP table with the same name as an existing table and then dropped it. This is possible but no one is fessing up, big surprise. Even the developers want to shoot the developer responsible.

Thanks for the query Jeff, I checked on all object with DDL against them. We still think it was a temp table, we NEVER should have given them schemas that allow them to create tables in production.

C'mon, everyone sing along with me..........

"Shoot the developers!"
"Shoot the developers!"
"Shoot the developers!"

Roses are nice
Violets are mute
I never met a devloper
I didn't wanna SHOOT!