mibuso.com
Home› SQL General
Options

SQL 2005 on 64bits died....no more odbc connections

BGIBGI Member Posts: 176
edited 2008-04-30 in SQL General
GOt this at a customer: no more connection possible, reboot necessary of sql server.....

Got into errorlogs : Lazywriter: warning no free buffers found
Got onto internet: http://forums.microsoft.com/MSDN/ShowPo ... 8&SiteID=1

So server is 64bit with 64bit sql with 4gb internal mem.
No awe used....
If i understand correctly the msdn post, i should limit the amount of memory for sql to 3gb...
I suppose i have to setup server memeory options to use awe to allocate memory and setup miniùm 0 and maximum 3000

Or is there someone with other ideas about this problem...
Rgds
Benny Giebens

Comments

  • Options
    NobodyNobody Member Posts: 93
    I would set the "Max Server Memory" to 3 GB, but I would not turn on AWE in a x64 env. There is just no need for it and AWE intialization requires memory that you would just be throwing away with no benefit.
  • Options
    BGIBGI Member Posts: 176
    If you do not enable awe, will the max memory setting be activated. Like its on the screen my idea is is that min and max only have effect with awe checked or am i wrong?
    Rgds
    Benny Giebens
  • Options
    garakgarak Member Posts: 3,263
    Take a look here
    Do you make it right, it works too!
  • Options
    NobodyNobody Member Posts: 93
    Actually No, with AWE enabled SQL will just grab what ever the MAX sever memory is in SQL on start-up, it will not be dynamic.
Sign In or Register to comment.