Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-08-12 : 07:53:58
|
| Eric writes "I understand you get alot of questions so I'll try to cut right to the chase and spare you the back story. I read in an SQL book that "A (full) database backup also backs up transaction log records but doesn't store empty pages or remove any transaction log records from a database." The backup I am looking at is the first backup that was done on the database, so the log file should have been full since it had not been backed up prior to that. The log file was not explicitly backed up on this date. When I restored the database and log file from the full backup the log file was empty and was only a few megs rather than 1.3 gigs which is the size that it is allowed to grow to. Is there a way to view the log file as it was when the full database backup was performed? Thank You,Eric" |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-12 : 11:05:56
|
| What this means is that there was virtually no 'active' log when the database was backed up (i.e. no un-committed transactions that would need to be recovered during restore to give a transactionally consistent view of the database). Backup won't backup the entire log file unless that log is needed.What recovery mode is the database in?Paul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
 |
|
|
|
|
|