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?
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_F ...
_________________ IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Add To Favorites View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum