Amazon RDS MySQL vs Amazon RDS SQLServer
I have a data size of about 30-50 GB and its all in SQL Server 2008 present in physical servers. I am thinking of moving my data to cloud and I am considering Amazon web services as a solution.
Now Amazon provides both MySQL and SQLServer and I am trying to figure out which database is the most seamlessly and efficiently supported. SQLServer in AWS is a very new service. My requirements are following :
Scalability (should be provided for both the databases)
Replication
One important thing is that recently there has been a lot of news about Oracle trying to kill MySQL . link --> http://techcrunch.com/2012/08/18/oracle-makes-more-moves-to-kill-open-source-mysql/
What would the implications of this be on Amazon MySQl service. Also besides this I dont think integration of the current db into Amazon should be a problem but how well are both db supported in Amazon. I am looking for a detailed and clear answer. Thanks!
EDIT 1 : I am still looking for a thorough answer. Does anybody have nay idea how well is SQLserver supported in AWS ?
Related
I'm studying the possibility to switch from an rds mysql (in use and with tables and data inside) to aurora serverless mysql to try to spend less money because the database is used for few operations. I can connect to rds mysql from my pc (dbeaver, mysql workbench and so on) without problems and I can design tables, view data, create users...
Now, I've created the new serverless db and attached to the same vpc and sec group of the first one but I can't connect to it from my pc. I've read on aws guides that there are two solutions:
use ec2 to ssh tunnel requests --> but it's a payware solution;
use cloud9 and connect via terminal --> but organizing a db in this way is not so simple as using a gui client.
For this reasons I've quite understood that serverless is not a good solution for now.
Any idea or suggest?
Thanks in advance
I have defined a schema and populated with data into MySql on my laptop. However, due to the large-scale of the datasets, the computing time suffers in the following analysis stage in python. So I decide to try to move all my work to cloud. I'm wondering if there is anyway to let the server in AWS directly connect to the mysql server in my laptop so that I can use the existing datasets without recollect them.
You may be interested in AWS Database Migration Service.
You can use DMS database migration service of aws which will do everything for you.
https://aws.amazon.com/dms/
But you have to take care about foreign key and other data. sometime it is generating the error.
DMS will transfer all of your data from laptop to aws database which will be on RDS or you can choose.
I am new to Amazon RDS, and looking to get answer for my question below and couldn't find the answer on stackoverflow yet.
I have a MySQL Database on premise that I want to synchronize with the MySQL Database on Amazon RDS. I understand that replication is possible with Amazon RDS, but how about continuous synchronization? Say my existing local database has one transaction that has been made, I want to synchronize just that transaction, either immediately or by schedule, so that I don't need to replicate the whole thing to RDS.
Does RDS have this feature for MySQL or any other database?
If not, what tools should I be using? EC2 + ? ?
Or is there any database that supports this so I can just run the database on EC2?
Your best (first) option should probably be the AWS Database Migration Service. This is a migration service for exactly your use-case.
If uptime is less of an issue, you could always do a mysql_dump, move that to an EC2 instance and load that into an RDS instance.
We are migrating our MySql instance from version 5.5 in US to 5.6 in Sydney.
To reduce downtime I want to do following:
Create Readonly Replica in US
Upgrade it to 5.6
Enable automated Backup as it's required to replicate the instance
PROBLEM: When I'm trying to create a replica of a replica(selecting Sydney as destination region) I get this: "The source DB instance specified needs to be non read replica"
If I understand this http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html correctly it should be perfectly fine for me to create a replica of a replica, however I'm running out of ideas why it doesn't let me... Should I make it non-readonly?
UPDATE: It looks like you can create a Replica(5.6) of a Read Replica(5.6) in the same region, however I still have no luck creating a readReplica from a readReplica in another region.
I think you are missing the step of Promoting the Read Replica to fully functional stand-alone RDS instance.
Once you are through this step, you can then enable the Backups and Snapshots.
Excerpt From AWS Blog
Upgrade Support
Today we are enhancing Amazon RDS with the ability to upgrade your
MySQL DB Instances from version 5.5 to the latest release in the 5.6
series that's available on RDS.
To upgrade your existing instances, create a new Read Replica, upgrade it to MySQL 5.6, and once it has caught up to your existing
master, promote it to be the new master. You can initiate and
monitor each of these steps from the AWS Management Console. Refer to
the Upgrading from MySQL 5.5 to MySQL 5.6 section of the Amazon RDS
User Guide to learn more.
References : MySQL 5.5 to MySQL 5.6 Upgrade Support for Amazon RDS
New newbie question:
I have a standard LAMP stack that I have configured to use with Amazon RDS MySQL. http://aws.amazon.com/rds/mysql/
It occurred to me that RDS itself uses MySQL, therefore do I need MySQL running on my webserver? Will I see a significant performance increase if I delete/disable it?
Thanks
RDS is, in effect, a MySQL server operated for you by Amazon. If you are using RDS for your databases, you don't need your own MySQL server. (You will still need MySQL modules loaded into PHP et. al. to access RDS, though.)