Error 513 when setting up connection to source DB with over 200+ tables

<@U01MMSDJGC9> - Any thoughts on how to fine tune the mssql connector? We keep receiving java heap space errors on large CDC change scenarios where there are millions of rows in the underlying_CT table. We have tried using the postgres actor_definition route but don’t seem to be able to overcome the java heap space error. see above thread

example error is :
2024-10-03 21:40:00 source > Terminating due to java.lang.OutOfMemoryError: Java heap space

root@airbyte-abctl-control-plane:/# kubectl get po -o custom-columns=“Name:metadata.name,CPU-limit:spec.containers[].resources.limits.cpu, CPU-request:spec.containers[].resources.requests.cpu, memory-limits:spec.containers[].resources.limits.memory, memory-request:spec.containers[].resources.requests.memory” --namespace=airbyte-abctl

Name CPU-limit CPU-request memory-limits memory-request
airbyte-abctl-airbyte-bootloader 1 500m 12Gi 2Gi
airbyte-abctl-connector-builder-server-5c6d48b574-tpm7h
airbyte-abctl-cron-5ddb45bc4d-swvcz
airbyte-abctl-pod-sweeper-pod-sweeper-7cbbf9cf6d-gfczc
airbyte-abctl-server-579f67894b-9m9ht
airbyte-abctl-temporal-d858d6866-zt6s4
airbyte-abctl-webapp-7f5b9b7654-8bmdg
airbyte-abctl-worker-5989b87ccf-2q59w 500m 250m 2Gi 2Gi
airbyte-abctl-workload-api-server-d64449cb8-czc2z
airbyte-abctl-workload-launcher-65854658f9-d57k9
airbyte-db-0
airbyte-minio-0 200m 200m 1Gi 1Gi
replication-job-13296-attempt-0 500m,500m,500m 500m,500m,500m 2861Mi,2861Mi,2861Mi 2861Mi,2861Mi,2861Mi
replication-job-13297-attempt-0 1,1,1 500m,500m,500m 12Gi,12Gi,12Gi 2Gi,2Gi,2Gi

Internal postgress db with abctl.