This request appears to be obsolete as of changes made on Jan 29, 2018 by @Evdlaar . As you can see in that particular commit, line 147:

SUBSTRING( [master].[sys].[fn_repl_hash_binary]( CONVERT( varbinary (MAX), [n].[query]( '.' ))), 1, 32 ),

was changed to:

(qs.query_hash+qs.query_plan_hash),

So, if OQS does not support SQL Server 2005, then it isn't due to the absence of fn_repl_hash_binary. If it was, then an easy solution would be to check for the SQL Server version, and if 2005, then use a different function. For example, there is the SQL# library (which I created) that contains a function, Util_HashBinary, that does the same thing (well, Util_HashBinary actually allows you to specify any of the hash algorithms available in .NET, not just MD5 which is all that fn_repl_hash_binary does). And yes, it is in the Free version. People wanting that functionality in SQL Server 2005 (or to do HASHBYTES without the 8000 byte limit on versions prior to SQL Server 2016), might have no issues with using SQLCLR. After all, it is available on all platforms except Azure SQL Database (even if SAFE assemblies only on Linux and Azure Managed Instances).

I realize that it is preferred (for this project) to not use SQLCLR, but it's the same solution that Microsoft came up with, given that fn_repl_hash_binary is, in fact, SQLCLR:

SELECT [type_desc] FROM sys.all_objects WHERE [name] = N'fn_repl_hash_binary';
-- CLR_SCALAR_FUNCTION

fn_repl_hash_binary is not available in SQL 2005 #16

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions