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

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

Post by Harald the Vikin » Sat, 05 Feb 2000 04:00:00



Hi !
Somebody knows of what this error message from ms sql 7.0 kernel is and how
to correct it ?

regards
harald

 
 
 

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

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

2. NYC - Sybase DBA - High Profile Group - 4 Weeks Vacation

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

4. Need help of delete

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

6. Returning a recordset based on a list view entry

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

8. initdata error 17122 & PAGE_FAULT

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

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

11. Mesg 17130: initdata: no memory for kernel locks

12. Setting not Null field to ""(empty string) does not work with CRecordset