Martha, Not that I have anything to add but I would like to know what are some good practices also. We also have similar issues where tables are getting quite large.
Tim On Thu, Mar 27, 2014 at 9:33 AM, Martha Driscoll <[email protected]>wrote: > We have been on Evergreen for nearly 2 years. Recently it has been taking > significantly longer to load patron records than it used to. We load files > just about weekly for our college libraries and the files contain thousands > of records. > > I asked a few people at the conference about trimming tables and found > that some delete data out of auditor tables. Our actor_usr_history table > is around 14 million rows and asset_copy_history is over 26 million rows. > We don't currently age the circulations and the actor.circulation table is > up around 67 million rows. > > I'm wondering what system administrators do periodically to keep the > database running efficiently and what the potential trade-offs are. > > -- > Martha Driscoll > Systems Manager > North of Boston Library Exchange > Danvers, Massachusetts > www.noblenet.org > -- Tim Spindler [email protected] *P** Go Green - **Save a tree! Please don't print this e-mail unless it's really necessary.*
