Hello.
Our company is running an application that uses the MSDE 2000 (SP4), to load
large amount of data using bulk inserts.
The sqlservr.exe process increases from the 4-10MB that it starts with to
80-100MB after all transactions has been completed.
When starting a new transaction session, the process just continue to grow
causing the OS to perform poorly.
Ok, I understand that while on an insert transaction, the memory should grow
but when we are done, why doesn’t it release the resources?
You can see that this is a bad behavior if you just close the process
manually and start it again, the memory will start with 4-10MB, and the
application still works, meaning that the exe have lots of unused resources.
What can I do about that (other than limiting the memory size to xMB)?
Hi
Not leaking, it is by design
INF: SQL Server Memory Usage
http://support.microsoft.com/default...b;en-us;321363
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli" <Eli@.discussions.microsoft.com> wrote in message
news:3444B8D1-3E64-4EF3-B457-2EFB5543C0C7@.microsoft.com...
> Hello.
> Our company is running an application that uses the MSDE 2000 (SP4), to
> load
> large amount of data using bulk inserts.
> The sqlservr.exe process increases from the 4-10MB that it starts with to
> 80-100MB after all transactions has been completed.
> When starting a new transaction session, the process just continue to grow
> causing the OS to perform poorly.
> Ok, I understand that while on an insert transaction, the memory should
> grow
> but when we are done, why doesn't it release the resources?
> You can see that this is a bad behavior if you just close the process
> manually and start it again, the memory will start with 4-10MB, and the
> application still works, meaning that the exe have lots of unused
> resources.
> What can I do about that (other than limiting the memory size to xMB)?
>
>
|||Ok, it’s by design, pretty weird design, by ok.
Now, how can I handle this, design or not, it is a problem…
Limiting the max memory? Stopping and starring the process of the SQL?
What is the best practice for it?
Eli.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Not leaking, it is by design
> INF: SQL Server Memory Usage
> http://support.microsoft.com/default...b;en-us;321363
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli" <Eli@.discussions.microsoft.com> wrote in message
> news:3444B8D1-3E64-4EF3-B457-2EFB5543C0C7@.microsoft.com...
>
>
|||Hi
Set the MAX memory.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli" <Eli@.discussions.microsoft.com> wrote in message
news:5D23EFC5-6240-47E3-AF83-B8B0CB0DC5D7@.microsoft.com...[vbcol=seagreen]
> Ok, it's by design, pretty weird design, by ok.
> Now, how can I handle this, design or not, it is a problem.
> Limiting the max memory? Stopping and starring the process of the SQL?
> What is the best practice for it?
> Eli.
>
> "Mike Epprecht (SQL MVP)" wrote:
Showing posts with label leaks. Show all posts
Showing posts with label leaks. Show all posts
Monday, February 20, 2012
Memory Leaks
SQL server is experiencing Memory leaks. So much so that 2gb of ram
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read als
o
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seem
s
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...[vbcol=seagreen]
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
>
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> I don't know what causes the problems, but we have had intermittent proble
ms
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NE
T
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read als
o
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seem
s
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...[vbcol=seagreen]
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
>
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> I don't know what causes the problems, but we have had intermittent proble
ms
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NE
T
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
Memory Leaks
SQL server is experiencing Memory leaks. So much so that 2gb of ram
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read also
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
> > dissapears and the server stops.
> >
> > THe server has 3 instances of SQL and most operations use linked servers
> > using oledb provider for oracle driver.
> > I have read some artavles that memory leaks can happen when the data type
> > long is returned using ref cursor.
> > The main queries used the syntax select * from openquery(linked
> > server,'oracle query') and are either select or update. Some cases sp's
> > are
> > created with an input parameter and this input parameter is used to update
> > a
> > single row and this sp is called severl times. Some articles i have read
> > also
> > claim that memory leaks also happen when such a statement is repeatedly
> > executed.
> >
> > Can anyone elaborate on this or give any suggestions as to the cause.
> >
> > SQL 2000 SP3 on windows server 2000
> > MDAC is 2.7 SP1
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seems
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
>> "mat" <mat@.discussions.microsoft.com> wrote in message
>> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
>> > dissapears and the server stops.
>> >
>> > THe server has 3 instances of SQL and most operations use linked
>> > servers
>> > using oledb provider for oracle driver.
>> > I have read some artavles that memory leaks can happen when the data
>> > type
>> > long is returned using ref cursor.
>> > The main queries used the syntax select * from openquery(linked
>> > server,'oracle query') and are either select or update. Some cases sp's
>> > are
>> > created with an input parameter and this input parameter is used to
>> > update
>> > a
>> > single row and this sp is called severl times. Some articles i have
>> > read
>> > also
>> > claim that memory leaks also happen when such a statement is repeatedly
>> > executed.
>> >
>> > Can anyone elaborate on this or give any suggestions as to the cause.
>> >
>> > SQL 2000 SP3 on windows server 2000
>> > MDAC is 2.7 SP1
>>
>> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's
>> OLE-DB
>> provider. I would suggest that you use Oracles OLE-DB provider. It
>> seems
>> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
>> ,Oracle 9i. I have not used with Oracle 10g.
>>
>> HTH
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
>>
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> > Cheers..
> >
> > i'm using Microsofts Provider.
> >
> > I'll try it, but do you know what caused these problems
> > ?
> >
> > "Rick Sawtell" wrote:
> >
> >>
> >> "mat" <mat@.discussions.microsoft.com> wrote in message
> >> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> >> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
> >> > dissapears and the server stops.
> >> >
> >> > THe server has 3 instances of SQL and most operations use linked
> >> > servers
> >> > using oledb provider for oracle driver.
> >> > I have read some artavles that memory leaks can happen when the data
> >> > type
> >> > long is returned using ref cursor.
> >> > The main queries used the syntax select * from openquery(linked
> >> > server,'oracle query') and are either select or update. Some cases sp's
> >> > are
> >> > created with an input parameter and this input parameter is used to
> >> > update
> >> > a
> >> > single row and this sp is called severl times. Some articles i have
> >> > read
> >> > also
> >> > claim that memory leaks also happen when such a statement is repeatedly
> >> > executed.
> >> >
> >> > Can anyone elaborate on this or give any suggestions as to the cause.
> >> >
> >> > SQL 2000 SP3 on windows server 2000
> >> > MDAC is 2.7 SP1
> >>
> >>
> >> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's
> >> OLE-DB
> >> provider. I would suggest that you use Oracles OLE-DB provider. It
> >> seems
> >> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> >> ,Oracle 9i. I have not used with Oracle 10g.
> >>
> >>
> >> HTH
> >>
> >> Rick Sawtell
> >> MCT, MCSD, MCDBA
> >>
> >>
> >>
> >>
> I don't know what causes the problems, but we have had intermittent problems
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NET
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read also
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
> > dissapears and the server stops.
> >
> > THe server has 3 instances of SQL and most operations use linked servers
> > using oledb provider for oracle driver.
> > I have read some artavles that memory leaks can happen when the data type
> > long is returned using ref cursor.
> > The main queries used the syntax select * from openquery(linked
> > server,'oracle query') and are either select or update. Some cases sp's
> > are
> > created with an input parameter and this input parameter is used to update
> > a
> > single row and this sp is called severl times. Some articles i have read
> > also
> > claim that memory leaks also happen when such a statement is repeatedly
> > executed.
> >
> > Can anyone elaborate on this or give any suggestions as to the cause.
> >
> > SQL 2000 SP3 on windows server 2000
> > MDAC is 2.7 SP1
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seems
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
>> "mat" <mat@.discussions.microsoft.com> wrote in message
>> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
>> > dissapears and the server stops.
>> >
>> > THe server has 3 instances of SQL and most operations use linked
>> > servers
>> > using oledb provider for oracle driver.
>> > I have read some artavles that memory leaks can happen when the data
>> > type
>> > long is returned using ref cursor.
>> > The main queries used the syntax select * from openquery(linked
>> > server,'oracle query') and are either select or update. Some cases sp's
>> > are
>> > created with an input parameter and this input parameter is used to
>> > update
>> > a
>> > single row and this sp is called severl times. Some articles i have
>> > read
>> > also
>> > claim that memory leaks also happen when such a statement is repeatedly
>> > executed.
>> >
>> > Can anyone elaborate on this or give any suggestions as to the cause.
>> >
>> > SQL 2000 SP3 on windows server 2000
>> > MDAC is 2.7 SP1
>>
>> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's
>> OLE-DB
>> provider. I would suggest that you use Oracles OLE-DB provider. It
>> seems
>> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
>> ,Oracle 9i. I have not used with Oracle 10g.
>>
>> HTH
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
>>
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> > Cheers..
> >
> > i'm using Microsofts Provider.
> >
> > I'll try it, but do you know what caused these problems
> > ?
> >
> > "Rick Sawtell" wrote:
> >
> >>
> >> "mat" <mat@.discussions.microsoft.com> wrote in message
> >> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> >> > SQL server is experiencing Memory leaks. So much so that 2gb of ram
> >> > dissapears and the server stops.
> >> >
> >> > THe server has 3 instances of SQL and most operations use linked
> >> > servers
> >> > using oledb provider for oracle driver.
> >> > I have read some artavles that memory leaks can happen when the data
> >> > type
> >> > long is returned using ref cursor.
> >> > The main queries used the syntax select * from openquery(linked
> >> > server,'oracle query') and are either select or update. Some cases sp's
> >> > are
> >> > created with an input parameter and this input parameter is used to
> >> > update
> >> > a
> >> > single row and this sp is called severl times. Some articles i have
> >> > read
> >> > also
> >> > claim that memory leaks also happen when such a statement is repeatedly
> >> > executed.
> >> >
> >> > Can anyone elaborate on this or give any suggestions as to the cause.
> >> >
> >> > SQL 2000 SP3 on windows server 2000
> >> > MDAC is 2.7 SP1
> >>
> >>
> >> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's
> >> OLE-DB
> >> provider. I would suggest that you use Oracles OLE-DB provider. It
> >> seems
> >> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> >> ,Oracle 9i. I have not used with Oracle 10g.
> >>
> >>
> >> HTH
> >>
> >> Rick Sawtell
> >> MCT, MCSD, MCDBA
> >>
> >>
> >>
> >>
> I don't know what causes the problems, but we have had intermittent problems
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NET
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
Memory Leaks
SQL server is experiencing Memory leaks. So much so that 2gb of ram
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read also
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1
"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seems
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...[vbcol=seagreen]
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA
|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> I don't know what causes the problems, but we have had intermittent problems
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NET
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
dissapears and the server stops.
THe server has 3 instances of SQL and most operations use linked servers
using oledb provider for oracle driver.
I have read some artavles that memory leaks can happen when the data type
long is returned using ref cursor.
The main queries used the syntax select * from openquery(linked
server,'oracle query') and are either select or update. Some cases sp's are
created with an input parameter and this input parameter is used to update a
single row and this sp is called severl times. Some articles i have read also
claim that memory leaks also happen when such a statement is repeatedly
executed.
Can anyone elaborate on this or give any suggestions as to the cause.
SQL 2000 SP3 on windows server 2000
MDAC is 2.7 SP1
"mat" <mat@.discussions.microsoft.com> wrote in message
news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
> SQL server is experiencing Memory leaks. So much so that 2gb of ram
> dissapears and the server stops.
> THe server has 3 instances of SQL and most operations use linked servers
> using oledb provider for oracle driver.
> I have read some artavles that memory leaks can happen when the data type
> long is returned using ref cursor.
> The main queries used the syntax select * from openquery(linked
> server,'oracle query') and are either select or update. Some cases sp's
> are
> created with an input parameter and this input parameter is used to update
> a
> single row and this sp is called severl times. Some articles i have read
> also
> claim that memory leaks also happen when such a statement is repeatedly
> executed.
> Can anyone elaborate on this or give any suggestions as to the cause.
> SQL 2000 SP3 on windows server 2000
> MDAC is 2.7 SP1
Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
provider. I would suggest that you use Oracles OLE-DB provider. It seems
to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
,Oracle 9i. I have not used with Oracle 10g.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Cheers..
i'm using Microsofts Provider.
I'll try it, but do you know what caused these problems
?
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:6601DAC1-672B-4B9B-B32D-F2EC4BEA4A18@.microsoft.com...
>
> Are you using the Microsoft OLE-DB provider for Oracle, or Oracle's OLE-DB
> provider. I would suggest that you use Oracles OLE-DB provider. It seems
> to work better for me. Notes: This was SQL 2k, Oracle 8i and SQL2k
> ,Oracle 9i. I have not used with Oracle 10g.
>
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
|||"mat" <mat@.discussions.microsoft.com> wrote in message
news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...[vbcol=seagreen]
> Cheers..
> i'm using Microsofts Provider.
> I'll try it, but do you know what caused these problems
> ?
> "Rick Sawtell" wrote:
I don't know what causes the problems, but we have had intermittent problems
using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
provider from MS had some issues here and there. Once we switched our .NET
to Oracle's .NET provider, the problems went away.
You may want to check out the Oracle metalink support site.
Rick Sawtell
MCT, MCSD, MCDBA
|||Thanks
Are there any conflicts between the Microsoft and aoracle providers.
I could not create a linked server using the oracle provider using
enterprise manger. I was gettint the errormessage
7302 coull not create an instance of ole db provider....
I Managed to create it on the server itself but when i try and view the
tables or execute a query from a remote machine i get the above error
"Rick Sawtell" wrote:
> "mat" <mat@.discussions.microsoft.com> wrote in message
> news:B3D168E8-0B3E-427C-9E8F-5580B56A39AE@.microsoft.com...
> I don't know what causes the problems, but we have had intermittent problems
> using the Microsoft drivers for Oracle in the past. Even the new ADO.NET
> provider from MS had some issues here and there. Once we switched our .NET
> to Oracle's .NET provider, the problems went away.
> You may want to check out the Oracle metalink support site.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
Subscribe to:
Posts (Atom)