Amazon RDS

SQLServerCentral Article

Cloning Master Admin User Permissions in Amazon RDS for SQL Server with Fine-Grained Control

  • Article

This article explores how to securely clone the master user permissions in Amazon RDS for SQL Server using a custom stored procedure, usp_rds_clone_login. It outlines a step-by-step process to generate, review, and apply a script that replicates server- and database-level access from the master user to a new login without directly exposing elevated credentials. The guide emphasizes the principle of least privilege, supports named account management, and enables transparent, auditable permission handling for DBAs and applications. Designed for secure and scalable environments, this solution enhances operational security while maintaining administrative flexibility in Amazon RDS.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2025-07-09

752 reads

SQLServerCentral Article

Creating a Linked Server in Amazon RDS for SQL Server: A Step-by-Step Guide

  • Article

Linked servers in Amazon RDS for SQL Server allow seamless connectivity to remote databases for distributed queries and data integration. In this article, I guide you through the step-by-step process of creating a linked server using SQL commands, from setting up authentication to testing the connection. Learn best practices, advanced configurations, and essential considerations, including why you can't use SSMS for linked server setup in RDS. This professional guide is tailored for experienced database administrators looking to optimize cross-server operations.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2025-01-29

1,707 reads

SQLServerCentral Article

Amazon EC2 | Creating a Connection to an Amazon RDS Instance

  • Article

In a previous article, we showed how to expose an Amazon RDS instance to the public internet securely for direct access to the database. In this article we shall configure an Amazon EC2 instance for network access to an existing Amazon RDS instance. The purpose of this would be to make sure that if we deploy an application to this EC2 instance, communication from the client to the RDS instance would be smooth.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(2)

You rated this post out of 5. Change rating

2022-12-05

2,349 reads

Blogs

Building the Team: Roles and Responsibilities in FinOps

By

In my experience, FinOps success has never been just about tools or dashboards. It...

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server: 

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this: 
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers