And there will always be substantial I/O bandwidth consumption. But when it is executed in parallel, with multiple targets, and using compression to save space then the impact to CPU When backups are executed using a single process, without parallel targets, and without compression the use of CPU resources is quite light. SQL Server Backup has varying impacts on CPU resources. For JAVA stack systems there can be some additional configuration information that is maintained at the Operating System level and should be attended to as well. For ABAP stack Netweaver systems, everything that is required for SAP (business data, metadata and ABAP applications etc) is included in one “” database. Users and batch jobs will continue to use SAP applications without problems. SAP databases should be backed up online with a Truly Mimic PRD with QA and/or Stress Testing Serversīack up system databases after configuration changes Know your chosen High Availability (HA) and Disaster Recovery (DR) solutions Here are the Best Practice recommendations:Įstablish Standard Operational Procedures The goal of this list is help your SAP-SQL Server environment be more stable and reliable, and for your end users to be happier. This post might perhaps benefit that situation. job transitioning or scoping, work overload, etc.). But, unfortunately, that isn’t true for those environments where DBA responsibilities continue to be overlooked for any number of reasons (e.g. For most of this audience, such critically important items are already well understood. The list is weighted heaviest from a Disaster Recovery perspective. The following recommendations are best practices for maintaining a SQL Server Netweaver database for an SAP implementation.