FreeTDS Bad token from the server (sql-server)?

A quick google search turned up this microsoft article that says: Often caused by an abruptly terminated network connection, which causes a damaged Tabular Data Stream token to be read by the client. Was the server network bound? I have no experience with MS-SQL but does it have a limit on the number of connections you can make?

You need to use some sort of connection pooling. Windows itself (including Windows Server X) will only allow a certain number of socket connections to be created in a given time frame, event if you close them. All others will fail after that.

A connection pool will keep the same sockets open, avoiding the problem. Also, new connections are REAL slow. HTH.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.