Comments for OneFreeVoice http://blog.onefreevoice.com A Blog About Databases and Stuff Sun, 05 Apr 2009 04:01:31 +0000 http://wordpress.com/ hourly 1 Comment on Creating an Intermediate Replication Layer by How MySQL Sandbox Solves All My Problems « OneFreeVoice http://blog.onefreevoice.com/2008/07/15/creating_intermediate_slaves/#comment-479 How MySQL Sandbox Solves All My Problems « OneFreeVoice Sun, 05 Apr 2009 04:01:31 +0000 http://blog.onefreevoice.com/?p=103#comment-479 [...] getting complicated? To you have two many slaves running off a single master and need to introduce a new layer. Mysql_sandbox comes with several prepared schemes out of the box, including standard, circular, [...] [...] getting complicated? To you have two many slaves running off a single master and need to introduce a new layer. Mysql_sandbox comes with several prepared schemes out of the box, including standard, circular, [...]

]]> Comment on Choosing the Tools for Release Management by Gregory Haase http://blog.onefreevoice.com/2009/03/22/choosing-tools/#comment-475 Gregory Haase Sun, 22 Mar 2009 15:00:44 +0000 http://blog.onefreevoice.com/?p=158#comment-475 Wow. I never thought about packing up releases with GNU Make. I'm glad you posted that comment. The tools that I'm most familiar with are ant and lately maven. These are arguably java-centric, but then I've been working in shops that are mostly java-based. Bottom line - I think using GNU Make is an excellent idea. If it is something that you are more comfortable with than other tools, or if your application development is compiling with Make then it should prove to be the best tool for <em>your</em> job. I think you've already shown that the tool can do what you want it to do - or you wouldn't be using it. The one thing that Maven does nicely is integrate with source control. You can configure it so that when you create a package, it first creates a tag or snapshot in your repository, then it uses that tag for the build. This ensures that at any given point in time, there is no confusion about which version of the code is in your build. I would be curious to know if Make has this ability. Wow. I never thought about packing up releases with GNU Make. I’m glad you posted that comment. The tools that I’m most familiar with are ant and lately maven. These are arguably java-centric, but then I’ve been working in shops that are mostly java-based.

Bottom line – I think using GNU Make is an excellent idea. If it is something that you are more comfortable with than other tools, or if your application development is compiling with Make then it should prove to be the best tool for your job. I think you’ve already shown that the tool can do what you want it to do – or you wouldn’t be using it.

The one thing that Maven does nicely is integrate with source control. You can configure it so that when you create a package, it first creates a tag or snapshot in your repository, then it uses that tag for the build. This ensures that at any given point in time, there is no confusion about which version of the code is in your build.

I would be curious to know if Make has this ability.

]]> Comment on Choosing the Tools for Release Management by Dennis Birkholz http://blog.onefreevoice.com/2009/03/22/choosing-tools/#comment-474 Dennis Birkholz Sun, 22 Mar 2009 14:35:28 +0000 http://blog.onefreevoice.com/?p=158#comment-474 Hallo, that sounds very interesting to me. Currently we are using GNU make to update triggers, views, stored procedures and schema changes or to create a new database setup from the scratch, but i would like to know watch is your opinion on that point! Unfortunately I am sitting in Germany and will not have the time to travel to Santa Clara, so is there a chance that your speech or slides will appear online? Would be very nice... Greets, Dennis Hallo,

that sounds very interesting to me. Currently we are using GNU make to update triggers, views, stored procedures and schema changes or to create a new database setup from the scratch, but i would like to know watch is your opinion on that point! Unfortunately I am sitting in Germany and will not have the time to travel to Santa Clara, so is there a chance that your speech or slides will appear online? Would be very nice…

Greets,
Dennis

]]> Comment on Source Control Layouts for Databases by Log Buffer #133: A Carnival of the Vanities for DBAs http://blog.onefreevoice.com/2009/01/27/source-control-heirarchy/#comment-459 Log Buffer #133: A Carnival of the Vanities for DBAs Fri, 30 Jan 2009 17:07:59 +0000 http://blog.onefreevoice.com/?p=145#comment-459 [...] Haas talks about his methods for source control for his database servers. It’s something that many DBAs don’t consider. I won’t [...] [...] Haas talks about his methods for source control for his database servers. It’s something that many DBAs don’t consider. I won’t [...]

]]> Comment on Source Control Layouts for Databases by Rdb Notes · Source Control Layouts for Databases http://blog.onefreevoice.com/2009/01/27/source-control-heirarchy/#comment-457 Rdb Notes · Source Control Layouts for Databases Tue, 27 Jan 2009 14:07:21 +0000 http://blog.onefreevoice.com/?p=145#comment-457 [...] Source Control Layouts for Databases « OneFreeVoice: It’s easy to decide that you’re going to store changes to your database in source control [...] [...] Source Control Layouts for Databases « OneFreeVoice: It’s easy to decide that you’re going to store changes to your database in source control [...]

]]> Comment on Source Control Layouts for Databases by Gregory Haase http://blog.onefreevoice.com/2009/01/27/source-control-heirarchy/#comment-456 Gregory Haase Tue, 27 Jan 2009 13:41:09 +0000 http://blog.onefreevoice.com/?p=145#comment-456 @Martin: I don't remember seeing this thread before, but it is a good resource. I'm going to talk about some of the other topics in that thread soon (e.g. push and rollback scripts). @Mark R: I like that idea, thanks! @Martin: I don’t remember seeing this thread before, but it is a good resource. I’m going to talk about some of the other topics in that thread soon (e.g. push and rollback scripts).

@Mark R: I like that idea, thanks!

]]> Comment on Source Control Layouts for Databases by Mark R http://blog.onefreevoice.com/2009/01/27/source-control-heirarchy/#comment-455 Mark R Tue, 27 Jan 2009 13:34:11 +0000 http://blog.onefreevoice.com/?p=145#comment-455 Perhaps calling them "Stateless" and "Stateful" objects would be better. It should be clear to the engineer that stateless objects can be dropped and re-created, but stateful ones should not. Perhaps calling them “Stateless” and “Stateful” objects would be better.

It should be clear to the engineer that stateless objects can be dropped and re-created, but stateful ones should not.

]]> Comment on Source Control Layouts for Databases by Martin Holzhauer http://blog.onefreevoice.com/2009/01/27/source-control-heirarchy/#comment-454 Martin Holzhauer Tue, 27 Jan 2009 05:40:41 +0000 http://blog.onefreevoice.com/?p=145#comment-454 I like your layout for versioning the schema. reminds me a lot to http://marksverbiage.blogspot.com/2008/07/versioning-your-schema.html there a really few sources for informations about versioning a db schema, what i think is a really important aspect of developing. I like your layout for versioning the schema.
reminds me a lot to http://marksverbiage.blogspot.com/2008/07/versioning-your-schema.html

there a really few sources for informations about versioning a db schema,
what i think is a really important aspect of developing.

]]> Comment on Continuous Integration is Not New! by Tukam Dixon http://blog.onefreevoice.com/2008/12/20/continuous-integration-is-not-new/#comment-453 Tukam Dixon Sat, 24 Jan 2009 22:27:14 +0000 http://blog.onefreevoice.com/?p=141#comment-453 Debbie/Gregory. Coming soon?? L8tr. Debbie/Gregory.
Coming soon??

L8tr.

]]> Comment on Continuous Integration is Not New! by Gregory Haase http://blog.onefreevoice.com/2008/12/20/continuous-integration-is-not-new/#comment-452 Gregory Haase Tue, 06 Jan 2009 15:15:17 +0000 http://blog.onefreevoice.com/?p=141#comment-452 I will be blogging more about this in the near future, and I will have my whole presentation and some supporting scripts online - if not before the conference - immediately after. The short answer is - you can either use mysqld_multi or mysql_sandbox to run multiple instances on a single server. Things to remember - you will need adequate memory and disk to support all your concurrent databases, and unless you have lots of spindles of very fast disks, you are going to have slow performance if lots of people are running lots of queries on the lots of databases on the same server. I will be blogging more about this in the near future, and I will have my whole presentation and some supporting scripts online – if not before the conference – immediately after.

The short answer is – you can either use mysqld_multi or mysql_sandbox to run multiple instances on a single server. Things to remember – you will need adequate memory and disk to support all your concurrent databases, and unless you have lots of spindles of very fast disks, you are going to have slow performance if lots of people are running lots of queries on the lots of databases on the same server.

]]>