MSDASQL ODBC queries to Linked Servers hang with no response after a couple weeks.

Question

MSDASQL ODBC queries to Linked Servers hang with no response after a couple weeks.

Ted 0

Hi all,

Our current setup is a linked server to NetSuite ODBC using MSDASQL 17 as the provider.
Everything works and runs fine and fast for about 2 weeks. Then the error will occur.
There will be no error message or anything, but the query just "hangs". The cpu time increases very small does while the wait time increase exponentially. There's no error but no data/rows are being copied over. Also when this happens, I will try "Test Connection" with the linked server which also just hangs with no error message. The wait_type is OLEDB and wait resource states our linked Server?

Our solution for now has to been to either resume/restart the SQL Server Service or the Server itself, both of which works but it's bad practice and wasn't an issue 3-6 months ago.
Is there any reason for this and is there any solution for this?
Thanks!

I'm also aware of a known issue since SQL Server 2000 with rolled-back operations through linked servers, where the linked server is not SQL Server, but like I said it wasn't an issue 3-6 months ago.

2 answers

Your answer

Answer 1

Erland Sommarskog 132.9K

This would be an issue in MSDASQL or the NetSuite ODBC driver. Or whatever NetSuite is talking with on the other end. I'm more inclined to put the blame on the latter two.

The wait type OLEDB means that SQL Server has called the OLE DB provider, and SQL Server has thereby given up all control. Which amongst other things means that you cannot kill it.

The only thing you possibly could do to alleviate the situation from the SQL Server side of things is to uncheck "Allow in-process" the OLE DB provider, and then find a way to kill what is running the OLE DB/ODBC thing from Windows when it reaches Nirvana.

Else, you would need to talk to the vendor of NetSuite.

Ted 0 Reputation points

2026-02-10T21:04:50.27+00:00

Hi Erland,
Thank you for your response. So I did message the vendor of Netsuite, and they claimed there were not records or logs that showed that the call made it to the Netsuite server.
Is there any protocol or best practice to debug MSDASQL? could this issue be a version error? (17 vs 18)
Erland Sommarskog 132.9K Reputation points

2026-02-10T21:48:08.88+00:00

MSDASQL 18? Is there one? I believe MSDASQL comes with the operating system.

Sounds like you are stuck in nowhere land. SQL Server people like points to NetSuite. And NetSuite points back.

If this can be debugged? That would be through WinDbg, and it would require quite a different skill set from what you can expect from a regular DBA. No, I've never done something like that myself; I've only watched Bob Ward do it in his presentation.

You could open a support case with Microsoft, and maybe they will help you. But unless it is actually an in SQL Server or MSDASQL, the support case will cost you an arm and a leg.
Ted 0 Reputation points

2026-02-10T21:52:37.75+00:00

Sorry I meant NetSuite ODBC driver. Im currently on NetSuite ODBC driver 17. Do you think updating to NetSuite ODBC driver 18 have any effect?
Erland Sommarskog 132.9K Reputation points

2026-02-10T21:55:44.9466667+00:00

Generally, when you run into issues like this, it pays to be on the most recent version when you discuss with the vendor. So, yes, it could certainly be worth trying, but please be aware that I know absolutely nothing about NetSuite.
Ted 0 Reputation points

2026-02-10T21:59:24.6266667+00:00

Thanks Erland, appreciate your help and support
Akhil Gajavelly 1,560 Reputation points Microsoft External Staff Moderator

2026-02-12T05:04:17.2633333+00:00

Hi @Ted ,

Glad to hear the solution worked for you. Since this resolved the issue, please consider marking @Erland Sommarskog reply as the accepted answer so it can help others facing the same problem.

Appreciate the confirmation.

Thanks,
Akhil.
Erland Sommarskog 132.9K Reputation points

2026-02-12T21:34:47.46+00:00

Akhil, I think you need to check the thread a little closer. It does not seem to me that Ted's issue is resolved; he only thanked my for my input. And since I've only posted comments, there is nothing that he can mark as an answer.

Answer 2

It sounds like you are experiencing a performance issue with your linked server setup using MSDASQL 17 for ODBC connections to NetSuite. This type of hanging behavior can occur due to various reasons, including network issues, resource constraints, or problems with the ODBC driver itself.

Here are a few suggestions that might help you troubleshoot and resolve the issue:

Check Resource Availability: Ensure that your SQL Server has sufficient resources (CPU, memory, etc.) available. If resources are constrained, it may lead to hanging queries.
Network Stability: Investigate the network connection between your SQL Server and the NetSuite ODBC source. Network instability can cause queries to hang.
ODBC Driver Updates: Make sure you are using the latest version of the ODBC driver. Sometimes, bugs in the driver can lead to performance issues, and updates may contain fixes.
Connection Timeout Settings: Review and adjust the connection timeout settings for your linked server. If the timeout is set too high, it may cause queries to hang longer than expected.
Monitor Wait Types: Since you mentioned that the wait type is OLEDB, you might want to monitor the specific wait statistics to identify if there are any patterns or specific issues related to OLEDB.
Review SQL Server Logs: Check the SQL Server error logs for any warnings or errors that may provide additional context about the hanging queries.
Consider Alternatives: If the issue persists, you might want to explore alternative methods for connecting to NetSuite, such as using a different driver or approach that might be more stable.

If the problem continues after trying these steps, you may need to consider reaching out to Microsoft support or the ODBC driver vendor for further assistance.

References:

Share via

MSDASQL ODBC queries to Linked Servers hang with no response after a couple weeks.

2 answers

Your answer