What collations does sys.fn_get_audit_file_v2 support

Question

What collations does sys.fn_get_audit_file_v2 support

Jakob Hommelhoff 0

When calling the function on a server with default collation Latin1_General_100_CI_AS_SC_UTF8 I get this error:

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_100_CI_AS_SC_UTF8" in the equal to operation.

Using collate with the various input paramteres does not seem to have an effect?
Is the function limited to databases with SQL_Latin1_General_CP1_CI_AS as default collation?

Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-09-03T21:33:04.6233333+00:00
What environment are you running this in? Since you talk about a server collation and this particular function, I would guess Azure Managed Instance, since the function is not available in SQL 2022.

What exact statement did you run?

For what it's worth, I was able to run this on SQL 2025 RC0:

SELECT * FROM sys.fn_get_audit_file_v2 ('C:\temp\Audit-20250903-232716*.sqlaudit', DEFAULT, DEFAULT, DEFAULT, DEFAULT)

My server collation is Finnish_Swedish_100_CS_AS_SC_UTF8.
Jakob Hommelhoff 0 Reputation points

2025-09-08T08:48:48.69+00:00

Hi Erland - It is an Azure SQL server (compatability level: SQL Server 2019 (150)).

Running your query I get the same error - here it is in full:

Msg 468, Level 16, State 9, Procedure fn_get_audit_file_v2, Line 66 [Batch Start Line 0]

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_100_CI_AS_SC_UTF8" in the equal to operation.

Msg 4413, Level 16, State 1, Line 561

Could not use view or function 'sys.fn_get_audit_file_v2' because of binding errors.
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-09-08T21:12:29.1433333+00:00
If you ran my query as I posted it on Azure SQL Database, you would get a different error. But I assume that you replaced the filepath with a URL to blob store? On the other hand, what you said the server collation does not match Azure SQL Database, so I still have a sense of uncertainty of your envrionment.

Since setting up an audit that writes to blob store requires a bit of effort, I would like some clarification before I try. Can you post the result of these two queries:

SELECT serverproperty('Collation'), databasepropertyex(db_name(), 'Collation'), serverproperty('EngineEdition') SELECT @@version
Jakob Hommelhoff 0 Reputation points

2025-10-13T08:53:49.2933333+00:00

Hi Erland

Sorry for the late reply here (I have been ill).

I would assume the error to be the same, as the binding error would pre-empt actual execution of the stp where the invalid path would surface, but I could be wrong... :-)

The result of the queries:

server_collation: SQL_Latin1_General_CP1_CI_AS database_collation: Latin1_General_100_CI_AS_SC_UTF8 engine_edition: 5 version: Microsoft SQL Azure (RTM) - 12.0.2000.8 Aug 6 2025 10:20:12 Copyright (C) 2025 Microsoft Corporation

Thank you - I appreciate your help!
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-10-13T21:56:06.3866667+00:00

Sorry! Apparently, I ran the query in master, where there is no conflict, so it could validate the file path. Yes, the collation conflict happens already on compilation of the query.

I would say that this quite a bug. You can only use the function on database level if your collation is SQL_Latin1_General_CP1_CI_AS which is not a very good collation in my opinion. For now, your only option is to run the query from master or view the audit logs from the portal.
Nithin Krishna Madadi 0 Reputation points Microsoft External Staff Moderator

2025-10-27T09:18:41.78+00:00

Hi Jakob Hommelhoff ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Jakob Hommelhoff 0 Reputation points

2025-10-27T10:28:34.69+00:00

Hi Nithin

I reviewed the information, an dit was useful. The context I am operating withind does not allow me to run the query in the master database, but I made a note of this being a known issue which is useful. Do you know how I can find out if or when this issue will fixed?

Kind regards, Jakob Hommelhoff
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-10-27T21:58:12.1666667+00:00
Do you know how I can find out if or when this issue will fixed?

One way to found is to start every day by running this query:

SELECT * FROM sys.fn_get_audit_file_v2 ('C:\temp\Audit-20250903-232716*.sqlaudit', DEFAULT, DEFAULT, DEFAULT, DEFAULT)

It you get this error message, you know that the issue has been fixed:

Msg 40538, Level 16, State 3, Line 1 A valid URL beginning with 'https://' is required as value for any filepath specified.

In fact this is the error I get when I run in one of my Azure databases, which suggests that the bug has been fixed. I can also confirm this when I run

EXEC sp_helptext 'sys.fn_get_audit_file_v2'

Where I can see the required fix.

My database is in West Europe. If you still get the collation error, it could be because the fix has not been rolled out in your region.
Nithin Krishna Madadi 0 Reputation points Microsoft External Staff Moderator

2025-10-31T12:08:49.26+00:00

Hi Jakob Hommelhoff ,

May I check if this issue has been resolved by the suggestion provided by Erland Sommarskog? If not, Please feel free to contact us if you have any further questions.

Thank you

1 answer

Your answer

Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-09-03T21:33:04.6233333+00:00

What environment are you running this in? Since you talk about a server collation and this particular function, I would guess Azure Managed Instance, since the function is not available in SQL 2022.

What exact statement did you run?

For what it's worth, I was able to run this on SQL 2025 RC0:

SELECT * FROM sys.fn_get_audit_file_v2 ('C:\temp\Audit-20250903-232716*.sqlaudit', DEFAULT, DEFAULT, DEFAULT, DEFAULT)

My server collation is Finnish_Swedish_100_CS_AS_SC_UTF8.
Jakob Hommelhoff 0 Reputation points

2025-09-08T08:48:48.69+00:00

Hi Erland - It is an Azure SQL server (compatability level: SQL Server 2019 (150)).

Running your query I get the same error - here it is in full:

Msg 468, Level 16, State 9, Procedure fn_get_audit_file_v2, Line 66 [Batch Start Line 0]

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_100_CI_AS_SC_UTF8" in the equal to operation.

Msg 4413, Level 16, State 1, Line 561

Could not use view or function 'sys.fn_get_audit_file_v2' because of binding errors.
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-09-08T21:12:29.1433333+00:00

If you ran my query as I posted it on Azure SQL Database, you would get a different error. But I assume that you replaced the filepath with a URL to blob store? On the other hand, what you said the server collation does not match Azure SQL Database, so I still have a sense of uncertainty of your envrionment.

Since setting up an audit that writes to blob store requires a bit of effort, I would like some clarification before I try. Can you post the result of these two queries:

SELECT serverproperty('Collation'), databasepropertyex(db_name(), 'Collation'), serverproperty('EngineEdition') SELECT @@version
Jakob Hommelhoff 0 Reputation points

2025-10-13T08:53:49.2933333+00:00

Hi Erland

Sorry for the late reply here (I have been ill).

I would assume the error to be the same, as the binding error would pre-empt actual execution of the stp where the invalid path would surface, but I could be wrong... :-)

The result of the queries:

server_collation: SQL_Latin1_General_CP1_CI_AS database_collation: Latin1_General_100_CI_AS_SC_UTF8 engine_edition: 5 version: Microsoft SQL Azure (RTM) - 12.0.2000.8 Aug 6 2025 10:20:12 Copyright (C) 2025 Microsoft Corporation

Thank you - I appreciate your help!
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-10-13T21:56:06.3866667+00:00

Sorry! Apparently, I ran the query in master, where there is no conflict, so it could validate the file path. Yes, the collation conflict happens already on compilation of the query.

I would say that this quite a bug. You can only use the function on database level if your collation is SQL_Latin1_General_CP1_CI_AS which is not a very good collation in my opinion. For now, your only option is to run the query from master or view the audit logs from the portal.
Nithin Krishna Madadi 0 Reputation points Microsoft External Staff Moderator

2025-10-27T09:18:41.78+00:00

Hi Jakob Hommelhoff ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Jakob Hommelhoff 0 Reputation points

2025-10-27T10:28:34.69+00:00

Hi Nithin

I reviewed the information, an dit was useful. The context I am operating withind does not allow me to run the query in the master database, but I made a note of this being a known issue which is useful. Do you know how I can find out if or when this issue will fixed?

Kind regards, Jakob Hommelhoff
Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator

2025-10-27T21:58:12.1666667+00:00

Do you know how I can find out if or when this issue will fixed?

One way to found is to start every day by running this query:

SELECT * FROM sys.fn_get_audit_file_v2 ('C:\temp\Audit-20250903-232716*.sqlaudit', DEFAULT, DEFAULT, DEFAULT, DEFAULT)

It you get this error message, you know that the issue has been fixed:

Msg 40538, Level 16, State 3, Line 1 A valid URL beginning with 'https://' is required as value for any filepath specified.

In fact this is the error I get when I run in one of my Azure databases, which suggests that the bug has been fixed. I can also confirm this when I run

EXEC sp_helptext 'sys.fn_get_audit_file_v2'

Where I can see the required fix.

My database is in West Europe. If you still get the collation error, it could be because the fix has not been rolled out in your region.
Nithin Krishna Madadi 0 Reputation points Microsoft External Staff Moderator

2025-10-31T12:08:49.26+00:00

Hi Jakob Hommelhoff ,

May I check if this issue has been resolved by the suggestion provided by Erland Sommarskog? If not, Please feel free to contact us if you have any further questions.

Thank you

Answer 1

Sravani Saluru 5 Microsoft Employee

This is a known issue, and a fix is currently being deployed. In the meantime, you can use the master database to query audit logs as a workaround.

Jakob Hommelhoff 0 Reputation points

2025-10-15T06:59:26.39+00:00

Ok, Thank you both.

Share via

What collations does sys.fn_get_audit_file_v2 support

1 answer

Your answer