With the recent release of SAP Replication Server 16.0 SP03 PL04, you might want to know what we added or changed. Read below to find out.

Automatic Memory Management

SAP Replication Server can now automate memory resource adjustments for replicating up to 20 databases at the same time, while simplifying configuration and reducing total cost of ownership (TCO). This is the most important enhancement. Why? Because you can better manage multiple pairs of databases in both HADR and non-HADR environments.

SAP Replication Server uses smart memory control and tiered pooling to manage memory automatically and efficiently.

Smart Memory Control

SAP Replication Server dynamically adjusts memory resources both vertically and horizontally among its components according to real-time data loading.

• Vertical memory control – adjusts memory resources in the same component throughout all replication paths that run in parallel. Components of the same type share a certain percentage of memory resources configured by a corresponding configuration parameter.
• Horizontal memory control – uses flow control in a single replication path. If a component hangs, runs slowly, or has gone down, its upstream component triggers the flow control automatically and stops feeding more data to it.

Tiered Pooling

SAP Replication Server shares the cache resources of Stable Queue Manager (SQM) and Component Interface (CI) among different paths and instances. It also shifts the cache resources dynamically according to real-time data loading.

For more info, see Automatic Memory Management.

rs_ticket Compilation

Previously, SAP Replication Server did not compile rs_ticket executions when using RTL or HVAR. This interrupted grouping, resulting in smaller groups and thus slower performance. Now, rs_ticket is compilable and can be included in groups, minimizing interruptions in the grouping process and allowing group sizes to grow large enough to optimize performance.

This enhancement introduces a new configuration parameter, dsi_compile_rsticket, which you can use to turn on or off the compilation of rs_ticket depending on your requirements.

For more, see configure replication server and alter connection.

setuser Support in Replication

SAP Replication Server can now replicate a DDL command executed by the impersonated user using the corresponding login. This preserves the ownership of the objects referenced in the DDL command.

Set the dsi_replication_ddl configuration parameter to on to support the use of setuser in a replication system.

For details, see Limitations of setuser.

Null Values Support in Subscriptions

You can use null values in the where clause when creating a subscription.

For more info, see rs_rules.

That’s all for this post. If you’d like to know more, check out the SAP Replication Server documentation.