.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

TLog backup size in Full vs. Bulk logged recovery model.

Posted By:      Posted Date: December 04, 2010    Points: 0   Category :Sql Server
When executing some minimally logged operations one can notice higher in TLog growth in Full recovery vs that of Bulk. But when it comes to talking a TLog backup one can notice its bigger (because the modified extents are also backed up along with TLog) Questions: 1. Are the pages backedup only those which were modified by minimally logged operation? 2. TLog backups in bulk recovery will be bigger than those from Full recovery but it depends if or not any minimally logged operations were done.

View Complete Post

More Related Resource Links

Question on Bulk-Logged Recovery Model


After reading this MSDN article , I'm a bit baffled about how bulk operations are logged...

If data extents are used for log backup, what data will be logged? Won't it be the data at a stage after several committed transactions have already been performed on those extents?

Just for my better understanding of the concept: Isn't it necessary to log the extents containing data at the time the bulk operation occured?

Is this the reason why restore operations cannot be performed on a point-in-time basis?

Thanks for helping me understand...

Bulk and full recovery model


hi team,


i have one dought,


in Full Recovery model have bulk log opertaions restore.

bulk log Recovery model also have bulk log operaions and bulk insert operations 


what are the difference in these two bulks could any body please explaine me.





BULK INSERT under the full recovery model


Hi Experts, is there any performance difference between BULK INSERT and row-insert operations under full recovery model? My database is configured as full recovery model, so I want to konw do I still try use BULK operations to modify data? Thanks!

Simple Recovery Model Yet Transaction Log Is Full

Hi there, There's a database which has been configured with SIMPLE recovery model but yet the transaction log will grow and fill up the disk at times. Is there anything one can do to prevent the log from filling up the disk? Thanks in advance.

how to understand full recovery model can restore to the point of failure


if I backup log hourly, 50 minutes after last log backup, sql server corrupts, I guess I can only restore to the last tlog backup, how to understand restore to the point of failure?

also if I use simple recovery model, backup differentially every hour, do I have the same data protection? I know answer is no, but how to understand it?



simple recovery model, backup plan best practise

any guideline on backup plan for a simple recovery model? if there is no differential backup, only has daily full backup, when the sever crashes, will it lose all info after last backup? if the data file crashes, but log file exists ok, is it possible to restore info after last backup? such as tail log backup?

Is a database online when it is changed from full to simple recovery model?



We have some databases that occaisally have very large ldf files and I have learned that the best way to shrink the ldf file is to change the backup mode to simple, shrink the log file, convert it back to full and do a full database backup so that the log file backups will run again. My question is during this process is the database available to the end users? When you guys do this do you feel it is nessesary to let the end users know or will they not notice what is going on?



Thanks! Kevin

SQL2008 - Cannot Restore a new database from a full backup of a different one, database in use

I am trying to restore a brand new database from a copy of another one and am encountering an error message stating: System.Data.SqlClient.SqlError: The file <Backup source database file location> cannot be overwritten.  It is being used by database <Backup Source Database>. (Microsoft.SqlServer.Smo) I am running the Restore procedure with the REPLACE option and am wondering why it is stating that the source database is the database in use when I am trying to restore and overwrite a completely different database. This issue happens when running the replace both in C# using SMO and when manually restoring with SqlServer Management Studio Interesting note is, the original source database is created / deployed using a database project within VisualStudios 2010 and then deployed to SqlServer through VisualStudios. Any thoughts on why this is happening? Thanks in advance for any help!

Full Backup

Hi All, I want to do a Full Backup Daily but is there a way of doing a complete Full Backup by writing over the pervious day full backup. I have done Differential backups by using INIT keyword but I wanted to be sure that I can use it for Full backup as well. Thank you    

calculating the size required for backup of database

Hi, How to calculate the size required to take backup of a database in mssql 2000.the results returned by sp_spaceused differ too much from the actual size taken on the disk. Thanks in advance

Full database backup takes so long

Today several full database backups took so long. Normally it took 2 hours to backup. But today the 5 backups didn't finish by the end of the work day. The backups went well until yesterday. I don't know what happened overnight. Is there a performance tool embedded in SQL Server? How can I find out why the backups take so long? What could be the possible reasons? Thank you,  

Full Farm Backup Fails on Windows Sharepoint Services Search Database

I am just now starting to us central administration to backup the entire sharepoint farm.  All content backups fine except for the Search Database.  In looking through the backup log, it appears that the search database may not exist.  How can I determine if the search database actually does exist and if it does not can it be recreated?

SharePoint 2010 Content DB Recovery Model

Hello Everyone, the following link states that the content db for SharePoint 2010 uses simple recovery model. http://technet.microsoft.com/en-us/library/dd207314.aspx   whereas this link at SQL Server documentation says that Simple model is not suitable for production systems because it has risk of data loss http://msdn.microsoft.com/en-us/library/ms189275.aspx   These two look totally contradictory to me.  

How to determine a partial vs full backup set?

I've written application that uses SMO to backup / restore database. I largely mimic the interface found in SQL Server Management Studio 05. In the restore display I display all available backup sets and I query msdb to get the info for each backup set via the following query: "select backup_set_id,name,description,recovery_model,type,server_name,database_name,position,  backup_finish_date,backup_size,user_name,expiration_date  from msdb.dbo.backupset Where msdb.dbo.backupset.database_name = '" + dbName.Text + "'"; How do I determine if the backup was full or incremental, so I can set the Partial property??

full text catalog size?

Is there a good way, using TSQL, to examine the size of a given full text catalog?   Does SQL compress the full text catalog?   SQL 2008 SP2   thanks  

Size limit for STSADM -o backup


Hi all

Is there a size limit for the .dat backup that can be taken using STSADM -o backup

and for the .dat that can be restore using STSADM.

Thanks in Advance


Database Switched to Simple Recovery Model


Hi there,

We came across a situation where the transaction log was full and we extended the disk that holds the transaction log. What happened after that is the log truncated and we noticed the recovery model of the database switched from FULL to SIMPLE. Does anyone come across this behaviour?

Thanks in advance.


Yong Hwee

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend