InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 05:02:08 GMT20http://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxIf the database needs to be in FULL recovery (that means you need to be able to recover all or nearly all transactions during a restore) then you must run regular transaction log backups. You should also be running regular full backups. The simplest way to do both is by creating a maintenance plans and scheduling them to run regularly. If you want to guarantee that you can recover to within 30 minutes of a failure, you should run transaction log a backup every 30 minutes.Your maintenance plans also need to clean up old backups that are no longer necessary.For DBs using FULL recovery model I typically run a FULL backup weekly, a DIFF backup daily, and LOG backup every 30 minutes. The maintenance plan that runs the FULL backup deletes the old DIFF backups. The one that runs the DIFF backup deletes the old LOG backups.Wed, 09 Jan 2013 05:52:06 GMTchuck.hamiltonhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxIf you have databases in "FULL" recovery you need to backup the transaction logs. The easiest way to set this up as a new user is to use the Maintenance Plan Wizard. Start a new plan and give it an appropriate name Select "Backup DB Transaction Logs"Set the Schedule to be Daily, every 15 minutesSelect "All databases""Create File for every database"Select the folder location. I like to choose "sub directory for each DB" to keep it organized. I suggest you do this right away to protect your data.Once you have it running, you can do more reading and decide how you want to fine tune your processes, and perhaps be more selective in what and when you take backups. But right now, it's better to back up too much and too frequently.Tue, 08 Jan 2013 07:36:16 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxNope.That will break the log chain, prevent further log backups, essentially put you in simple recovery model (which means you cannot meet your SLAs), then shrink the log to a stupidly small size.Please read the article I referenced.Tue, 08 Jan 2013 05:07:43 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxPlease confirm if the below points are true for full recovery model without changing the recovery model:-The below query will take the back up transaction log and shrink the log file:-USE DBNAMETake a DB Full bacp of DBTake a back up of log:-backup log DBNAME with no_logShrink log:- DBCC SHRINKFILE DBNAME_Log, 10)Tue, 08 Jan 2013 04:39:01 GMTDIB INhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspx[quote][b]DIB IN (1/8/2013)[/b][hr]database to be Full recovery.there will be no data loss or minimum data loss.[/quote]Simple recovery model doesn't support that. Have another read through that article, specifically the sections on log backups.p.s. Don't shrink the log to 0. Once you have log backups running, you can shrink the log to a sensible size (0 is not sensible)Tue, 08 Jan 2013 04:15:35 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxThen you need to ensure that you setup transaction log backups otherwise the issue will keep happening.Go back to the business and ask them what the recovery point objective is for the database, that will determine how often you need to backup the transaction log.If they can loose 15 minutes worth of data, then transaction log backups need to run every 15 minutes etc.If your not bothered about restoring to a point in time now, then yes setting to simple and shrinking will be one option. If you want the log chain to be intact, do a manual backup of the log, then shrink, which will give you the recoveryability which you get from full without breaking the chain.Tue, 08 Jan 2013 03:56:58 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxdatabase to be Full recovery.there will be no data loss or minimum data loss.Tue, 08 Jan 2013 03:53:45 GMTDIB INhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxDo you need the database to be in FULL recovery?As I have said what is your acceptable amount of data loss? How much data can you afford to loose with this database?Tue, 08 Jan 2013 03:48:34 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxWell i have gone through the articles mentioned above. Currently there is no transaction back up. database is in full recovery. Will it be useful if we run the below query when there is no transaction active? USE DBNAME;GO-- Truncate the log by changing the database recovery model to SIMPLE.ALTER DATABASE DBNAMESET RECOVERY SIMPLE;GO-- Shrink the truncated log file to 1 MB.DBCC SHRINKFILE (DBNAME_Log, 1);GO-- Reset the database recovery model.ALTER DATABASE DBNAMESET RECOVERY FULL;GOTue, 08 Jan 2013 03:46:26 GMTDIB INhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxYou should keep it to simple recovery model, untill u dont think your all transactions should logged in log file till the database backup process and it increses size of your log file..OR you should take backup periodically..Tue, 08 Jan 2013 03:38:12 GMTAadhar Joshihttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxPlease read through this - [url=http://www.sqlservercentral.com/articles/64582/]Managing Transaction Logs[/url]Tue, 08 Jan 2013 02:37:45 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxDo you do transaction log backups?Do you need the databases to be in full recovery?What is your acceptable amount of data loss? What is your recovery point objective? Can you loose a days worth of data with no affects to the business, or can you only loose minutes?How often do you do full or differential backups?Tue, 08 Jan 2013 01:37:27 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxrecovery model is fullTue, 08 Jan 2013 01:35:52 GMTDIB INhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxAs you state that you are a new DBA, I would strongly recommend reading the Accidental DBA guide (link in my signature below) as it will cover some of the main issues which are faced in the world of SQL.But as Bhuvnesh, what is the recovery model of the database? If FULL or BULKLOGGED do you have transaction log backups running?Tue, 08 Jan 2013 01:15:11 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspx[quote][b]DIB IN (1/8/2013)[/b][hr]If in a database MDF file Size is 10 GB and LDF file size is 50 GB.What are the steps require to reduce to log file size.[/quote] LDF will grow it should. it is its nature. but we need to manage the files ? whats the recovery model ? simple or full ? are you taking its regular backup ? see this link [url]http://www.sqlservercentral.com/articles/Administration/64582/[/url]Tue, 08 Jan 2013 01:03:55 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1403996-146-1.aspxi am new in DBA.If in a database MDF file Size is 10 GB and LDF file size is 50 GBWhat are the steps require to reduce to log file size.Tue, 08 Jan 2013 00:27:34 GMTDIB IN