Phil Factor (6/18/2010)

---

[p]I thought that it was a good idea to re-feature the article, because it provoked an interesting debate, and I enjoyed reading through all the points that were...

Charles Kincaid (6/15/2010)

---

YSLGuru (6/15/2010)

---

MANAGEMENT - The problem (from personal experience) is that far too foten the managemnt or decission makers are often programmers themselves and unless they have at least...

MANAGEMENT - The problem (from personal experience) is that far too foten the managemnt or decission makers are often programmers themselves and unless they have at least a respect for...

OK, My Turn. This is something I have suspected for some time but only recently got verification on.

In addition to offensively breaking just about every rule in DB Design,...

DeronDilger (6/2/2010)

---

Not having "29 years of...

Thanks Imu92 & bteraberry for giving me some starting points

George

I have not yet done this. Our DB is almost 200GB and we have only a few hours of...

RonKyle (6/2/2010)

---

Not everyone is an expert at every part of SQL Server and while this persons article does not show the best approach to this, it is sufficient enough to...

Martin Mason (6/1/2010)

---

YSLGuru (6/1/2010)

---

Martin Mason (6/1/2010)

---

I couldn't disagree with an article more. The author should read Chapter 2 of Kimball's The Data Warehouse Toolkit for a proper way to handle...

Martin Mason (6/1/2010)

---

I couldn't disagree with an article more. The author should read Chapter 2 of Kimball's The Data Warehouse Toolkit for a proper way to handle dates and times...

Neepa (5/24/2010)

---

Also, think about getting a backup tool like sql backup from RedGate or Litespeed from Quest. They compresses the backups very well and have proven blessings whenever I ran...

george sibbald (5/24/2010)

---

reindexing operations can cause this behaviour. Be warned if you switch to full recovery mode whatever the process was will no longer be minimally logged, so you will...

UPDATE - RESOLVED (somewhat)

I managed to correct this issue by switching our RECOVERY MODEL to use FULL (instead of BULK-LOGGED).

With some additional searching I found a post at the SQLMOnster...

Jeffrey Williams-493691 (5/21/2010)

---

I have read through this multiple times now, and I don't see where you state what the actual error is. What error are you getting?

As others have...

george sibbald (5/21/2010)

---

I wouldn't drop an ldf because log backups are failing, that way heartache lies. Run a dbcc checkdb on the database.

Is the log growing if the log backups...