1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
-1
Hi Vinnie,
You cannot create indexes on any table under "rdsadmin" database. That database is being used by our automation system and we do not provide any write operations to be performed on any of table/objects in that database.
But this table should not be used in any of the user processes/executions. This is only used for our automation/monitoring tasks by RDS Service.
So you should not worry about the execution times for this table.
Thanks for your reply, however this is not the answer to the question.
I am 100% aware of what the table is and what rdsadmin is. However, when you run "back_up" or "restore", it creates a new entry in this table. This is an async task system ran by AWS.
Now when you have ran this over 10k times, then you have the problems of "no indexing" and costly sql queries. Note that I have ran a script that tells me the costs of all queries in my db instance, which is where I have come up with this problem. I am not just making this stuff up, this is a major performance issue on RDS.
This is an oversight from AWS, as they have not indexed these tables as part of the build. Either the rdsadmin tasks table needs to be purged of its data regularly, or indexes placed.
Unless this problem is fixed, I am going to abandon RDS in favour of running my own EC2 with SQL SERVER, where I have full control over it. It is much cheaper anyway, and TBH what benefits are there other than a 30m autoamted backup?