SQL Server Support Blog

Options
8,385
SaniyaSamreen on Aug 31 2021 04:06 AM
2,381
Liwei on Jun 23 2021 07:24 AM
3,647
Liwei on May 31 2021 09:00 AM
2,090
Liwei on May 26 2021 07:29 PM
7,427
dineu on Mar 26 2021 07:47 AM
37.3K
Joseph Pilov on Jan 27 2021 12:58 PM
4,328
FranciscoBertao on Jan 27 2021 03:52 AM
14.2K
Bob_Cai on Jan 24 2021 01:45 AM
1,810
HeminMSFT on Nov 11 2020 03:04 PM
5,863
UjjwalPatel on Sep 24 2020 03:54 AM

Latest Comments

First SQL Query as text for the next poor fellow who finds this post :D SELECT spm.class_desc, spm.permission_name, spm.state_desc, spr.name, spr.type_desc, spr.is_disabled, ep.name AS EndpointName, ep.protocol_desc AS EndPointDescription, ep.state_desc AS EndPointState, ep.type_desc AS EndpointType...
0 Likes
This is a Windows defect.If memory allocation calls are going to fail due to a lack of resident available memory then Windows should be setting the memory pressure state so that applications can voluntarily release memory rather than just crashing.
0 Likes
I am here because I got this error and hoped I would find a clue, but no dice. In your case it might be explained by nvarchar(max), however I got it on a postgreSQL boolean column which is bit on SQL server. Makes no sense. Discard this. I found my solution, naturally outside Microsoft Tech Communit...
0 Likes
Also in some case this error maybe occurre because of "Common Criteria Compliance" feature was enabled on the server.To resolve this error you should:1-Disable "Common Criteria Compliance":sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'common criteria compliance enabled', ...
0 Likes