Forum Discussion
Using pyodbc in python 3.11 notebook
- 10 months ago
Hi P_work ,
Thanks for the follow up.
As Vinodh247 already mentioned, keeping long running global connections is not recommended because the SQL analytics endpoint can become idle and drop sessions in the background. The Microsoft documentation notes that the endpoint can be suspended after inactivity:
https://learn.microsoft.com/en-us/fabric/data-warehouse/sql-analytics-endpoint-performanceIn that case a reused pyodbc connection may fail since pyodbc does not automatically recover when the backend session is dropped.
There are similar reports in the community where idle connections to the lakehouse SQL endpoint resulted in errors:
Solved: Failed to access/connect to Lakehouse SQL Endpoint... - Microsoft Fabric CommunityTo reduce repeated reconnect times you can keep related queries inside the same connection block and optionally add a simple retry approach for transient disconnects.
Hope this helps. Please reach out for further assistance.
Thank you.
Pyodbc does not give you a native connection pool, and you do not want one inside fabric notebooks anyway. Use one connection per endpoint (one for fabric SQLDB, one for lakehouse SQL endpoint). Do not pool. Wrap every operation in a with block so the connection opens, executes, and closes cleanly. Avoid long lived or global connections because Fabric endpoints drop idle sessions and pyodbc does not auto-recover well.