Mike, I haven't checked the quantity or compared it to our entire database size but we probably have a lot deleted bibs and copies in the database just do to normal workflows. Is there ever an advantage in wiping those from the database (not just changing the deleted flag)?
I know this would have to be carefully done because removing those entirely could break other things but I could see maybe in another couple years it might be advantageous to remove the oldest ones from completely from the database. Tim On Thu, Mar 27, 2014 at 9:43 AM, Mike Rylander <mrylan...@gmail.com> wrote: > Martha, > > Other than storage, the auditor tables won't impact performance -- > they are insert-only in practice. What process are you using for > loading patrons? If you're using the staging tables, it may just be a > matter of creating some indexes. > > > On Thu, Mar 27, 2014 at 9:40 AM, Rogan Hamby <rogan.ha...@yclibrary.net> > wrote: > > I've contemplated doing this but have been hesitant for a number of > reasons. > > Moving storage to SSDs eliminated a lot of bottlenecks for us though. > > > > > > On Thu, Mar 27, 2014 at 9:35 AM, Tim Spindler <tjspind...@gmail.com> > wrote: > >> > >> 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 <drisc...@noblenet.org > > > >> 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 > >> tjspind...@gmail.com > >> > >> P Go Green - Save a tree! Please don't print this e-mail unless it's > >> really necessary. > >> > >> > > > > > > > > > > -- > > > > Rogan Hamby, MLS, CCNP, MIA > > Managers Headquarters Library and Reference Services, > > York County Library System > > > > "You don't have to burn books to destroy a culture. Just get people to > stop > > reading them." > > -- Ray Bradbury > > > > "You can never get a cup of tea large enough or a book long enough to > suit > > me." > > -- C.S. Lewis > > > > -- > Mike Rylander > | Director of Research and Development > | Equinox Software, Inc. / Your Library's Guide to Open Source > | phone: 1-877-OPEN-ILS (673-6457) > | email: mi...@esilibrary.com > | web: http://www.esilibrary.com > -- Tim Spindler tjspind...@gmail.com *P** Go Green - **Save a tree! Please don't print this e-mail unless it's really necessary.*