Resource required
HI Guys Does anybody know if there is a mysql mailing list where we can post for a position we have open in terms of MySQL dba. I know some mailing lists have a specific list for job ads... Regards Machiel
Re: Resource required
On Thu, Dec 9, 2010 at 1:46 PM, Machiel Richards machi...@rdc.co.za wrote: Does anybody know if there is a mysql mailing list where we can post for a position we have open in terms of MySQL dba. Here might work, I'm not aware of a specific list for MySQL jobs. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: Resource required
Well, if there is anyone out there interested. We have an opening for a Junior MySQL dba preferably with Linux experience as well. The person must however live in South Africa as the position is in the JHB area. If anyone is interested, let me know and we can discuss offline. Regards Machiel -Original Message- From: Johan De Meersman vegiv...@tuxera.be To: Machiel Richards machi...@rdc.co.za Cc: mysql mailing list mysql@lists.mysql.com Subject: Re: Resource required Date: Thu, 9 Dec 2010 14:00:18 +0100 On Thu, Dec 9, 2010 at 1:46 PM, Machiel Richards machi...@rdc.co.za wrote: Does anybody know if there is a mysql mailing list where we can post for a position we have open in terms of MySQL dba. Here might work, I'm not aware of a specific list for MySQL jobs. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: migrating a split replication
On 12/8/2010 22:50, Robert Citek wrote: Greetings to all, Can I migrate slave databases between slave servers? Imagine the following scenario: I have one master database server with 10 databases. I also have two slave database servers, one replicating 5 of the 10 databases, the other replicating the other 5 databases. Can I migrate one of the replicated databases from one slave to the other, resulting in one slave having 6 databases and the other having 4? I'm using the term migrate, but is there a more appropriate term? The docs mention various replication strategies[1], including splitting out different databases to different slaves. In the extreme case, I would like to do the opposite, consolidate databases among slaves, with the final state being all 10 databases on one slave and none on the second. Thanks in advance for your help, especially pointers to any references. [1] http://dev.mysql.com/doc/refman/5.0/en/replication-solutions.html Regards, - Robert The trick to moving replicated tables between boxes is to get both slaves to the same replication coordinates. Stop replication on one wait 5 minutes then stop it on the other. Check the binary log coordinates between the two. For the one that's looking at the older data, use a START SLAVE UNTIL ... command to get them both to the same binlog position. http://dev.mysql.com/doc/refman/5.1/en/start-slave.html Now, the copy of the data on one slave should be in an identical state to the copy of the data on the other slave (if it were replicating the table). Move the table(s) or database(s) to the other slave then undo any --replicate-* filters you may have that prevented replicating that information on the new box before the move. At this point, you probably need to copy the same --replicate-* rule you are removing from the new box to the old box so that it will stop processing commands for the data are trying to move. http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html After all looks good, START SLAVE on both machines and observe SHOW SLAVE STATUS to ensure that they are both catching up to the master. -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Design: how to prioritise 1-to-many fields
I have a typical contact database which caters for multiple email addresses with a distinct Email table keyed to a foreign key inside the Contact table, ie. a 1-to-many relationship. However, I want to prioritise these Email entries for a given Contact entry so all I can think of is to add a numeric Priority field alongside the Address field inside the Email table. Is this the best/standard solution or is there another way? gvim -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Design: how to prioritise 1-to-many fields
On Thu, Dec 9, 2010 at 3:33 PM, gvim gvi...@gmail.com wrote: I have a typical contact database which caters for multiple email addresses with a distinct Email table keyed to a foreign key inside the Contact table, ie. a 1-to-many relationship. However, I want to prioritise these Email entries for a given Contact entry so all I can think of is to add a numeric Priority field alongside the Address field inside the Email table. Is this the best/standard solution or is there another way? That would be it, I guess, yeah :) -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: migrating a split replication
On Thu, Dec 9, 2010 at 9:10 AM, Shawn Green (MySQL) shawn.l.gr...@oracle.com wrote: On 12/8/2010 22:50, Robert Citek wrote: Greetings to all, Can I migrate slave databases between slave servers? Imagine the following scenario: I have one master database server with 10 databases. I also have two slave database servers, one replicating 5 of the 10 databases, the other replicating the other 5 databases. Can I migrate one of the replicated databases from one slave to the other, resulting in one slave having 6 databases and the other having 4? I'm using the term migrate, but is there a more appropriate term? The docs mention various replication strategies[1], including splitting out different databases to different slaves. In the extreme case, I would like to do the opposite, consolidate databases among slaves, with the final state being all 10 databases on one slave and none on the second. Thanks in advance for your help, especially pointers to any references. [1] http://dev.mysql.com/doc/refman/5.0/en/replication-solutions.html Regards, - Robert The trick to moving replicated tables between boxes is to get both slaves to the same replication coordinates. Stop replication on one wait 5 minutes then stop it on the other. Check the binary log coordinates between the two. For the one that's looking at the older data, use a START SLAVE UNTIL ... command to get them both to the same binlog position. http://dev.mysql.com/doc/refman/5.1/en/start-slave.html Now, the copy of the data on one slave should be in an identical state to the copy of the data on the other slave (if it were replicating the table). Move the table(s) or database(s) to the other slave then undo any --replicate-* filters you may have that prevented replicating that information on the new box before the move. At this point, you probably need to copy the same --replicate-* rule you are removing from the new box to the old box so that it will stop processing commands for the data are trying to move. http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html After all looks good, START SLAVE on both machines and observe SHOW SLAVE STATUS to ensure that they are both catching up to the master. -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. Office: Blountville, TN Thanks, Shawn. I'll give that a try. Regards, - Robert -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Design: how to prioritise 1-to-many fields
From: gvim [mailto:gvi...@gmail.com] Sent: Thursday, December 09, 2010 9:33 AM To: MySQL Subject: Design: how to prioritise 1-to-many fields I have a typical contact database which caters for multiple email addresses with a distinct Email table keyed to a foreign key inside the Contact table, ie. a 1-to-many relationship. However, I want to prioritise these Email entries for a given Contact entry so all I can think of is to add a numeric Priority field alongside the Address field inside the Email table. Is this the best/standard solution or is there another way? [JS] Sounds about right to me, but don't use a sequence like 1, 2, 3. Use 10, 20, 30. You never know when you'll have to squeeze in a new priority level, and you don't want to have to renumber them all. Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 E-mail: je...@gii.co.jp Web site: www.the-infoshop.com gvim -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=je...@gii.co.jp -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
