Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim Chapman discusses the perils of not handling SQL Server log growth ...

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is ...

So I'm trying to figure out when I should be backing my transaction logs relative to my full/diffs. It seems like right after would be when I'd want to have the checkpoint happen, or does it ...

Under SQL Server 7.0, for example, you can specify that logins — both successful and failed — be written to the Windows 2000 (or Windows NT) application log, which you view using the Event Viewer.

Drive Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG Did you have any previous SQL installs on the machine?

In SQL Server, the database can be stored in different files and filegroups. If your database is small (100 MB or less), you do not need to worry too much about files and filegroups.