How do you manage a 76gigs database?

[silent-kill]

---

and that is all live data XD we have 600gb+ database but not yet archived.. how do you managed that?.

[digitalsuperman]

that shouldnt've happend..pag 10gb palang unta to naka archive na..

[vern]

Data warehousing, mirrored servers & replication, hot backup.

[silent-kill]

where not in content base man gud bro, more on processing... thats why ana ka paspas mo accumulate ang data... nya required pajud mo keep 1-2years of data sa production database lol.

ako ta question what other things we can do to keep the query/system fast...
there comes a time nga ma max out na ang limit sa SQLEngine sa ka dako sa database hehee.
naa gali mi table nga max out na ang column number. lol kananglan pa lain table para mo support sa extended columns. hehehe. 175 columns man basin max. nya lapas pajud paet lol.

[eax]

Im not a database admin but if mo abot na siya sa maximum I think you need to data warehousing, clustering or ma shared ang load sa db.

[bigeasy]

This might be too late but whoever designed your database is at fault here. Take him out back and beat him up.

[silent-kill]

its not just a database bro.. hehee daghan sila database. 1 for each client... pari parihas sila og design...

i was thinking... kong pwede bana..

             system 
                 |
                  ---- 'select * from table where blah blah blah'
                 |
 'some multi paralleling engine'
                 |
                 -----'foreach active database server send: select * from table (then merge result)'
                 |
---------------------------
|        |        |       |        |
|        |        |       |        |
db1   db2     db3   db4    dbn

where ang system... mo insert og record bisanasa sa database...so ma hulog nga 'fragmented/distributed' ang database... of course ang inserting/updating will be controlled did2 na sa 'engine' para ang related record will be inserted/updated in the same database

when mo query na siya.. mo request lang siya simultaneously sa db1-n then ang 'engine' na ang mo merge sa mga results... which i think will be faster kai dugan man mag dagan ang query.

it would be cheaper basin kong buhaton nalang ang engine kaisa mo invest sa very expensive hardwares
lol lol

also ako tanaw ang dapat i save is per object lvl dili per record..

so kong i save sample is apple

apple
- seeds
- sugar
- vitamin c
dapat ang apple,seed, sugar,vitamin c ma save sa same database... para di magka gubot ig query balik eheheh

[javapenguin]

grabe sad ka dako akong database, ako lang gi replicate pagkakaron, peru ug ma dungan access, kamang kamang ang server, peru mas maau kanang clustering with load balancer, unya gamit ug blade server nga tag 500K+, hehehe, para paspas (paspas sad hurot imo kuwarta kay mahal kaau ang blade, hehehe)

[uzumaki]

how about mag create kag another company with thesame structure sa daan...usually pwede mana e rar or zip ang backup para mogamay...ru using SQL database?

[MarkCuering]

Grabeha sad ana database nila...unsa man mga data pinaprocess ana? how many years na?