Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Capacity Error

Author  Topic 

khalik
Constraint Violating Yak Guru

443 Posts

Posted - 2002-05-16 : 03:34:34


hi

after a search in forums i was not able to find any thing which tak about Capacity Error .....

i have a vb app using ado 2.7 it was working fine and recently it started giving me a error...

when ever i have a begin transaction.. i get a error

A New Transaction could not be Created Due to unspecified Capacity Error issue

need some help why is it and how to solve it...

and one more quick one...
is there some way of checking the server status...
my app connect in start and in mean time server is down how do we find the status of it...

thanks


======================================
Ask to your self before u ask someone

rihardh
Constraint Violating Yak Guru

307 Posts

Posted - 2002-05-16 : 08:50:06
Hmmm... Do you have an open connection all the time your app is running? Do you have multiple transactions running at the same time using this connection? If so, this might be the problem.

You can check the status and many other usefull things of SQL server using SQL-DMO.

Go to Top of Page

khalik
Constraint Violating Yak Guru

443 Posts

Posted - 2002-05-16 : 21:44:03


thanks rihardh
my App is a client server once the app started a connection is established and is on till the user exits... and it a multy user app so on a given point of time there can me many transaction active... but that was not the problem before recently it stated . i dont think that will be problem....

thanks

======================================
Ask to your self before u ask someone
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2002-05-16 : 22:13:30
I'm thinking that ADO 2.7 may be at issue, especially if it was recently installed on any machines that didn't have it before. Have you checked that all of the machines (including the SQL Server) have the same MDAC components? If there's a mismatch somewhere, it might be causing some obscure problem.

The 2nd thing is the fact that it's a multi-user app that holds connections open from login to logout. That's bad. Especially in ADO. I won't say it's badly designed because I don't know the circumstances, but it is definitely not ideal. If that can be rewritten, to at least close the connection after a long period of inactivity, that will help. And if the connection is NOT explicitly closed (meaning that the app just terminates) there's no guarantee that the connection is closed properly. Someone could exit the app and reopen it, and a new connection established while the old connection is not cleared.

I can't find any documentation in Books Online regarding the maximum number of transactions (capacity) but I'm certain there is a limit, possibly with internal structures like stacks and such. Considering that there's no explicit transaction limit in BOL, and that the error message states "unspecified capacity" it seems to me that this is the culprit. A lot of transactions also means a lot of locks, and while it may not exceed the limit it will eat up RAM.

Go to Top of Page

khalik
Constraint Violating Yak Guru

443 Posts

Posted - 2002-05-17 : 01:50:45


thanks a lot robvolk it is in details info...
the App is running for last one yr no problem as such.

ur 1 point
the system had early version of ADO and the other screen work which dont have begin transaction work fine...

2nd point
if i dont maintain a open connection all the time the client should connect and most of the time is wasted in connecting and i dont think what will be a good idea... mostly it is a online APP so beening inactive not much.. and when user terminates the app (VB code) query_unload event we are setting connection object to nothing so the connection is closed..

3rd point

quote:
A lot of transactions also means a lot of locks, and while it may not exceed the limit it will eat up RAM.


but that will it lead to a such error and either BOL nor any other site talk about it.

when we start transaction by begin trans is not for long time
it will be in with in a event begin ..commit / rollback and not much of processing of record.. i posted in vbfourms people say that if lack of database space it might lead this.. if so there should be a log of it if so how can i find out the details of it....

thanks a lot


======================================
Ask to your self before u ask someone
Go to Top of Page
   

- Advertisement -