[firebird-support] Re: Security per database - migrating from FB 2.5

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

Marcin,

you have to make embedded connection to the zt1 and create at least one user 
there
(probably you need sysdba, probably no):

isql zt1
create user sysdba password 'pwd';


Regards,
Vlad

Re: [firebird-support] Re: Sort error No free space found in temporary...

[Alexey Kovyazin a...@ib-aid.com [firebird-support]]

Hi,

If you have big sort files (you can check their existence manually in 
temp folder or use HQbird FBBDataGuard to monitor them for you), 
increasing TempCacheLimit to fit all of them can speed up sorting 
queries (with GROUP BY and ORDER BY, for example).


However, the better approach is to decrease record sets which should be 
sorted.
For example, many developers use ORDER BY for internal processing in 
stored procedures - usually it can be simply removed.


Regards,
Alexey Kovyazin
IBSurgeon


On 03.09.2017 20:47, kragh.tho...@yahoo.com [firebird-support] wrote:

Hey
Thanks for the clarification, that is also the only explanation that 
made sense to me, after i had a look at the optimized config published 
at ib-aid.com.


Alexey perhaps you can answer this, is there anything to gain from 
configuring TempCacheLimit to use 2, 4 or 6Gb? Or perhaps more 
important could this have an negative effect? Of course provided that 
the server has plenty of RAM.

[firebird-support] Re: Sort error No free space found in temporary...

[kragh.tho...@yahoo.com [firebird-support]]

Hey
 Thanks for the clarification, that is also the only explanation that made 
sense to me, after i had a look at the optimized config published at ib-aid.com.
 

 Alexey perhaps you can answer this, is there anything to gain from configuring 
TempCacheLimit to use 2, 4 or 6Gb? Or perhaps more important could this have an 
negative effect? Of course provided that the server has plenty of RAM. 
 

Re: [firebird-support] Re: Sort error No free space found in temporary...

[Alexey Kovyazin a...@ib-aid.com [firebird-support]]

Hi,

I remember I answered incorrectly that time :)

TempCacheLimit is always per server instance.

For Classic it means it is allocated per each connection (since each 
connection has own server process), for SuperClassic and SuperServer 
temp space will be shared between connections, since there is the single 
server process.


Regards,
Alexey Kovyazin
IBSurgeon
www.ib-aid.com




On 02.09.2017 20:46, Thomas Steinmaurer t...@iblogmanager.com 
[firebird-support] wrote:


Hi Thomas,

> From what i can read on the internet TempCacheLimit, is per server
> process, and not per attachment.

In SuperServer architecture, right, but if I remember correctly, you
have mentioned in one of your first posts that you are using
SuperClassic, right?

> http://firebird.1100200.n4.nabble.com/TempCacheLimit-td4309475.html

Talking about SuperServer.

> 
https://www.mail-archive.com/firebird-support@yahoogroups.com/msg10199.html


Talking about SuperClassic with answers that it is per connection.

>
>
> I believe I have found the statements that caused the problem, first 
one

> was executede about 400/second and contained a union, that was replaced
> by union all in the hope that would eliminate the need for temp cache.

UNION vs. UNION ALL. UNION is removing duplicates, thus some sort of
applying DISTINCT with first sorting to remove duplicates is applied.

DISTINCT, sorting, group by (internally first doing a sort) will
internally produce temporary data.

> The second statement is a really nasty dynamically build common table
> expression containing upwards of 10 union.. Here we are in the process
> of moving this search to Elastisearch.
>
> We just purchased FB TraceManager at our company to weed performance
> issues  - Thanks for a great product : )

Great to hear. Thanks. :-)

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

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