Error 17122 : initdata: Warning: Could not set working set size to 1038848 KB.

Error 17122 : initdata: Warning: Could not set working set size to 1038848 KB.

Post by Ben Smil » Wed, 10 Jan 2001 19:56:28



Dear all,

    I am urgently request for a solution for this case from my SQL Server:

    From EventLog: 17122 : initdata: Warning: Could not set working set size
to 1038848 KB.

    SQL Server configuration:
        SQL Server 7.0 + SP3 on NT 4.0 + SP5
        SQL: Dymanic memory configuration: max = 900 M
        1.0 G Memory
        MDAC 2.1.1.3711.11

    I have a VB program on this SQL server processing large volumn of data
insertion.
    The SQL WriteLog process increasingly takes memory and the SQL Server
dynamical memory
    is also increased.

    (1) I have already setup a Backup Log agent to truncate the log hourly
with Trunc Log on CheckPoint = False

    (2) I have also test not to use the hourly log backup with Trunc Log on
CheckPoint = True

    (3) I have also setup a non-logged UpdateText statement in my program
    (e.g. if i mod 1000 = 0 then execute this update text statement)
    in a bid to invalidate the log backup sequence.

    But all in vain.

    Value of i                                                1        -->
1000        -->        10000        -->    60000
    Transaction Log Size                                10 M            15 M
56 M                175 M
    SQL Server DB Size                                50 M            60 M
170 M                450 M
    WriteLog Sys Process Memory                5 M                50 M
500 M            900 M
    SQL Memory Used (dynamically)            256 M             312 M
845 M                940 M

    The log size, db size, and the memory used is the roughly figure.
    You can see the WriteLog sys process memory takes so much memory during
the process,
    however the transaction log size does not take so much.

    The SQL Server takes memory increasingly, the VB finally only have a
little to run,
    and performance is dropped dramatically.

    Any ideas, hints or suggestions are highly appreciated.

    Thanks.

Ben

 
 
 

Error 17122 : initdata: Warning: Could not set working set size to 1038848 KB.

Post by Neil Pik » Wed, 10 Jan 2001 21:30:16


Ben - see the memoryleak FAQ entry.  Turn off "set workingset size" in
sp_configure and reduce the maximum SQL memory to 800MB.  See if that helps/.

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 Reply here - no email
 SQL FAQ (484 entries) see
 http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
 (faqxxx.zip in lib 7)
 or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
 or www.sqlserverfaq.com
 or www.mssqlserver.com/faq

 
 
 

1. error 17122 : initdata: Warning: Could not set working set size to 519104 KB.

All,

I am receiving error 17122.  I am probably going to reconfigure the server
to dynamically allocate memory, but can somebody answer the following
question?  Why is SQL Server attempting to set the working set size to
519104KB, when the configuration is as follows (basically, fixed memory at
350MB)?

SQL Server 7.0 SP2
512MB

Set working set size = 1
Min Server Memory = 350MB
Max Server Memory = 350MB

I have searched everywhere, and I have check the SP3 fixlist, and have
failed to find an explanation.  Any help would be appreciated.

Thanks,
Gerard

2. - Financials Applications Programmer/Analyst: Purchasing - Portland, Oregon jw008921

3. initdata: Warning: Could not set working set size to 1038848 KB.

4. How many users ?

5. 17122 :initdata: Warning: Could not set working set size to 519104 KB.

6. Opportunity with Fortune 500 Co. Manager, Information Systems

7. Eventlog Mesg 17122 : initdata: Warning: Could not set working set size to 519104 KB

8. initdata error 17122 & PAGE_FAULT

9. SQL Error Could not set working set size to ... KB

10. Setting Working Set Size on SQL 7 under Windows 2000

11. UPDATE / Multiple SET not working - fields being set to NULL

12. SQL 7.0 - Working set size ERROR