COMPRESS is not a recognized built-in function name [closed]
According to the documentation given here, I am tried to use COMPRESS
function to compress VARCHAR(MAX) column data before storing in SQL server, but its not working
SELECT COMPRESS ('Satishakumar');
The error I received in SSMS is
Msg 195, Level 15, State 10, Line 1 'COMPRESS' is not a recognized
built-in function name.
The version details of SQL server are
Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 (X64) Jan 5 2018 22:11:56 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: )

closed as off-topic by Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon Jan 2 at 20:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
According to the documentation given here, I am tried to use COMPRESS
function to compress VARCHAR(MAX) column data before storing in SQL server, but its not working
SELECT COMPRESS ('Satishakumar');
The error I received in SSMS is
Msg 195, Level 15, State 10, Line 1 'COMPRESS' is not a recognized
built-in function name.
The version details of SQL server are
Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 (X64) Jan 5 2018 22:11:56 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: )

closed as off-topic by Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon Jan 2 at 20:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon
If this question can be reworded to fit the rules in the help center, please edit the question.
7
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57
add a comment |
According to the documentation given here, I am tried to use COMPRESS
function to compress VARCHAR(MAX) column data before storing in SQL server, but its not working
SELECT COMPRESS ('Satishakumar');
The error I received in SSMS is
Msg 195, Level 15, State 10, Line 1 'COMPRESS' is not a recognized
built-in function name.
The version details of SQL server are
Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 (X64) Jan 5 2018 22:11:56 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: )

According to the documentation given here, I am tried to use COMPRESS
function to compress VARCHAR(MAX) column data before storing in SQL server, but its not working
SELECT COMPRESS ('Satishakumar');
The error I received in SSMS is
Msg 195, Level 15, State 10, Line 1 'COMPRESS' is not a recognized
built-in function name.
The version details of SQL server are
Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 (X64) Jan 5 2018 22:11:56 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: )


edited Jan 2 at 20:08


scsimon
22.3k51637
22.3k51637
asked Jan 2 at 10:55


Satishakumar AwatiSatishakumar Awati
2,09011528
2,09011528
closed as off-topic by Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon Jan 2 at 20:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon Jan 2 at 20:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – Larnu, HoneyBadger, Squirrel, Martin Smith, scsimon
If this question can be reworded to fit the rules in the help center, please edit the question.
7
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57
add a comment |
7
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57
7
7
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57
add a comment |
1 Answer
1
active
oldest
votes
As you can see from the docs from the link you gave, this function is available in SQL Server starting with version 2016, while you are using version 2012.
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As you can see from the docs from the link you gave, this function is available in SQL Server starting with version 2016, while you are using version 2012.
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
add a comment |
As you can see from the docs from the link you gave, this function is available in SQL Server starting with version 2016, while you are using version 2012.
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
add a comment |
As you can see from the docs from the link you gave, this function is available in SQL Server starting with version 2016, while you are using version 2012.
As you can see from the docs from the link you gave, this function is available in SQL Server starting with version 2016, while you are using version 2012.
answered Jan 2 at 10:58


Andrey NikolovAndrey Nikolov
4,3233922
4,3233922
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
add a comment |
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
Thanks, I missed that part in the link, our DB version is 2012.
– Satishakumar Awati
Jan 4 at 11:06
add a comment |
7
As per the document COMPRESS (Transact-SQL) that you linked to as well: "APPLIES TO: SQL Server (starting with 2016)". Emphasis mine. You're using 2012.
– Larnu
Jan 2 at 10:57