Store Log File

495 Words2 Pages
1. Should you store log files in the same directory as data files? Why or why not? Data files and log files both hold data. Data files hold the indexes and support structures while log files hold all the transaction data validating consistency. No you should not store log files in the same directory as data files because they both mark down, at the exactly same time and it is better for performance and is less risky should a conflict arise. 2. What are some good practices for deciding on the values for file sizing options for SQL Server databases? Some good practices for deciding on the values for file sizing options for SQL server are to configure auto growth correctly so that fragmentation does not occur, to monitor growth, to set a maximum size that’s not unlimited in growth. By setting it a maximum size you will get error messages before you have run out of disk space. 3.…show more content…
Should you create more than one log file for a database? There should only be one log file for a database because adding more logs does not boost performance. 4. List some ways in which a log chain would be broken, and describe the implications of this. A log chain may break for many reasons, and more often than not they break because of human actions resulting in some data is lost. Switching the recovery modes, using the truncate only option while taking log backups, as well as using the No_log option and database snapshot to revert the database will cause the log chain to break. To fix the chain a full backup is needed. 5. Identify the conditions under which indexes improve performance, versus when they don’t. Well designed indexes can reduce disk operations and use less system resources. Indexes can be unique, and are maintained for a table. Over indexing transactional tables with heavy activity will affect on performance negatively. Improper indexing can leave a high performing database running
Open Document