Normally this would require restoring the full DB backup from Thursday night at 9:30pm onto a separate SQL server, then the last diff backup from Friday morning, and the remaining transaction log ...

You really didn't read the post did you?<BR><BR>It's not that I'm not doing backups, I'm just not sure how often teh transaction logs should be backed up, and relative to when the full/diff is run ...

But SQL Server itself provides you with no way to see what's in the transaction log. If something goes wrong with your database, you can restore from a backup -- but there's no way to see in ...

Some examples of fully durable transactions on SQL Server 2014 include system transactions, cross-database transactions, and transactions involved with FileTable, Change Tracking, and Change Data ...

If you have accidently deleted data from database tables in MS SQL Server, you can restore the deleted data (tables) using Log Sequence Number (LSN). But for this, you need the transaction backup file ...

In SQL Server 2005 and later, you can create a transaction log backup while a full or differential backup is occurring, but the log backup will not truncate the log due to the fact that the entire ...

So to avoid ginormous transaction logs; don’t use Simple Recovery Model, simply periodically back up the transaction logs so they don’t get too large, and the best time to do this is ...

Using the Transact SQL ALTER DATABASE statement to shrink the transaction log file Open SQL Server Management Studio (SSMS) and click Query Analyzer to open the Query Analyzer window. Type the ...

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). But ...