SQL Server Backup - Scripts Advantages over Maintenance Plans

-

  • We can quickly generate all of the backup tasks on an instance by running a single script
  • Issues editing or viewing maintenance plans on differing versions of sql server management studio
  • Extra layer of complexity with maintenance plans
  • Much easier to standardize, roll out and make changes in a large environment like ourselves - maintenance plans inherently slow to create and not easy to move across instances.
  • Ola Hallengren scripts are tried and tested and used by multiple large organisations. Well maintained and trusted in the industry.
  • Standardises our express backups to match our full sql server backups

Comments

Post a Comment

Popular posts from this blog

How to read and interpret the SQL Server log

-
Image
When a transaction is being committed, each step is written into the transaction log. Each value that is being inserted, updated, or deleted is recorded so that if there is a failure before the log is written to the data file, the appropriate rollback or roll forward can take place. The transaction may take and release locks on tables or indexes. To view the entries in the log there is an undocumented fn_dblog command . The SQL Server transaction log contains the history of every action that modified anything in the database. Reading the log is often the last resort when investigating how certain changes occurred. It is one of the main forensic tools at your disposal when trying to identify the author of an unwanted change. Understanding the log and digging through it for information is pretty hard core and definitely not for the faint of heart. And the fact that the output of ::fn_dblog can easily go into millions of rows does not help either. But I’ll try to giv...
Read more

ASM Proxy: New Instance Type in Oracle 12c

-
Image
Prior Oracle Database 12c, an ASM instance ran on every node in the cluster and ASM Cluster File System (ACFS) Service on a node connected to the local ASM instance running on the same host to fetch the required metadata. If the ASM instance on a node were to fail, then ACFS file systems could no longer be accessed on that node. With introduction of Flex ASM in Oracle 12c, hard dependency between ASM and its clients has been relaxed and only a smaller number of ASM instances need run on a subset of servers in a cluster. In such a scenario, in order to make ACFS services available on nodes without an ASM instance, a new instance type has been introduced by Flex ASM: the ASM-proxy instance which works on behalf of a real ASM instance. ASM Proxy instance fetches the metadata about ACFS volumes and file systems from an ASM instance and caches it. If ASM instance is not available locally, ASM proxy instance connects to other ASM instances over the network to fetch the me...
Read more

Setting MAXSIZE on datafiles using Management Studio in SQL Server

-
When attempting to set a MAXSIZE value for a non-logfile group datafile, any value greater than 2Tb (2,097,152 MB) will result in the following error: "Msg 5040, Level 16, State 1, Line 1 MODIFY FILE failed. Size is greater than MAXSIZE" This seems to be a bug in the SQL Server Management Studio.  The size restriction IS applicable when dealing with logfile datafiles but it is rather confusing why this restriction is applied to datafile files. Workaround: The simple solution is to apply the restriction as a Tranact-SQL command ALTER DATABASE [DATABASE NAME] MODIFY FILE (NAME = [filename], MAXSIZE = [size]Mb); GO
Read more