Asked 12 years, 8 months ago. Active 3 years, 11 months ago. Viewed k times. Improve this question. Add a comment. Active Oldest Votes. This is the recommended solution for most of the cases. If you have to be able to restore to the exact point in time - use FULL recovery mode. In this case you have to take regular Transaction Log backups.
The log file will be truncated at this time and would not grow beyond certain limits. Improve this answer. Ross Ross 5 5 silver badges 7 7 bronze badges. Just curious: While during taking backup, what will happen if a transaction is being done?
One process is taking backup of the file while another process is busy writing to the file? Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 1. Hot Network Questions.
Question feed. Accept all cookies Customize settings. For discussions on features exposed through tools, please post to the directly-related forum 1 3. Sign in to vote.
MDF file size is not too large, its around 4 GB but. LDF is creating problems, its size is 17 GB now. Please suggest me how to decrease its size.. My machine is going too slow and its taking quite long time to execute queries. Thanks' Kalpesh Mahajan. Monday, June 1, AM. Hi, Check this link to srink. SQL Server is smart in selecting great default options for a new database. If you can afford to lose the changes between backups to keep maintenance simple in most non-critical databases it is a reasonable compromise and you backup your database regularly, then the simple recovery model selected by default is appropriate for you.
However even in this case if you ever had massive data operations, you may notice that the size of your transaction log LDF file is huge.
0コメント