>
> I am now thinking there must be an easy way to fire off this query in a
> different datasession or thread so that any problems caused by the ODBC
> driver are lost after each execution, any brilliant ideas?
>
Memory is allocated on the process level and not automatically freed when
the thread
>
> We are running into an intermittent issue w/ our SQL Server running
> SQL2016. It's not that our tables are all that large (usually), but our
> server is trying to manage around 550 different DB's parked on it. Few of
> the DB's are open at any one time, but the server has to keep track of them
2 matches
Mail list logo
