I read a blog post on this topic recently.

I like the approach depicted in the article - try to resolve and then rollback after having run there enough troubleshooting to...

microbot

Nothing wrong with the CTE that you were using from what I can tell. That said, I didn't do an intrusive code review either.

All that was needed was the...

I know Bob (Dixie) has done a masterful job with this script.

Here is a slightly different route I have taken in the past that was also quite efficient and performed...

That explanation is...

LOL

SELECT person.personID

, cs562.personID

, cs562.attributeID

, cs562.value

, cs562.[date]

, cs563.personID

, cs563.attributeID

, cs563.value

, cs563.[date]

, cs564.personID

, cs564.attributeID

, cs564.value

, cs564.[date]

, cs565.personID

, cs565.attributeID

, cs565.value

, cs565.[date]

FROM Person cs562

INNER JOIN sProgram sp

ON cs562.PersonID = sp.PersonID

join...

You need to find what query is running that is causing the massive growth.

Here is an article with a technique that could be applied...

http://www.sqlservercentral.com/articles/Log+growth/69476/

I like the idea of the chaos monkey. Outages need to be tested and processes practiced. Without the practice, people forget what to do or they act slowly...

Yeah that is funny...

MAN

rjoseph (3/3/2014)

---

Hello Sathish,

When I parse this script, I got no errors but when tried to execute it to get the backup history on SQL 2000 or 2008 databases from MSSMS...

Steve Jones - SSC Editor (2/28/2014)

---

That would be quite a thriller. I need to pick up his...

David.Poole (2/28/2014)

---

I picked up a few Dean Crawford books on a 2nd hand stall. Enjoyable escapism, sort of x-files meets Clive Cussler.

Hollywood seems to be doing more reboots than...

daisy