Results 1 to 2 of 2
  1. #1
    Join Date
    Feb 2006

    Unanswered: Sybase Provider ran out of memory

    Hi All,

    I am running a .Net Windows Service hourly which connects to Sybase Link Server thru SQL Server 2000. The service is a threaded application as it spawns 40 threads to connect to Sybase DB's using 'openquery' from SQL stored procs.

    After it ran for hours (approx 30 Hrs), the when the service calls SP whcih has got openqeury to Sybase Linked Servers fails. It throws following exception,

    "System.Data.SqlClient.SqlException: OLE DB provider 'Sybase.ASEOLEDBProvider' reported an error. The provider ran out of memory."

    The sybase provider is told to use Out of SQL Server process memory. When the sybase provider runs out of memory, I checked the Available free memory in the machine. It is still 4GB out of 8GB.

    Please let me know the reason for the Provider running out of memory often if anybody has faced this issue before.

    The version of the Sybase provider in the machine is Sybase.ASEOLEDBProvider 5.0.

    Help is needed badly...

    Thanks in adv,

  2. #2
    Join Date
    Jan 2006
    Hate to be critical, but why this architecture? Connect to Sybase directly.

    Jay Grubb
    Technical Consultant
    OpenLink Software
    Product Weblogs:
    Universal Data Access & Virtual Database Technology Providers

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts