Go Back > Forum > Baan Quick Support: Functional & Technical > Tools Administration & Installation

User login

Frontpage Sponsor


Google search

For ERP LN feature pack upgrade, what method of install are you using?
Installation Wizard into existing VRC
Installation Wizard into new VRC
Manual into existing VRC
Manual into new VRC
Total votes: 50

Baanboard at LinkedIn

Reference Content

Thread Tools Display Modes
Old 7th June 2013, 21:06
GaryEd GaryEd is offline
Senior Member
Join Date: Sep 2001
Location: CT, USA
Posts: 138
GaryEd is on a distinguished road
Baan: 4c4 sp 30 - DB: SQL 2008 R2 - OS: Windows 2008 R2
db resource file
Baan: Other/Unknown
DB: Other/Unknown
OS: Other/Unknown
C/S: None/Unknown

What do these settings do and what is a typical value

Reply With Quote
Sponsored Links
Old 7th June 2013, 21:47
bhushanchanda's Avatar
bhushanchanda bhushanchanda is offline
Join Date: Sep 2012
Location: India
Posts: 2,355
bhushanchanda has a spectacular aura aboutbhushanchanda has a spectacular aura aboutbhushanchanda has a spectacular aura about
Baan: LN FP 1-9, 10.4, a little bit of Baan IV - DB: SQL Server 2008, Oracle - OS: Windows Server 2008 R2, Unix

The Infor ERP MSQL Level 2 database driver has three resource variables
that influence the cursor handling: msql_cursor_type,
msql_max_free_cursors and msql_retained_cursors. Each of these
resource variables is described in the following section.
The resource msql_cursor_type configures the driver to use one of the two
SQL Server cursor types: 1 (Keyset-driven with autofetch enabled) by default
or 2 (Fast forward-only with autofetch enabled). Changing this value can
result in a difference in performance slightly. Which type performs better
depends on the particular scenario. In a 3-tier scenario (where the client,
application server and the RDBMS physically exist on 3 different machines)
msql_cursor_type:1 may give better performance.
The resource msql_max_free_cursors influences the number of statement
handles (SQL Server cursors) that are kept for reuse by the driver. The
default value is 32. Whenever the application closes a query, most resources
in the driver are freed. However, if the MSQL cursor being allocated will soon
Database driver configuration and tuning | 6-3
be re-used, closing and opening of the cursor can be avoided. To avoid
closing and re-opening cursors, the cursor is put in a free list containing all
cursors, which are disassociated from a query. When a request for a new
cursor comes, first a free cursor is taken from the free list. If no free cursors
are available, a new cursor is opened. In this way the number of times a
cursor is closed and opened is reduced. When the number of free cursors
exceeds the value of msql_max_free_cursors, the MSQL cursor will be
closed. Increasing the value of msql_max_free_cursors will result in more
concurrent cursors open (thus more memory), but in fewer cursors being
opened and closed.
Note: When array fetch interface is enabled, free cursor list is not
maintained. The driver internally resets the msql_max_free_cursors to 0.
With this resource the number of inactive cursors and thus the number of
open cursors can be reduced.
When a query has fetched all rows, a close is issued on the corresponding
cursor, which means that SQL Server is notified that no additional fetches will
be done. This gives SQL Server the chance to free certain query resources.
After the cancel, the query can be re-executed without re-opening (parsing,
binding) the cursor. The driver does not know if a cursor in cancel state will
be re-used later. In the worst case it is not re-used, and the cursor will
continue to be reserved for the query. After all rows have been fetched, the
driver has a facility to put inactive cursors (in cancel state) in a cancel list, so
that they become candidates for being assigned to a different query.
However, a number of inactive cursors in this list that is not available for this
purpose are defined by the resource msql_retained_cursors, which defaults
to 20.
If the number of cursors in the cancel list is less than 20, a cursor from the
cancel list cannot be assigned to a different query.
If more than 20 cursors are in the cancel list, and a request for a new cursor
is issued, the least recently inactivated cursor is used for this new cursor.
This cursor is disassociated from the original query and assigned to a new
query, which does parsing and binding on this cursor.
When the original query is doing a re-execute, the driver detects that the
cursor has been associated with another query and will get a new cursor and
re-parse and bind the query again. Increasing the value of
msql_retained_cursors leads to less re-parsing and re-binding of queries,
which reduces CPU resources. The number of open cursors however (and
thus memory) is increased.


Unless you try to do something beyond what you have already mastered, you will never grow!
Reply With Quote

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Programming Question mr_suleyman Tools Development 37 11th November 2016 08:14
Using -set BAAN_WIN_TITLE in some resource file VishalMistry Tools Administration & Installation 4 18th June 2011 14:06
bshell received SIGTERM manojsharma Tools Development 11 5th June 2008 09:22
How to print Postcript in landscape orientation heliopaixao Tools Administration & Installation 8 28th July 2006 13:39

All times are GMT +2. The time now is 05:21.

©2001-2018 - -