SQL Server Support Blog

Options
142
Dharshana on Mar 18 2024 08:56 PM
2,841
moematsuo on Feb 15 2024 04:25 PM
1,519
JamesFerebee on Nov 20 2023 09:45 AM
2,449
moematsuo on Sep 04 2023 01:47 AM
2,508
IdaliaL on Aug 16 2023 11:14 AM
16.7K
mizuhokitao on May 08 2023 02:32 AM
18.2K
Dharshana on Apr 23 2023 02:29 PM
1,915
Katsuya_Ito on Apr 07 2023 06:08 AM
16.9K
JuanPabloSalg on Mar 29 2023 08:11 AM
5,240
Katsuya_Ito on Mar 16 2023 11:03 PM
13.3K
Joseph Pilov on Feb 27 2023 03:02 PM
3,800
NathanMSFT on Feb 27 2023 09:13 AM
4,763
Joseph Pilov on Dec 13 2022 12:31 PM
6,175
prakashkc on Dec 07 2022 07:40 PM
5,837
Krishnakumar_Rukmangathan on Nov 14 2022 01:56 AM
5,393
Liwei on Nov 01 2022 11:16 AM
4,450
Krishnakumar_Rukmangathan on Jul 12 2022 04:47 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