[firebird-support] File-based write filter

2013-10-11 Thread Petri Parviainen
Hello all When you are using File-Based Write Filter is there something Firebird files which should be excluded. Start situation is that firebird is installed and configured to work correctly. After that you enabled fbwf. Firebird version 2.5.2.26540. -br- Petri

Re[2]: [firebird-support] Restore error during unique index creation

2013-10-11 Thread Dmitry Kuzmenko
Hello, Thomas! Saturday, October 12, 2013, 1:06:24 AM, you wrote: TS> * Running th restore through the Services API/Manager right, this is the fastest way. TS> * Provide a larger page cache upon restore, because especially the index TS> creation step loves RAM. Don't forget to set the page buff

RE: [firebird-support] Restore error during unique index creation

2013-10-11 Thread Bob Murdoch
Thomas - -Original Message- From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] On Behalf Of Thomas Steinmaurer Sent: Friday, October 11, 2013 5:06 PM To: firebird-support@yahoogroups.com Subject: Re: [firebird-support] Restore error during unique index creati

Re: [firebird-support] Restore error during unique index creation

2013-10-11 Thread Thomas Steinmaurer
> I have a 100GB database that I am trying to run a restore on after a > successful backup. This is on a new virtual Windows Server 2008 box > running FB 2.1.5 Classic 32-bit (due to some UDFs that have not been > ported). > > After 26 hours of restore, the process quits with this error: > > gbak:

RE: [firebird-support] Restore error during unique index creation

2013-10-11 Thread Leyne, Sean
Bob, > I have a 100GB database that I am trying to run a restore on after a > successful > backup.  This is on a new virtual Windows Server 2008 box running FB 2.1.5 > Classic 32-bit (due to some UDFs that have not been ported). > > After 26 hours of restore, the process quits with this error: >

[firebird-support] Restore error during unique index creation

2013-10-11 Thread Bob Murdoch
I have a 100GB database that I am trying to run a restore on after a successful backup. This is on a new virtual Windows Server 2008 box running FB 2.1.5 Classic 32-bit (due to some UDFs that have not been ported). After 26 hours of restore, the process quits with this error: gbak:acti

Re: [firebird-support] MembershipProvider and RoleProvider width Firebird (ASP.NET)

2013-10-11 Thread Mark Rotteveel
On 10-10-2013 05:02, taqtaq2...@yahoo.com wrote: > Hi I have to build a asp.net application that connects to a database > that is in use with users and passwords. > > Someone can explain me how to work everything related to > MembershipProvider and RoleProvider with Firebird?. > > I have no idea ho

Re: [firebird-support] Optimise OR in WHERE

2013-10-11 Thread Tim Ward
On 11/10/2013 13:39, Kjell Rilbe wrote: Duh... No, try this where clause: AND ( (cast(WIDGET as vacrhar(10)) || '.' starting with coalesce(:param || '.', '') ) Actually it turns out that EXECUTE STATEMENT goes fast enough, so although slightly tacky I'll live with that for now. Thanks for

Re: [firebird-support] Optimise OR in WHERE

2013-10-11 Thread Kjell Rilbe

Re: [firebird-support] Optimise OR in WHERE

2013-10-11 Thread Kjell Rilbe

Re: [firebird-support] Optimise OR in WHERE

2013-10-11 Thread Tim Ward
On 11/10/2013 12:51, Kjell Rilbe wrote: Den 2013-10-11 13:40 skrev Tim Ward såhär: > > Yes I know you can't optimise OR, so I'm looking for an alternative > approach. > > I've come across a query in a stored procedure which goes like this: > > FOR SELECT FROM > WHERE ... > AND ( (WIDGET= :par

Re: [firebird-support] Optimise OR in WHERE

2013-10-11 Thread Kjell Rilbe
Den 2013-10-11 13:40 skrev Tim Ward såhär: > > Yes I know you can't optimise OR, so I'm looking for an alternative > approach. > > I've come across a query in a stored procedure which goes like this: > > FOR SELECT FROM > WHERE ... > AND ( (WIDGET= :param ) OR ( :param is null ) ) > ORDER BY >

[firebird-support] Optimise OR in WHERE

2013-10-11 Thread Tim Ward
Yes I know you can't optimise OR, so I'm looking for an alternative approach. I've come across a query in a stored procedure which goes like this: FOR SELECT FROM WHERE ... AND ( (WIDGET= :param ) OR ( :param is null ) ) ORDER BY INTO DO BEGIN END There are two ways in which this procedur