[firebird-support] NBackup Backup Takes Long Time For Level 2.

[Anto Edin Charley antoedinchar...@gmail.com [firebird-support]]

Hi,I have Implemented NBackup in one of my client's Central Database which will 
be connected by more than 150 Remote Locations, Web Services Etc.Database Size 
- 40GBOS                   - Windows 2012, 32 GB RamFirebird            - 2.5.6 
CSNBackup Frequency -     Level 0 - Sundays,     Level 1 - Daily @ 00:00,     
Level 2 - Every 15 Minutes.
For every Level 2 Backup it takes more than 30 Minutes to complete. Is there 
anything i need to Check/Improve or if this is the normal time that will take 
for this kind of Database.
Nb:- Surprisingly 30 Minutes is the Same Time Consumed to create a Level 0, 1, 
2. In this logically Level 0 has more data than Level 2 Still it consumes same 
time.

Thanks and Regards-- Anto Edin Charley 

Re: [firebird-support] Moving DB from 32 bits to 64 bits

[m_brahi...@yahoo.fr [firebird-support]]

Yes exactly and thanks again ! 

Re: [firebird-support] Moving DB from 32 bits to 64 bits

[Thomas Steinmaurer t...@iblogmanager.com [firebird-support]]

> I am only using some functions from the ib_udf.dll which is installed in 
> the \Firebird\Firebird_3_0\UDF  and have built a little functions 
> calling functions of that dll there is no problem I suppose ?

If you are talking about a PSQL-based stored function (new feature in 
3.0), then you are right, this won't be a problem.


-- 
With regards,
Thomas Steinmaurer
http://www.upscene.com/

Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.

[firebird-support] Re: FBExport tools

[hv...@users.sourceforge.net [firebird-support]]

---In firebird-support@yahoogroups.com,  wrote :
 
 > please inform me how can I use this "FBExport" tool... 

 

 http://fbexport.sourceforge.net/manual.html 
http://fbexport.sourceforge.net/manual.html

 

 Regards,
 Vlad

Re: [firebird-support] Moving DB from 32 bits to 64 bits

[m_brahi...@yahoo.fr [firebird-support]]

I am only using some functions from the ib_udf.dll which is installed in the 
\Firebird\Firebird_3_0\UDF  and have built a little functions calling functions 
of that dll there is no problem I suppose ?

[firebird-support] FBExport tools

[Ahmad Alammar / vamos Eltern-Kind-Reisen GmbH alam...@vamos-reisen.de [firebird-support]]

Hi,
I'm using "Firebird Isql" Command Promt Database..
I'm searching for Export and Import options..I find "FBExport" tool..
now my problem is how to use "FBExport" tool...
I have downloaded the files and extracted it
please inform me how can I use this "FBExport" tool...

Viele Grüße aus Hannover

Ahmad Alammar
Medien & EDV

vamos Eltern-Kind-Reisen GmbH
Hindenburgstr. 27, 30175 Hannover

Tel. +49 511 400 799-71
Fax +49 511 400 799-99
alam...@vamos-reisen.de

www.vamos-reisen.de
www.vamos-geheimtipps.de
www.vamos-blog.de

Bürozeiten: Mo. bis Fr. 09.00 bis 18.00 Uhr, Sa. 09.00 bis 14.00 Uhr

Geschäftsführer: Stephan Krug und Jens Kubicki | Handelsregister Hannover Abt. 
B Nr. 52723 | USt-IdNr. DE115647989
Sparkasse Hannover | IBAN: DE88 2505 0180  1251 99 | BIC: SPKHDE2H

Re: [firebird-support] Moving DB from 32 bits to 64 bits

[m_brahi...@yahoo.fr [firebird-support]]

I am already under FB3 and I am only planning in case I will move to 64 bits 
server
Thank you very much for these informations

Re: [firebird-support] Moving DB from 32 bits to 64 bits

[Helen Borrie hele...@iinet.net.au [firebird-support]]

Wednesday, November 15, 2017, 5:54:05 AM, m_brahi...@yahoo.fr wrote:

> I would like to know please, if we can use a DB in win64 but built
> under win32 . The client app is built with delphi 32 bits so the
> clients will connect to that DB in 64 bits. Is it possible ? Thanks
>   
1. Your database should be fine if moved from win32 to win64.  It is
recommended that you back up the database on the old platform with
gbak and restore it with gbak on the new. as a good housekeeping
measure.

2.  Firebird servers don't care whether the client is 32-bit or
64-bit.

2.  Clients must use the fbclient.dll that matches the bitness of the
*application*.  If your database is going to be restored for use under
Fb3 then you will need to download the win32 zip kit and extract the
32-bit fbclient.dll from it.  In the Fb2.5 win64 kit, there should be
a copy of the 32-bit client in the system32 subdirectory.  I don't
know why it is omitted from the Fb3 kits.

Helen

Re: [firebird-support] Moving DB from 32 bits to 64 bits

['livius' liviusliv...@poczta.onet.pl [firebird-support]]

Hi,

bitness of the server does not matter only bitness of client library 
(fbclient.dll).
Client library bitness must be the same as your application.

regards,
Karol Bieniaszewski

From: m_brahi...@yahoo.fr [firebird-support]
Sent: Tuesday, November 14, 2017 5:54 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Moving DB from 32 bits to 64 bits


Hello,

I would like to know please, if we can use a DB in win64 but built under 
win32 . The client app is built with delphi 32 bits so the clients will 
connect to that DB in 64 bits. Is it possible ? Thanks




Posted by: m_brahi...@yahoo.fr

[firebird-support] Moving DB from 32 bits to 64 bits

[m_brahi...@yahoo.fr [firebird-support]]

Hello,
 

 I would like to know please, if we can use a DB in win64 but built under win32 
. The client app is built with delphi 32 bits so the clients will connect to 
that DB in 64 bits. Is it possible ? Thanks

Re: [firebird-support] Firebird 3.0 create database syntax

[palevi pablo.l...@horus.es [firebird-support]]

Thanks Mark! Using single quotes solved all my issues ...

Pablo

El 14/11/2017 a las 10:39, Mark Rotteveel m...@lawinegevaar.nl 
[firebird-support] escribió:


On 14-11-2017 10:31, Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] wrote:
> On 14-11-2017 00:00, palevi pablo.l...@horus.es [firebird-support] 
wrote:

>> In firebird 2.x you can specify some parameters when creating a
>> database, i.e.:
>>
>>     create database "localhost:milenio-central.fdb" user "milenio"
>> password "secreto" page_size 16384 default character set utf8 collation
>> unicode;
>>
>> However in fb 3.0 I get this error:
>>
>>     Use CONNECT or CREATE DATABASE to specify a database
>>     SQL> create database "localhost:milenio-central.fdb" user milenio
>> password "secreto" page_size 16384 default character set utf8 collation
>> unicode;
>>     Statement failed, SQLSTATE = 42000
>>     Dynamic SQL Error
>>     -SQL error code = -104
>>     -Token unknown - line 1, column 17
>>     -"localhost:milenio-central.fdb"
>>
>> if I strip out the "character set" and "collation" parameters, then the
>> order runs fine again, but ¿what are the allowed parameters for "create
>> database" in fb 3.0? ¿and what are the alternatives for unsupported 
ones?


I just noticed the second part about stripping out all options, and then
it works. I can reproduce that. I'm not sure why that works. It would
suggest that a basic create database statement is parsed differently
from a create database with options.

However in both cases single quotes work just as well. So just get into
the habit of using single quotes.

Mark
--
Mark Rotteveel

Re: [firebird-support] Firebird 3.0 create database syntax

[Mark Rotteveel m...@lawinegevaar.nl [firebird-support]]

On 14-11-2017 10:31, Mark Rotteveel m...@lawinegevaar.nl 
[firebird-support] wrote:
> On 14-11-2017 00:00, palevi pablo.l...@horus.es [firebird-support] wrote:
>> In firebird 2.x you can specify some parameters when creating a
>> database, i.e.:
>>
>>    create database "localhost:milenio-central.fdb" user "milenio"
>> password "secreto" page_size 16384 default character set utf8 collation
>> unicode;
>>
>> However in fb 3.0 I get this error:
>>
>>    Use CONNECT or CREATE DATABASE to specify a database
>>    SQL> create database "localhost:milenio-central.fdb" user milenio
>> password "secreto" page_size 16384 default character set utf8 collation
>> unicode;
>>    Statement failed, SQLSTATE = 42000
>>    Dynamic SQL Error
>>    -SQL error code = -104
>>    -Token unknown - line 1, column 17
>>    -"localhost:milenio-central.fdb"
>>
>> if I strip out the "character set" and "collation" parameters, then the
>> order runs fine again, but ¿what are the allowed parameters for "create
>> database" in fb 3.0? ¿and what are the alternatives for unsupported ones?

I just noticed the second part about stripping out all options, and then 
it works. I can reproduce that. I'm not sure why that works. It would 
suggest that a basic create database statement is parsed differently 
from a create database with options.

However in both cases single quotes work just as well. So just get into 
the habit of using single quotes.

Mark
-- 
Mark Rotteveel

Re: [firebird-support] Firebird 3.0 create database syntax

[Mark Rotteveel m...@lawinegevaar.nl [firebird-support]]

On 14-11-2017 00:00, palevi pablo.l...@horus.es [firebird-support] wrote:
> In firebird 2.x you can specify some parameters when creating a
> database, i.e.:
> 
>       create database "localhost:milenio-central.fdb" user "milenio"
> password "secreto" page_size 16384 default character set utf8 collation
> unicode;
> 
> However in fb 3.0 I get this error:
> 
>       Use CONNECT or CREATE DATABASE to specify a database
>       SQL> create database "localhost:milenio-central.fdb" user milenio
> password "secreto" page_size 16384 default character set utf8 collation
> unicode;
>       Statement failed, SQLSTATE = 42000
>       Dynamic SQL Error
>       -SQL error code = -104
>       -Token unknown - line 1, column 17
>       -"localhost:milenio-central.fdb"
> 
> if I strip out the "character set" and "collation" parameters, then the
> order runs fine again, but ¿what are the allowed parameters for "create
> database" in fb 3.0? ¿and what are the alternatives for unsupported ones?

The database name and password are strings, and must be enclosed in 
single quotes. That you could use double quotes in ISQL in previous 
versions, was probably for backwards compatibility with dialect 1.

However since Firebird 3, the username is an object name (just like 
tables and columns), and not just a string, which means that double 
quotes are now reserved for the ability to quote object names, and you 
must use single quotes for strings, just like in normal dialect 3 
statements.

It looks like the release notes should expand on this (specifically, 
https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-compat-sql.html#rnfb30-compat-username-namelength
 
)

Mark

PS The above create database statement would fail under Firebird 2.5 and 
earlier with a "Token unknown SYSDBA" as it would need to be enclosed in 
single (or double) quotes just like the database name and password.

-- 
Mark Rotteveel

[firebird-support] Firebird 3.0 create database syntax

[Рустам Муса-Ахунов rusta...@ukr.net [firebird-support]]

Here is CREATE DATABASE syntax: 
http://www.firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-ddl-db.html
 



Try use single quotes:




create database 'localhost:milenio-central.fdb' user 'milenio' 
password 'secreto' page_size 16384 default character set utf8 collation 
unicode; 
















14 листопада 2017, 04:07:06, від "palevi pablo.l...@horus.es 
[firebird-support]" :

>   Hi,
> 
> In firebird 2.x you can specify some parameters when creating a 
> database, i.e.:
> 
>     create database "localhost:milenio-central.fdb" user "milenio" 
> password "secreto" page_size 16384 default character set utf8 collation 
> unicode;
> 
> However in fb 3.0 I get this error:
> 
>     Use CONNECT or CREATE DATABASE to specify a database
>     SQL> create database "localhost:milenio-central.fdb" user milenio 
> password "secreto" page_size 16384 default character set utf8 collation 
> unicode;
>     Statement failed, SQLSTATE = 42000
>     Dynamic SQL Error
>     -SQL error code = -104
>     -Token unknown - line 1, column 17
>     -"localhost:milenio-central.fdb"
> 
> if I strip out the "character set" and "collation" parameters, then the 
> order runs fine again, but ¿what are the allowed parameters for "create 
> database" in fb 3.0? ¿and what are the alternatives for unsupported ones?
> 
> Thanks!