Category: Amazon RDS Custom

This is the second post of a two-part series. In Part 1, we explored how you can use Automatic Data Optimization (ADO) and Oracle Information Lifecycle Management (ILM) policies for data compression. In this post, we demonstrate how to use Heat Map statistics to monitor data usage and integrate this information with hybrid partitioning and ILM data movement policies to move data to more cost-effective storage solutions.

In this two-part series, we demonstrate how to optimize storage for Oracle database workloads on AWS by using Oracle’s built-in features, such as Heat Map, Automatic Data Optimization (ADO), and hybrid partitioning. These features help classify data by its lifecycle stage and automate data management tasks to significantly reduce storage costs, while enhancing database performance, especially for growing datasets. In this post, we explore how to use ADO and Oracle ILM policies to automatically compress data based on usage patterns.

Amazon RDS Custom for SQL Server now allows you to directly join your DB instances to the domains of Microsoft Active Directory (AD). In this post, we show how to join RDS Custom DB instances to an AD for Windows Authentication. This applies to AD domains running in a self-managed environment either on premises or Amazon Elastic Compute Cloud (Amazon EC2) and AWS Managed Microsoft AD.

In this post, we discuss how to determine the causes of an INCOMPATIBLE_CREATE state of an RDS Custom instance because of incorrect instance profile permissions.

Amazon RDS Custom for SQL Server allows up to 5,000 databases per instance. However, the number of databases that can be restored to a specific point in time using point-in-time recovery (PITR) depends on the instance class type. In this post, we show how to use native backup and restore commands to achieve PITR for databases that aren’t eligible because of the instance type limitation. We present two solutions: one applicable to all versions of RDS Custom for SQL Server and the other for RDS Custom for SQL Server version 2022.

In this post, we explain how to perform a database minor version upgrade (patch) with Multi-AZ on CEV instance, where RDS Custom performs rolling upgrades, so you have an outage only for failover period and the time needed for post-upgrade scripts until the instance is fully operational.

In this post, we show you how to implement Application Continuity in an RDS Custom for Oracle environment using a sample application. We also show you how to test the implementation to see that, when an outage occurs at the database tier, the application recovers and resumes without any data loss—automatically and transparently—along with the database failover. Finally, we show you how to verify the results before cleaning up the environment.

This is the second part in a two-part series on how to migrate a multi-TB database to Amazon Relational Database Services (Amazon RDS) Custom for SQL Server. RDS Custom for SQL Server is a managed database service that automates database setup, operation, backups, high availability, and scalability while providing access to both the database and […]

Amazon Relational Database Server (Amazon RDS) Custom for SQL Server is a managed database service for applications that require operating system access and database customization that is not available in Amazon RDS for SQL Server. The ability to encrypt an application’s connection to RDS Custom is a common security requirement. Network encryption protects data in […]

Adopting lift and shift or rehost migration approach can be a viable option for time-sensitive scenarios, particularly when transitioning from an on-premises data center environment. However, it’s crucial to ensure that the chosen migration strategy aligns with your organization’s overall cloud adoption strategy to realize the long-term benefits of cloud-native architectures. For many applications, a […]