Hello,
We have a mapping with MS SQL source which is very slow.
But, when we execute SQL generated by xDI on an SQL editor like DBeaver or SQL Server we have a good response time.
How to get a better response time on xDI ?
Three-point to check :
Check if the module was default and therefore used the jdbc in the default module and prefer to use sqlserver module instead.
Add sendStringParametersAsUnicode=false parameter in the jdbc url parameter
Removed the SelectMethod=cursor still in the jdbc url.
Audric FREY
Hello,
We have a mapping with MS SQL source which is very slow.
But, when we execute SQL generated by xDI on an SQL editor like DBeaver or SQL Server we have a good response time.
How to get a better response time on xDI ?
Three-point to check :
Check if the module was default and therefore used the jdbc in the default module and prefer to use sqlserver module instead.
Add sendStringParametersAsUnicode=false parameter in the jdbc url parameter
Removed the SelectMethod=cursor still in the jdbc url.
Audric FREY
Three-point to check :
Check if the module was default and therefore used the jdbc in the default module and prefer to use sqlserver module instead.
Add sendStringParametersAsUnicode=false parameter in the jdbc url parameter
Removed the SelectMethod=cursor still in the jdbc url.
-
File external resolver with encrypted value
-
Timeout on Mapping/Webservice call
-
UNIQUE TEMP TABLE NAMES
-
Previous step name from a sub-process of execute delivery
-
Dropping multiple tables at once in XDI
-
Freeze Designer and corrupted workspace
-
FileWait/Move/Copy: FileInclude with space
-
Loop excel files
-
Change SVN user in the Designer
-
How to Specify the JVM used by the Designer?
See all 64 topics