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.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability