VB6 .dll Using ADO Requires Frequent Restarts | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

VB6 .dll Using ADO Requires Frequent Restarts

Hello, We’ve got an application that uses a .dll compiled with VB6 to access a SQL database using ADO. It is managed by COM+ in Windows 2000 Server.
The problem we’ve had forever is that after running for some random lenth of time (<24Hrs) the app get’s bogged down. Our current fix is to shut down and restart the component.
I was wondering if anyone knew any possible fixes. The only ideas I have now are that 1)There is no connection pooling with VB6 2)I need to archive some of the data in the DB. <shrug> Any ideas? Thanks,
Any message on event viewer during this behaviour?
IS the SQL server available for normal queries during this time? Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Well, the logs in the event viewer are empty. And I’m pretty sure that the server IS available.
We have another application with a similar component that runs fine the entire time. I think the only difference is the size of the DB. That’s why I was wondering if it was just an archiving issue.
I feel there is some memory leak issue on the machine where the erring application uis run. Did you look at the perfmon counters for the same. Whren you say the application boggs down, do you see high resorce utilization on SQL Server or the application end? How about checking for any non-committed transactions in the database which may have acquired over a period of time? What about connections?<br /><br />High amount of data can’t be a problem as if that was the case, the application would have run slower from the start and not after it has run for certain period of time…. [}<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ />]<br /><br />My 2 cents….<br /><br />Gaurav<br /><i>Moderator<br /><font size="1">Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard</i></font id="size1"><br /><font size="1">The views expressed here are those of the author and no one else. There are no warranties as to the reliability or accuracy of anything presented here.</font id="size1">
What do you mean bogged down. You get timeouts? Do the components on the working and non working server have identicl properties in COM+?
Do the servers have same MDAC version? Some MDAC versions had memory leaks.
Do the servers/application have the same default network libray (tcp/ip or named pipes?)
When issues occur, how much memory is free on the server, how is the cpu utilization, how many connections are in the database (any blocks?)
Does the server have any other applications running on it or some configuration that makes it different from the working server?
Is SQL Server running on the server, if so is the memory limited? Otherwise it will eventuall take all the memory.

True, and also collect the counters information using PERFORMANCE MONITOR in order to assess the issue. Counters like memory, physical disk, process, processor and SQL server memory & locks. Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.