Working efficiently in a production environment can profoundly impact performance. In this article, learn 5 tips to make the job of an SQL Server DBA easier.
Join the DZone community and get the full member experience. Working efficiently in a production environment where even a minor change can have a profound impact on performance, there are some tips you can follow to ensure the best possible database performance. In this article, we will discuss five tips to make the job of an SQL Server DBA easier in a production environment. While backups are an important part of an effective recovery plan, frequent backups can cause issues if the available storage space is limited. In such a situation, deleting old backups can help clear the storage space. The Maintenance Cleanup Task feature (in SQL Server 2005 and later versions) available in the Maintenance Plan Wizard can help remove obsolete database backup files. Using Maintenance Cleanup Task, you can remove backup of all types (i.e., Full, Differential, and Transaction Log) from the given location. However, you can only delete one type of file in each Maintenance Cleanup Task. In other words, you cannot remove transaction log files (.trn) and full or differential backup files (.bak) in a single task. You need to create two tasks to purge the files. To delete the old SQL backup files created using Maintenance Cleanup Task, do the following: Note: You may also create a new job schedule to run the maintenance plan of deleting old backup files weekly. For more information about Maintenance Cleanup Task, see Microsoft’s guide. When a maintenance plan is created in SQL Server, a user logged into the server is the plan’s owner.
