On 11/04/13 09:58, compdoc wrote:
> By the way, it wasn't enough to enable InnoDB - I had to create the bacula
> database after it was enabled for the tables to use this engine. (it was a
> new install)  
> 
> I don't know if it's possible to convert the tables after enabling InnoDB,
> but I would think it's better to start them out that way. You can google
> ways to tell if your tables are using InnoDB. 


It is trivial to convert the tables to InnoDB after creation.  Here's a
simple Unix bash shell one-liner to do it:

for T in $(mysql -BNe 'show tables from bacula'); do echo Converting
table bacula.${T} ; mysql -BNe "alter table bacula.${T} engine=InnoDB" ;
done

Any time you're working with InnoDB or converting tables to InnoDB,
remember that within limits, the more memory you have allocated to the
InnoDB buffer pool, the faster it will go.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users