All stored procedures overwritten?

Hi Experts!

Something odd happened to my db!

As far as I can scripts or dts's were one has been on the server...nothing...yet...I came in this morning and ALL my sproc's seem to have been overwritten or re-created!
They all had today's date...and changes made recently were lost!

I have no clue as to how or why this happened!

ANY ideas?

LVL 37
Who is Participating?
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
either you looked on the wrong database, or someone run a script with the old version of the procedures on the database.
you can try to use some tools like Lumingent Logexplorer to check through the transaction log file what/when it has happened, but you will NOT find back the values unless you have a backup from "yesterday"
Aneesh RetnakaranConnect With a Mentor Database AdministratorCommented:
Check your log files using the tools like Apex log , Lumigent log explorer .You can go thru the log and  check any alternation happened
Aneesh RetnakaranDatabase AdministratorCommented:
Someone may  accidently ran the database script ,
you can download the trial versions of these products from their websites .. Just google with the product name
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

ptjcbConnect With a Mentor Commented:
Someone in a hurry ran the wrong script. The database would not automatically run scripts to change procedures. You may be able to find who did it, but first you should restore a recent backup and run those scripts over the "changed" database. You also probably have missing tables or indexes.
samtran0331Author Commented:
thanks everyone...I assumed "someone did something"....just wanted to make sure no one knew of any instance where SQL Server would freak out and do something like this on its own...
No, thankfully SQL Server does not decide to freak out. We had a problem with a table being dropped even though only one procedure referenced it. We went through the code and could not find the drop database. We finally found it on a different proc, where the developer had been in a hurry and left a drop table at the bottom.
All Courses

From novice to tech pro — start learning today.