Mark, I understood your explanation, but here where I work, the people don't do any maintenance on the database, such as sweep (they turn it off for default) and index stats. To avoid that, on the end of the day, they turn off the application and execute backup and restore. I would like to change this culture, but I need to know what to do. Like I told, I just know that I have to execute de sweep and collect index stats, but what more? Here they have some problems with old transactions, so I also need to do something with them, like force rollback or commit. But how I do that?
Regards, Marcelo Guimarães Em ter, 13 de nov de 2018 às 08:53, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] <firebird-support@yahoogroups.com> escreveu: > > > On 2018-11-13 10:58, Marcelo Guimaraes mfguimar...@gmail.com > [firebird-support] wrote: > > I'm quite new on Firebird world and I have doubts about the database > > maintenance. > > I would like some advices what I should concern and periodically > > execute on the database to leave them working and performing well. > > As a read one way to do this is doing a maintenance doig "gbak -b" and > > "gbak -c", but I want something that can be online, to reduce the > > downtime. > > What do you mean? Creating a backup **is** online, and you should > **not** overwrite your existing database after each backup. The advice > to restore the database (to some temporary location) is to double check > that the backup is restorable (certain logical corruptions can allow a > backup to be created but not fully restored, which would be annoying to > find out if you have an emergency). > > Mark > > -- Atenciosamente, Marcelo Guimarães
