Read a story about how one company saved substantially on their cloud costs with a few simple changes and no interruptions to service.
2026-08-21
2,729 reads
RDS Custom for SQL Server recently released exciting new features related to Bring Your Own Media (BYOM) and High Availability. By using BYOM, customers may leverage their existing SQL Server licenses with Amazon RDS Custom for SQL Server, when used in accordance to Microsoft terms. This allows customers who have already purchased SQL Server licenses to save on TCO/license costs, while offloading the undifferentiated heavy lifting of database management to Amazon RDS Custom. By using Multi-AZ deployment, customers can now set up high availability for their databases.
2023-08-14
In this article, you will learn how to configure an RDS database for connections from client tools.
2022-11-21
3,236 reads
In this article we look at using AWS Performance Insights to help monitor and troubleshoot SQL Server performance issues when running on RDS.
2019-10-23
There are a number of different ways that you can host SQL Server. RDS SQL Server, for example, uses SQL Server within AWS as a simple database service, much like a more versatile alternative to MySQL. Obviously, it is a compromise, in that you lose many of the extras beyond the database. Laerte Junior answers those questions about RDS that people seem to assume you know the answers to, but which you may be too shy to ask.
2017-11-17
3,241 reads
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
By Steve Jones
Yesterday was the first day of sessions at the PASS Data Community Summit (after...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers