Hello Paul.
Thanks for your advice.
My strategy was based on backup data once approach but this would produce to
many files I now realize.
But I still want to avoid to backup the entire database (N=0) on regular basis.
Whats your opinion about this approach?
First backup N=0
Every day N=1 for a
Den 2014-03-16 07:27 skrev hugo.lar...@yahoo.com såhär:
Hello Paul.
Thanks for your advice.
My strategy was based on backup data once approach but this would
produce to many files I now realize.
But I still want to avoid to backup the entire database (N=0) on
regular basis.
Whats your
Hello,
Hello,
We have a POS applications with hundreds of clients and need some advice
on how to backup.
Each application has it's own Firebird database.
Read about nbackup and thought that this could be a solution since the
clients has low bandwidth.
I'm not entirely sure if I understand
The following procedure causes a deadlock when the user on the web page
navigates rapidly through a javascript object on the web page. Please
give me some advice on how best to deal with this. I've thought about
changing it using DATEDIFF so they update only once a minute, but I
would
Hello Kjell,
Thanks for your time analyzing and explaining my backup strategy and proposing
yours.
You wrote that my strategy wont work. Maybe i'm missing something or I
explained wrong.
As I understood your strategy is based on annually full backups (N=0) and maybe
you understood that my
Hello Thomas,
Each shop, for example a restaurant has its own local database on the computer
the Point Of Sale software is running on.
The shops has ADSL connection with 1MBit upload speed and the database is
around 50 MB and growing every day.
Uploading such file to our server with this
Each shop, for example a restaurant has its own local database on the
computer the Point Of Sale software is running on.
The shops has ADSL connection with 1MBit upload speed and the database
is around 50 MB and growing every day.
Uploading such file to our server with this bandwidth disturbs
Kjell Rilbe wrote:
First day of year: N=0, initial complete backup.
First day of each month: N=1, will contain all pages changed since first
day of year.
First day of each week: N=2, will contain all pages changed since first
day of month.
Each day: N=3, will contain all pages changed since
Den 2014-03-16 11:58 skrev Paul Vinkenoog såhär:
Kjell Rilbe wrote:
First day of year: N=0, initial complete backup.
First day of each month: N=1, will contain all pages changed since first
day of year.
First day of each week: N=2, will contain all pages changed since first
day of
Hi Kjell,
If two such days coincide, you still need to run both colliding levels
(lower N first, higher N directly afterwards), or the sequence will be
broken next day.
That's not necessary, and the higher level backup will add nothing on
that moment.
Suppose you make a level-2
Session login is is unique between logins, but will be reused by the same user.
I've no doubt that there are two attempts to update the same record. That is
because session login is used to validate the user has permission to write the
record they are attempting to. In the scenario
11 matches
Mail list logo
