Windows Servers are in AWS will show some glitches in sometimes. My previous article explains how Windows Server 2016 had some issues with DNS Suffix and Forwarders. This time I got a chance to play around with PowerShell automations. The requirement is automatically add EC2 instances to Active directory domain during the instance launch. It might be an On Demand purpose ec2 or launched by an Auto scaling group.
According to PostgreSQL migration, we can migrate the databases and tables. I was migrating a Postgresql environment from EC2 to RDS Postgresql. I have completed the data migration. In many blogs, they have mentioned the steps to migrate PostgreSQL users to another server. But in RDS I couldn’t able to do that. I got the below error.
Before reading further about this DNS issue, I want to clarify few things.
- This issue happened only in AWS.
- Windows Server 2016 has this issue.
- On Domain Controller, I was Able to access the internet before configuring the AD/DNS.
- On Member Server, I was able to access the internet before joining the domain.
- Standalone Windows servers are working fine. Only the Domain Controller and the members of the domain having this problem.
AWS recently announced a new feature which will help to enable CDC in RDS SQL server on user databases. Here this the detailed blog post that explains how to enable this CDC for DMS service. CDC is an enterprise edition feature. But RDS SQL Server Standard editions are supporting CDC. The most important thing is we can use this feature to achieve the below things.
I have started my career to handle the databases which all are in the Cloud. Most of the database servers are in AWS EC2. AMI is one the simplest and great feature to take a VM level backup and restore it when a disaster happens. But DBAs never depend on the VM or SAN backups, so I have configured native backups for all of my database servers. But I used to choose to restore the AMI whenever we need a Dev/Test server. Because restoring a huge database will take more time and its pretty expensive operation. So I just drop the existing Dev DB server and launch it from the AMI.
First of all, I’m seeing this feature on SSMS 17, but later I found this feature came with SSMS 2016. So if you found this already then just ignore this.
In earlier versions of SSMS, If we want to get the SHOWPLAN in TEXT or Table format then we can use the SHOWPLAN_ALL query. But it would return only the plan of the query not for the result. But in SSMS 2016 or later we can see this show plan without add any additional query and also it’ll return the result of that query.