AWS -RDS-Issue

RDS Server not Configured Correctly

The following error can occur when running the rds_restore_database stored procedure.

Solution The above error occurs if the SQLSERVER_BACKUP_RESTORE option has not been applied to the server (see the original article for details of how to do this).

Issue 2 : Cannot Restore a Database and Replace an Existing Database

Solution In this case this has occurred because it’s not possible to overwrite an existing database while restoring a backup, unlike a normal SQL Server restore. In other words, there’s no equivalent of the ‘WITH REPLACE’ option in RDS. Instead you have to delete the database yourself, before running the restore command above.

Issue 3 : Exceeding the Limit of 30 Databases per Instance

RDS limits you to 30 user databases per instance. If you try and exceed that limit then you’ll get the SQL error below (if trying to create the database using SQL).

If you try and do this via the GUI then you’ll get a similar error : 

Issue 3 : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible... The wait operation timed out – Microsoft SQL Server, Error: 258

Solution The access rules enforced by your local firewall and the IP addresses authorized to access your DB instance might not match. The problem is most likely the inbound rules in your security group.

Issue 3 : How do I troubleshoot Amazon RDS for SQL Server Windows Authentication with AWS Managed Microsoft Active Directory?

• The Active Directory is unavailable

  • I receive an error that says "Failed to join a host to a domain"

  • I can't log in to the DB instance using Windows Authentication

Solution :If the VPC and the directory are in different AWS Regions than the DB instance is in, you won't see the directory listed when you create or modify a DB instance. To resolve this issue, be sure that the DB instance is in same AWS Region and the same VPC as your directory.