In contrast to example B, this example base64 string was encoded using RFC 4648 Table 2 (url_safe), but can be decoded the same way as example B.
BASE64_DECODE varchar url_safe base64 string Note the string contains URL-unsafe characters = and /. In the following example, the string is base64 decoded. In the following example, the base64 encoded string is decoded back into varbinary. If the input contains more than two padding characters or padding characters followed by extra valid input the function returns error Msg 9803, State 23.If the data has valid characters, but incorrectly formatted, the function returns error Msg 9803, State 21.When the input contains characters not contained within the standard or URL-safe alphabets specified by RFC 4648 the function returns error "Msg 9803, Level 16, State 20, Line 15, Invalid data for type "Base64Decode"".This function ignores whitespace characters: \n, \r, \t, and. The URL-safe alphabet specified within RFC 4648 Table 2 is also accepted. The encoded string's alphabet must be that of RFC 4648 Table 1 and may include padding, though padding is not required. If the input expression is null, the output is null.Varbinary(max) if the input is varchar(max).Transact-SQL syntax conventions Syntax BASE64_DECODE(expression)Īn expression of type varchar (n | max). Applies to: SQL Endpoint and Warehouse in Microsoft FabricīASE64_DECODE converts a base64 encoded varchar into the corresponding varbinary.
0 kommentar(er)
