The nvarchar(max) field of sql server is read as LOB by datastage ODBC stage ([IBM (DataDirect OEM)][ODBC SQL Server Wire Protocol driver]). In order to read the data it suggests to change the array size to 1 for LOB and this change highly impacts the performance.
Is there any solution/workaround for reading nvarchar(max) fields without impacting the performance?
Improve performance for nvarchar(max)/LOB type in ODBC stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You may be able to increase array size by one or two, but are quickly likely to run into the maximum number of bytes that the ODBC driver can handle.
That figure can be tuned by including MAX_FETCH_BUFF in the uvodbc.config entry for the DSN; but tune it too big and you will hit other memory limits and either start using scratch disk or taking out of memory errors.
That figure can be tuned by including MAX_FETCH_BUFF in the uvodbc.config entry for the DSN; but tune it too big and you will hit other memory limits and either start using scratch disk or taking out of memory errors.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.