CPU goes up 100% for no apperent reason

[GHG]

OS Name Microsoft Windows 2000
Version 5.0.2195 Service Pack 4 Build 2195
System Model PowerVault 725N
Total Physical Memory 1,572,336 KB
Available Physical Memory 856,568 KB
Total Virtual Memory 3,777,256 KB
Available Virtual Memory 2,407,764 KB
Page File Space 2,204,920 KB

Pervasive.SQL V8 sp1

The program ntdbsmgr.exe uses 99% CPU for no apperent reason.

Thanks for the help,
GHG

 

[mirtheil]

What's running in terms of Pervasive? Any ODBC queries? Crystal Reports? Anything like that? What's happening in terms of the Pervasive MOnitor? Any pattern to this 99% CPU usage?

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[jforero]

Mirthel, thanks for answering.

I am with GHG.

This is the scenario:

We have ACCPAC program running its database in a server with Pervasive V8.

We have some VBA customized programs that use ADO to connect to that database as following:

Set oCon = New ADODB.Connection
oCon.ConnectionString = "Provider=PervasiveOLEDB.8.10;Data Source=DBSEAL;Location=powervault"
oCon.CursorLocation = adUseClient
oCon.Open

Set oComTra = New ADODB.Command
oComTra.CommandText = "SELECT IDCUST, IDINVC, CNTBTCH, CNTITEM, CNTLINE, IDARACCT FROM ARATR"
oComTra.CommandType = adCmdText
oComTra.ActiveConnection = oCon

Set oRecTra = New ADODB.Recordset
Set oRecTra.Source = oComTra
oRecTra.CursorType = adOpenStatic
oRecTra.LockType = adLockReadOnly
oRecTra.Open

What I have noticed is that when the program is opening the ADO recordset the CPU in the server goes up 100%.

What could be the problem?

Any help appreciated.

Thanks, Jose.

 

[Peager]

Jose,

I think that what you are seeing is that the MS server is just giving 100% of it's attention to your SQL request (Select statement). It appears normal to me.

Paul

 

[MacolaHelp]

Is your page file on a partition that is getting low on space, like a smaller C partition? If so, move it onto another drive with more free disk space. I fought this battle for weeks at one site & once we moved the page file, I've never really had another problem, though it was psql2001 sp3 at the time.