GSquared (1/6/2011)

---

GilaMonster (1/6/2011)

---

Craig Farrell (1/6/2011)

---

Best way to start that research is get yourself a small partition on a drive (usually your C:\ is smaller), create a database, and fill it with stuff until your Transaction Log is out of room. You'll get some errors. Start researching those errors. It's a common issue.

Good idea, but I'd suggest limiting the size of the log, not filling C drive up. Windows gets a little twitchy when there's no free space on C.

Which, to me, sounds like a good idea for disaster prep. If you've never had to deal with SQL on a server that's twitchy, you'll be tharn the first time it happens.

Just don't do it on a production server. VM or re-imagable test box is best.