New answers tagged

0

Problem could also be the encryption key...If you are using IAM for security and have correctly configured your security groups, each user will have an encryption key 'certificate' that needs to be downloaded to the connecting client! Had something similar beat me up for the better part of a few hours when setting up our SQL Server RDS instance... Doh!


2

Sounds like the connection is successful but SSMS is having trouble loading metadata to populate Object Explorer. I would try opening SSMS without connecting to this server, open an empty query window, disable IntelliSense, and then change that query window's connection. Also your copy of SSMS is quite old, I would strongly consider applying SP3 + CU1 to ...


0

One solution proposed in https://forums.aws.amazon.com/thread.jspa?threadID=45258 requires setting backup retention period to zero. Which should mean no automatic backup! But you can still take manual snapshots.


0

You should be able to do the work with CLOUDBASIC RDS AlwaysOn SQL Server Replication product available on the AWS Marketplace: CLOUDBASIC RDS AlwaysOn Replication It supports all SQL Server versions, including Express and Web Edition. The product is designed for Disaster Recovery, data locality and reporting, but can be used for migrations as well.


2

Un-panic. Your queue had lots of rows inserted and quickly deleted, correct? And now it has very few rows in it? Specifically, about 17K? More importantly, there was, at one point, maybe a million rows? So the tablespace expanded to handle it, but has not shrunken. The dump dumped only the data for the current 17K rows. The reload loaded only those ...


2

Please note this Pictorial Representation of ibdata1 (from Vadim Tkachenko) You have many moving parts inside ibdata1 Data Dictionary Double Write Buffer Insert Buffer Rollback Segments Undo Space Almost 3 years ago, I wrote a post addressing why ibdata1 can grow too fast : How can Innodb ibdata1 file grows by 5X even with innodb_file_per_table set? ...


0

When we are doing Alter on innodb the "tmpdir" need to be observed. The Erro 1034 : Key repair is definetly because of "tmpdir" full, and your alter will throw the error. So I suggest when the Alter is got triggered give one more eye on your "tmpdir" utilization. If tmp is using 100% there you can see this error for sure :).


0

17 minutes is not a reasonable time to wait. Try to provide an index hint: SELECT * FROM contact USE INDEX (IDX_LIST_ID_SUBSCRIBED_DELETED_EMAIL_ADDRESS) WHERE list_id = '014c7cba-c124-11e5-b4ea-0a4287b2e8c5' AND subscribed = 1 AND deleted = 0


0

This is not possible using RDS snapshots. AWS RDS Snapshots are "hidden" (though almost certainly in S3). They are not accessible to you, the user, at all. They can only be restored to RDS. The only way to get data out from RDS MySQL instances is to export it using mysqldump ...


0

A couple of things: The tutorial assumes that you have already created an EC2 Security Group named WebServerSG, as shown in the previous step of the tutorial. As of this writing, the auto-complete logic for the field in question keys off of the security group's Group ID rather than the Group Name. The tutorial incorrectly suggests the opposite. You can ...



Top 50 recent answers are included