Best Practice No.37
Check Database consistency at-least once every month.
Read moreLet's learn together!
Check Database consistency at-least once every month.
Read moreDo proper capacity planning for the growth of your Transaction log file and size them accordingly – don’t leave it
Read moreIn your backup strategy avoid taking daily backups of your read-only databases, monthly full backup is more than enough.
Read moreRebuild only those Indexes where the fragmentation level exceeds the threshold value of 30.
Read moreConfigure a dedicated NIC (network card) card for your Backups on your busy systems.
Read moreAlways use SQL Server Configuration Manager to change Service account for any SQL Related Service.
Read moreWhile referring objects in Stored Procedures, functions, views and Triggers always use Fully Qualified (Multi Part) Name of the object.
Read moreEnable “remote admin connections” on all your SQL Servers to be able to take DAC (Dedicated Admin Connection) remotely.
Read moreApply Password policy on all SQL Server logins (along with password expiration if possible) to avoid any security compromise.
Read moreUnderstand NOLOCK hint before using this in your transactions\applications – the data you are reading might not be consistent (Dirty
Read more