I am trying to connect Airbyte to a large SQL Serv...
# replication-ask-ai
h
I am trying to connect Airbyte to a large SQL Server. During the connection process there is always a HTTP 402 Error, service temporarily unavailable.
k
It seems like you're encountering a "Service temporarily unavailable" error (HTTP 502) when trying to connect Airbyte to a large SQL Server. This issue has been reported by other users as well. Here are some steps and considerations based on the information available: 1. Check Connection Tool: First, ensure that your SQL Server database is accessible from the machine running Airbyte. You can use the check connection tool in the Airbyte UI to verify this. [Source](https://docs.airbyte.com/integrations/sources/mssql#1-make-sure-your-database-is-accessible-from-the-machine-running-airbyte). 2. Deployment Configuration: If you are running Airbyte on Kubernetes, ensure that your deployment has sufficient resources. One user reported increasing the capacity of the pods (RAM up to 4Gi and CPU up to 4 for the
worker
pod and up to 1G in RAM & 1 CPU for
temporal
and
webapp
pods) but still faced issues. [Source](https://github.com/airbytehq/airbyte/issues/31695). 3. Timeout Issues: There have been instances where users faced timeout errors when connecting to SQL Server. This could be related to the Hikari connection pool timing out. Ensure that your network settings and SQL Server configurations are optimized to handle large schema fetches. [Source](https://github.com/airbytehq/airbyte/discussions/31267). 4. Version Compatibility: Ensure that you are using a compatible version of Airbyte. There have been reports of errors occurring after upgrading to certain versions. If you recently upgraded, consider rolling back to a previous stable version to see if the issue persists. [Source](https://github.com/airbytehq/airbyte/issues/27837). 5. Logs and Debugging: Check the logs for any specific error messages that might give more insight into the issue. If there are no logs in the
worker
pod, it might indicate a deeper issue with the deployment or configuration. If these steps do not resolve the issue, you might want to provide more details on the specific error messages and your current setup for further assistance. You can also refer to the [Airbyte documentation](https://docs.airbyte.com/) for more detailed troubleshooting steps. If you need further assistance, you can also raise an issue on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte/issues) or seek help on the [Airbyte community forum](https://discuss.airbyte.io/).