[firebird-support] Re: in new API

2018-06-08 Thread Norbert Saint Georges n...@tetrasys.eu [firebird-support]
>> and connection (= current_connection)? > Almost the same way as with ISC API: use ITransaction::getInfo() and > IAttachment::getInfo() I search since but can not find any info on items: byteptr. in dot net sources, i found a constant isc_info_next_transaction: = 107 but does not exist in fir

[firebird-support] URGENT - Database performance is very slow

2018-06-08 Thread Vishal Tiwari vishuals...@yahoo.co.in [firebird-support]
Hi All, It's urgent... We are facing a database performance issue. Currently, we are using firebird version 2.5.2 ODS 11.2. If we try to run a simple SQL i.e. Select * from using FlameRobin, it is taking time and next time the time span increases. Same happens from all of our applications side a

Re: [firebird-support] Get last time a procedure is accessed.

2018-06-08 Thread blackfalconsoftw...@outlook.com [firebird-support]
If as Mark has already stated, there is no way to provide information on procedures as to when they were last accessed, you may want to opt for your own logging file that is updated every time a procedure is called. You can do this either with a trigger in each stored procedure or within your

Re: [firebird-support] Recover database encrypted by trojan (Dharma)

2018-06-08 Thread Ann Harrison aharri...@ibphoenix.com [firebird-support]
> On Jun 6, 2018, at 6:06 AM, Volker Cordes v...@freeline-edv.de > [firebird-support] wrote: > > Hello, > > a customer of ours got himself a trojan that led to his databases > (firebird 2.5) getting encrypted. I looked at the files with a text > editor and found that they do not look entirely

Re: [firebird-support] Get last time a procedure is accessed.

2018-06-08 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
On 2018-06-08 08:30, antoedinchar...@gmail.com [firebird-support] wrote: > Is there any way that we could log last accessed time of a procedure. > > I am in a process of cleaning up 8 years old database. DB is having > more than 1000 procedures in which only 10-20% will be using now after > optimi