• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 414
  • Last Modified:

SQL Server 2005, Not enough storage when inserting records.

We have written an application which migrates from an interbase database to SQL Server 2005.

The software works fine on a development station when both interbase and sql server 2005 are on the same machine. ( we have tested millions of inserts on many different dev stations).

In Production, the migration software (running on same machine as interbase), cannot appear to insert specific records into the database, reporting error "Not enough storage is available to complete this operation"

The destination database should have ample space, and memory, and inserts are failing every time (not intermittent).

My suspicion is that it had something to do with running the software via the network or possibly something to do with a blob field (which causes space lookup which gets executed incorrectly possibly because of the via network scenario).

Note that other records insert fine.

Any thoughts as to what could be causing this ?
0
beefcake5000
Asked:
beefcake5000
  • 8
  • 4
  • 3
  • +2
1 Solution
 
chapmandewCommented:
Are you sure that there is enough space?  Does it error when you insert just one record?  
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
from the error message, MS suggests the following actions:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/3715.mspx?mfr=true

Do one of the following, then retry the operation:
(1) reduce the number of running programs;
(2) remove unwanted files from the disk the paging file is on and restart the system;
(3) check the paging file disk for an I/O error;
(4) install additional memory in your system.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
or, with SQL 2000, I found this bug (fixed), so you might have the "old" client tools?
http://support.microsoft.com/kb/889170
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
beefcake5000Author Commented:
I am 99.9999% sure it is not a resource issue in this instance.
The migration process migrates successfully 120 records into one table, then fails approximately 100 times on inserting into another table.

Both tables are part of the same database.
0
 
chapmandewCommented:
hmm...have you tried dbcc checktable()?
0
 
beefcake5000Author Commented:
I have ruled out anything to do with blob fields, there are none.

What does dbcc checktable() do ?
0
 
chapmandewCommented:
it checks the integrity of the pages of the table.
0
 
beefcake5000Author Commented:
angelll, could it be that we have an old version of the ADO connection drivers on the production machines ?

and how do i update these ?
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
a small vbscript to retrieve the ado version:
http://www.vbrad.com/article.aspx?id=5

Dim o As Object
    
    On Error Resume Next
    Set o = CreateObject("ADODB.Connection")
	
    If Err.Number = 0 then
        'ADO with version  o.Version  is installed
    Else
        'ADO is not installed
    End If

Open in new window

0
 
beefcake5000Author Commented:
I will need to check this version tomorrow, as I do not have access to the machine from here.

Are you able to help with expected versions, and where to get updated drivers so that I can try tomorrow morning ?
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
on this page, you can download the latest ADO (not .net) version: 2.8:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en

you also have a link to the 2.8 SP1, and another link to the MDAC version checker software.
0
 
beefcake5000Author Commented:
An update on this,

The MDAC has been updated and no difference there. I have tested on 3 more environments, and always the problem is encountered when the station running client, is on a different machine from database.

Some records are migrated successfully and some produce "not enough storage" error. If i rerun transfer, it is the same records each time.

This is the same whether I use ODBC or SQL.

I trimmed insert down to just the keys, incase records had invalid data, this unfortunatley made no difference.

Very strange thing is that this is not encountered on any dev station.

Over to the experts....
0
 
beefcake5000Author Commented:
I also checked tempdb, and appears to have plenty of space along with databases involved.
0
 
beefcake5000Author Commented:
It appears to be a problem with ntext fields if i take them out, all seems to work fine.
0
 
beefcake5000Author Commented:
I managed to resolve this issue myself. It turned out to be a bug with the MIDAS data provider drivers. I replaced with a newer version of the driver and it worked.
0
 
Daniel WilsonCommented:
Glad you resolved it.
Would you accept your explanation as the solution?
And if you found some of the expert comments helpful, would you award them points?  Points you do not award come back to your account.
Thanks.
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 8
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now