We Keep Coding

Is there a limit on the number of connections opened from a client's side to a SQL Server database?

I'm working on a Python application with an SQL Server database using pyodbc, and I need to open multiple connections from the application's side to the database.
I learnt that the max number of connections allowed on an instance of the SQL Server database is 32,767. My understanding is this is the max that the DB instance "can handle", i.e. all simultaneous users combined.
Is there a limit on how many connections one client can open towards the same database instance, is it also 32,767? If yes, where / how is this limit configured?

Taking an educated guess here that there is no connection count limit on the client side towards the same DB instance, there is a limit of 32,767 on the server side, but the client would be more likely to run out of other resources way before it gets close to this figure.
I was using one connection, one cursor, and threading to insert multiple records, but kept getting a "connection is busy" error, this is resolved by adding "MARS_Connection=yes" in the pyodbc database connection string, thanks to this MS documentation.
Related:
How costly is opening and closing of a DB connection?
Can I use multiple cursors on one connection with pyodbc and MS SQL Server?

Create cx_Oracle Python timeout on connect

I'm trying to get the Oracle inbuilt timeout attribute to work in Python.
Some relevant docs are here:
https://cx-oracle.readthedocs.io/en/latest/connection.html
import cx_Oracle
connection = cx_Oracle.connect("user/pass#thedb")
connection.callTimeout = 2000
cursor = connection.cursor()
The trouble is that the initial connection command is the one that is taking an excessive period to timeout (several minutes).
My question is, is there a way to somehow apply the callTimeout before the connection is made? or is there another way to do what I want?
I'm aware of this help:
Set database connection timeout in Python
It seems excessive to use threads for this.

pymysql close connection and clean port

I'm making a really transactional script that is migrating data from one nosql db to mysql but after a like 2 or 3 minutes I get this message
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on
'foo.com' ([Errno 99] Cannot assign requested address)")
I'm already opening and closing connections as soon as they finish (since the script is multiprocessing to get a better usage of the server resources) I already have something that waits between tries,
but rather than having a bandaid solution I would like to make my script better, is there a way in which I can make pymysql disconnect and clean the used port?
I'm using an aws ubuntu server for the migration, I'm already aware that ubuntu keeps the ports open for 60 seconds and I've already extended the range of ports to the max, the script is running on a pool of 15 concurrent process, the mysql server is aws hosted (aurora).
So far while testing the script that I'm using processes about 10000 records per second.
Update:
Missed a 0 on the amount of records per second

python mysql database connection error

I am trying to access the remote database from one Linux server to another which is connected via LAN.
but it is not working.. after some time it will generate an error
`_mysql_exceptions.OperationalError: (2003, "Can't connect to MySQL server on '192.168.0.101' (99)")'
this error is random it will raise any time.
each time create a new db object in all methods.
and close the connection as well then also why this error raise.
can any one please help me to sort out this problem

This issue is due to so many pending request on the remote database.
So in this situation MySql closes the connection to the running script.
to overcome this situation put
time.sleep(sec) # here int is a seconds in number that to sleep the script.
it will solve this issue.. without transferring database to local server or any other administrative task on mysql

My solution was to collect more queries for one commit statement if those were insert queries.

SQL Server 2005 terminating connections after 30 sec

We moved our SQL Server 2005 database to a new physical server, and since then it has been terminating any connection that persist for 30 seconds.
We are experiencing this in Oracle SQL developer and when connecting from python using pyodbc
Everything worked perfectly before, and now python returns this error after 30 seconds:
('08S01', '[08S01] [FreeTDS][SQL Server]Read from the server failed (20004) (SQLExecDirectW)')

First of all what you need is profile the sql server to see if any activity is happening. Look for slow running queries, CPU and memory bottlenecks.
Also you can include the timeout in the querystring like this:
"Data Source=(local);Initial Catalog=AdventureWorks;Integrated Security=SSPI;Connection Timeout=30";
and extend that number if you want.
But remember "timeout" doesn't means time connection, this is just the time to wait while trying to establish a connection before terminating.
I think this problem is more about database performance or maybe a network issue.

Maybe check your remote query timeout? It should default to 600, but maybe it's set to 30? Info here