On behalf of all of us here at JodoHost, staff and customers alike, I’d like to welcome our new server, MSSQL7 to the family.
We hope you’ll have a long and prosperous life there at the Jodo data centre, and we will do everything we can to make you feel at home, and a beloved member of our growing cluster. We know you’ll make make many rewarding new connections here.
If there’s anything you need, please don’t hesitate to ask the Jodo staff by beeping. In the event you feel a bit blue and fall over, you will be taken care of in no time, given a strong cup of tea and a stirring motivational talk.
We all look forward to interfacing with you in the very near future!
[QUOTE=Yash]
Our MSSQL servers are quite satisfied, they hardly ever beep.. We have never had a total mssql server crash that has required a recovery from backup
[/QUOTE]
As badly coded ASP app leaving connections open? I created an ASP class for using ADO which, when the page ends and the Class_Terminate code runs, it closes all open db connections, as long as they were opened using the class.
It means an ASP script can terminate anywhere anytime and all open connections will be closed.
Very simple bit of code, just a wrapper for creating and destroying connection & recordset objects, but IMO all ASP coder should be using that methodology to manage ADO connections properly. I can post it up if you want, but don’t know how you’d get people to use it.
