Comments for OneFreeVoice

Comment on Information_Schema.Partitions – table_rows by Baruch Lvovsky

Baruch Lvovsky — Thu, 02 Feb 2012 04:32:09 +0000

I found good and simple explanation here.

Thank you for your notes.

Comment on Choosing the Tools for Release Management by Gregory Haase

Gregory Haase — Thu, 18 Mar 2010 01:23:48 +0000

Hi Abhi,

Thanks for you interest. Immediately before the tutorial session, I posted all of the materials that were used here: http://sites.google.com/a/onefreevoice.com/build_and_release/

The materials included instructions on how to work through the examples in PDF format, and a tgz with some files that were used.

Although the software versions might be a bit out of date now (this was almost a year ago), you should be able to follow through the examples and get a good idea about how the process works.

Of course, if you have specific questions you can post them here and I’d be happy to try to help.

Comment on Choosing the Tools for Release Management by Abhi

Abhi — Wed, 17 Mar 2010 13:58:09 +0000

Hello,
I am trying to setup an automated process for DB releases in my organization.right now , the Db releases are handled manually and require more effort and time but still is error prone.I read your article and thought if you can post me your speech or presentation , it will be of much help.

Thanks in advance
—————–
ABHI

Comment on Creating an Intermediate Replication Layer by How MySQL Sandbox Solves All My Problems « OneFreeVoice

How MySQL Sandbox Solves All My Problems « OneFreeVoice — Sun, 05 Apr 2009 04:01:31 +0000

[...] 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

Gregory Haase — Sun, 22 Mar 2009 15:00:44 +0000

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

Dennis Birkholz — Sun, 22 Mar 2009 14:35:28 +0000

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

Log Buffer #133: A Carnival of the Vanities for DBAs — Fri, 30 Jan 2009 17:07:59 +0000

[...] 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

Rdb Notes · Source Control Layouts for Databases — Tue, 27 Jan 2009 14:07:21 +0000

[...] 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

Gregory Haase — Tue, 27 Jan 2009 13:41:09 +0000

@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

Mark R — Tue, 27 Jan 2009 13:34:11 +0000

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.