You can translate the question and the replies:

Issue with sql server connector

I've an instance of sql2016 enterprise. Althoung I do not see a connector for this specific version, I am working with sql server 2014, which seems to be good enough. However, I started noting that for some reason the amount of time it takes to run things on this node is huge, while it shouldn't since on the instance itself things run pretty fast
sqlserver mssql performance
user
12-01-2017 15:21:20 -0500
code

2 Answers

Hi! Although SQL Server 2016 is not officially supported yet, I made it work with the SQL Server 2014 adapter. For your situation, I’d look into the execution trace of your query to check if it is being delegated to the source. You can find more information regarding the execution trace in the *“Execution Trace of a Statement” *section of the [VDP Administration Guide](https://community.denodo.com/docs/download/document/Virtual%20DataPort/Denodo%206.0/Virtual%20DataPort%20Administration%20Guide). Also the logs located in *<DENODOHOME>/logs/vdp* may contain useful information about your issue. In addition, take a look at the new [Diagnostic & Monitoring tool](https://community.denodo.com/docs/download/document/Virtual%20DataPort/Denodo%206.0/Virtual%20DataPort%20Monitoring%20and%20Diagnostic%20Tool) that helps to monitor the Denodo servers in order to identify the cause of possible problems. Hope this helps!
Denodo Team
17-01-2017 07:34:23 -0500
code
The execution plan seems o.k., but it seems like it is having big overhead. I will check it again, although it is somewhat weird. I'll try and add example.
user
22-01-2017 09:10:55 -0500
You must sign in to add an answer. If you do not have an account, you can register here