Tag Info

New answers tagged

0

You are using a scalar function in your WHERE clause, which means that function needs to be called multiple times. You should consider calling that function once (since you already know the values of @N and @Ticker) at the start of the script to return the scalar and then pass that scalar in as a variable. While not perfect, this should reduce the multiple ...


1

It is not possible to restore an EC2 snapshot to RDS. It is possible, though not necessarily advisable, depending on the circumstances, to restore an EC2 snapshot to another server.


0

DISCLAIMER : I haven't tried this myself What you asking for is somewhat rare. Nevertheless, it is possible. Here is a link to Looker.com to explain how. Basically, you do the following: Create a read replica Create a Custom DB Parameter group Tweak the read_only setting in the Custom DB Parameter Group When replica has been created, ... you modify ...


0

You cannot get around this with MySQL RDS, ... EVER !!! Can we disable binary logging for one specific session or user in AWS RDS MySQL Documentation says it requires SUPER even at the session level The Scale-Out Blog: Replicating from MySQL to Amazon RDS says We will take a recent replicator build that contains the RDS changes, which are documented ...


2

The paths in the generated script are the locations where the data and log files should be on your laptop. If you copy paste the script to amazon AWS that will be the location where the files are created when you create the database. If that path doesn't exist on the Amazon instance you will get errors. You could comment out the lines and then the files ...


3

This happens when not having USAGE privilege on any of the schemas of search_path. By default the pseudo-role public (all users) has this privilege on the publicschema, so this error happens only after revoking it explicitly with: revoke usage on schema public from public; This is required when it's not desirable that people peek into other people ...


0

Look for Amazon instructions. With RDS, the instructions are roughly: Upgrade the Slave first. Replication works when the Master is 'older'. Failover, but do not turn on the Slave. Upgrade the Slave (was Master) Turn on replication (START SLAVE) Wait for replication to catch up before using the Slave.


5

This is due to MySQL Master and Slave version mismatch The message below is clear, and confirms the master/slaves run different versions. The variable SERVER_UUID is not supported with MySQL 5.5 but is supported with MySQL 5.6 2015-06-29 11:01:01 8026 [Warning] Slave I/O: Unknown system variable 'SERVER_UUID' on master. A probable cause is that the ...


0

If you cannot use the RDS CLI, set proper DB Parameters or other means to set slave-skip-errors=1062, you are better off just creating a read replica to make a new Slave from the Master then dropping the old Slave that had the 1062 error. I have mentioned MySQL RDS Read Replicas in the past May 21, 2013 : Best strategies to have a backup of an RDS MySQL ...



Top 50 recent answers are included