Failed to reserve contiguous memory

Hello,
(I have to repost it under different header since I didn't get any comment
or answer)
We faced a problem running PERL script which creates big XML file and
inserts it into ntext data type column of the table.
When XML file is relatively small – the process runs OK, but with big file
s
we get the following error appearing in the SQL server log:
2006-04-06 16:01:13.97 spid117 WARNING: Failed to reserve contiguous memory
of Size= 19333120.
2006-04-06 16:01:14.05 spid117 Query Memory Manager: Grants=5 Waiting=0
Maximum=152183 Available=151908
2006-04-06 16:01:14.05 spid117 Global Memory Objects: Resource=2921
Locks=29503 ...
2006-04-06 16:01:14.05 spid117 Dynamic Memory Manager: Stolen=34679 OS
Reserved=5272 ...
2006-04-06 16:01:14.05 spid117 Procedure Cache: TotalProcs=763
TotalPages=2142 InUsePages=899
2006-04-06 16:01:14.05 spid117 Buffer Counts: Commited=337792 Target=337792
Hashed=302526...
2006-04-06 16:01:14.05 spid117 Buffer Distribution: Stolen=32594 Free=530
Procedures=2142...
I checked several common things posted by Microsoft such as network packet
size and sql_variant data type – there is no any connection to our problem
.
Surprisingly, but the same insert works OK when performed from query
analyzer, even for a big files.
There quite amount of posts on the issue implying MemToLive
configuration, however this is a production server, I can't 'play' with it.
I would be very grateful for your help.
Thanks,If you can get the same hardware configuration and the same volume of
the same type of queries in a test environment, then you could probably
recreate your scenario there and "play" with fragmentation in
MemToLeave. When we called Microsoft, it came down to playing with the
-g parameter to increase the amount of memory allocated in MemToLeave
at startup. But still, that only works to a point because the
fragmentation isn't predictable - which is why it will work sometimes
(ie when you run it through QA) and fails at other times... We've just
had to push it back to developers to implement retries.
This just reinforces my opinion that all those nice little non-database
add-ons made to attract developers to SQL Server should really just
never be used...
BB|||If the same insert works ok when performed in QA, even for a big file.
That narrows the problem down to the PERL script rather. It could be a
time out issue. What library you use to connect to SQL Server in perl?
May be you should post more details in the PERL user group and see if
people have similar experiences.
Mel

Failed to reserve contiguous memory

Hello,
(I have to repost it under different header since I didn't get any comment
or answer)
We faced a problem running Perl script which creates big XML file and
inserts it into ntext data type column of the table.
When XML file is relatively small â' the process runs OK, but with big files
we get the following error appearing in the SQL server log:
2006-04-06 16:01:13.97 spid117 WARNING: Failed to reserve contiguous memory
of Size= 19333120.
2006-04-06 16:01:14.05 spid117 Query Memory Manager: Grants=5 Waiting=0
Maximum=152183 Available=151908
2006-04-06 16:01:14.05 spid117 Global Memory Objects: Resource=2921
Locks=29503 ...
2006-04-06 16:01:14.05 spid117 Dynamic Memory Manager: Stolen=34679 OS
Reserved=5272 ...
2006-04-06 16:01:14.05 spid117 Procedure Cache: TotalProcs=763
TotalPages=2142 InUsePages=899
2006-04-06 16:01:14.05 spid117 Buffer Counts: Commited=337792 Target=337792
Hashed=302526...
2006-04-06 16:01:14.05 spid117 Buffer Distribution: Stolen=32594 Free=530
Procedures=2142...
I checked several common things posted by Microsoft such as network packet
size and sql_variant data type â' there is no any connection to our problem.
Surprisingly, but the same insert works OK when performed from query
analyzer, even for a big files.
There quite amount of posts on the issue implying MemToLive
configuration, however this is a production server, I can't 'play' with it.
I would be very grateful for your help.
Thanks,If you can get the same hardware configuration and the same volume of
the same type of queries in a test environment, then you could probably
recreate your scenario there and "play" with fragmentation in
MemToLeave. When we called Microsoft, it came down to playing with the
-g parameter to increase the amount of memory allocated in MemToLeave
at startup. But still, that only works to a point because the
fragmentation isn't predictable - which is why it will work sometimes
(ie when you run it through QA) and fails at other times... We've just
had to push it back to developers to implement retries.
This just reinforces my opinion that all those nice little non-database
add-ons made to attract developers to SQL Server should really just
never be used...
BB|||If the same insert works ok when performed in QA, even for a big file.
That narrows the problem down to the perl script rather. It could be a
time out issue. What library you use to connect to SQL Server in perl?
May be you should post more details in the perl user group and see if
people have similar experiences.
Mel

Faced unknown problems on SQL Server (Urgent)

Hi all,

I'm facing some unknown errors occured in SQL server. SQL server prompt out the errors and I'm aware when are those errors occur.

Server displayed the sentences as below which I do not have any idea with its.


1) xpstar.dll to execute extended stored procedure 'xp_MSADEnabled'
2) xpsqlbot.dll to execute extended stored procedure 'xp_qv'

Anyone has any idea on how to solve those problem or any idea how is it caused?

I'm very appreciate for any reply and thank you for helping!!The second one is normally found in SQL Server's errorlog. I am not sure about xp_MSADEnabled. Have you registered the SQL Server with AD in Enterprise Manager? These messages are normally recorded in the errorlog, and do not normally indicate a problem.|||Hi,

Thank you for reply, MCrowley.
Any idea or suggestion on how to make the SQL server can execute back
because the system users could not login because of the database.|||Depends on what is wrong. What error are the users getting?|||Hi,

Users could not login to the system since both the issues happened. :S