[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [PROGRAMMERING] MySQL tabel og index'



On Fri, 28 May 2004 13:32:35 +0200, Nis wrote:

> Men når der bliver kørt backup på den database, tager det 16 min!!!
> Slow-query loggen viser at det er den ene tabel som trækker tiden ud og
> nu skal jeg har fundet ud af hvordan jeg for lavet om på det.

Uanset om index-omfanget forekommer voldsomt: Læsning i databasen burde
da ikke blive sløvet af index'erne? - Eller hvad: Hvordan back'er I op?

Forekommer der mange ændringer i tabellen under backup? (Måske et
låsningsproblem?)

> Jeg ændre ikke selv i tabel strukturen, men beder kunden om selv at gøre
> det, da der pt. er en ting som stikker mig i øjenene. Tabellen fylder
> 169.448 KB, hvor af de 62.114 er data og de 107.334 KB er index. Det er
> lige voldsomt nok!

Forholdet mellem tallene synes sært, men der kan da på ingen måde siges
at være tale om voldsomme datamængder.

>    `kode1` varchar(10) default '0',
>    `kode2` varchar(10) default NULL,
>    `kode3` varchar(10) default NULL,
>    `kode4` varchar(10) default NULL,
>    `kode5` varchar(10) default NULL,
>    `kode6` varchar(10) default NULL,
>    `kode7` varchar(10) default NULL,
>    `kode8` varchar(10) default NULL,
>    `kode9` varchar(10) default NULL,
>    `kat1` varchar(255) default NULL,
>    `kat2` varchar(255) default NULL,
>    `kat3` varchar(255) default NULL,
>    `kat4` varchar(255) default NULL,
>    `kat5` varchar(255) default NULL,
>    `kat6` varchar(255) default NULL,
>    `kat7` varchar(255) default NULL,
>    `kat8` varchar(255) default NULL,
>    `kat9` varchar(255) default NULL,

(Det ser ud til, at relationen mangler noget normalisering, men lad det nu
ligge.)

-- 
Greetings from Troels Arvin, Copenhagen, Denmark



 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 22:43 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *