Does anyone have any more details on this KB? MS states this happens when you set max memory to a "large value". A hard cutoff here would be more helpful. Also, on the versions list in the KB, SQL2008 Std is not listed, although SQL2005
Std edition is listed. Any help here would be great. Thanks.
View Complete Post