Close recordsets and release memory

[Dr_Michael]

Using ADO, we know that each connection we use and each recordset, after finishing what we have to do with them, we must close the recordset and the connection with the database and set both items to nothing.
I ask you know:
Let's assume that we have the following scenario:
A server machine (database server) and a lot of client machines that perform everyday a lot of queries to the server 24 hours per day!
If the application that the clients use to perform the queries, doesn't close neither the connection nor the recordsets and doesn't set them to nothing, then what will be the result?
You are all ready to say "It will crash the server". Please answer the question ONLY IF YOU HAVE TEST THIS SCENARIO! I know the theoretical answer but I want the PRACTICAL one!
Thank you all!

P.S. The server runs on Windows NT 4 Service Pack 6. SQL Server 7 is the database on that and nothing else runs there. A window of Task Manager program is always open to monitor the server...

Michael Vlastos
Automation Engineer
Intracom, Research & Development Department
Athens, Greece

Nobody is going to answer this?, I think no, all we have readed about test on server in WEB in many tutorials, and did't say "It will crash the server", maybe say "many client will no connect" and this depends on many factors, then i think you must do a test with your resources (modem, clients, server, memory, proccessor, etc).
Regards
Juan Arturo Gomez
jasistemas@correoweb.com