You can translate the question and the replies:

Denodo slower performance querying SQL Server databases using Windows AD Authentication compared to SQL Authentication

Hi, We have Denodo cloud setup off prem however we have noticed that when it is trying to query our on prem MS SQL 2016 server authenticating with a Windows AD account the connection when querying the databases is extremely slow (taking minutes). We noticed if we change this to using a SQL Authentication instead querying is coming back half a second. We have our on-prem servers setup with other external sites and there is no problem with performance using WIN AD. Just looking to see if there is anything else we need to setup or check?
user
21-03-2024 09:39:25 -0400
code

1 Answer

Hi, I think you should look into the [Execution Trace](https://community.denodo.com/docs/html/browse/latest/en/vdp/administration/appendix/execution_trace_information/execution_trace_information) to determine whether the source, client, or Denodo is the main contributor to the overhead. The knowledge base article, [Best Practices to Maximize Performance IV: Detecting Bottlenecks in a Query](https://community.denodo.com/kb/en/view/document/Best%20Practices%20to%20Maximize%20Performance%20IV%3A%20Detecting%20Bottlenecks%20in%20a%20Query), offers insights on identifying and resolving bottlenecks. Additionally, please refer to the knowledge base article [Accessing MS SQL Server Using Windows Authentication](https://community.denodo.com/kb/en/view/document/Accessing%20MS%20SQL%20Server%20using%20Windows%20Authentication#:~:text=using%20Windows%20Authentication-,Accessing%20MS%20SQL%20Server%20using%20Windows%20Authentication,-Applies%20to%3A). This article provides a detailed explanation of how to utilize Windows Authentication to access SQL Server via a JDBC data source. Hope this helps!
Denodo Team
22-03-2024 11:18:55 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here