Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

Symptoms

Consider the following scenario:

  • You use SQL Server Audit in Microsoft SQL Server 2008 to audit an instance of the SQL Server Database Engine or of a single database.

  • The instance of SQL Server 2008 is running on an IA-64 computer.

  • The audit target is the Windows Security log or the Windows Application log.

In this scenario, corrupted codes are recorded in the Windows Security log or in the Windows Application log. For example, the following information is recorded in the log:

Audit event: event_time: DateTime

sequence_number:1

action_id:SL

succeeded:true

permission_bitmask:1

is_column_permission:true

session_id:53

server_principal_id:269

database_principal_id:1

target_server_principal_id:0

target_database_principal_id:0

object_id:2121058592

class_type:U

session_server_principal_name:⁀聒

server_principal_name:⁀聒

server_principal_sid:010500000000000515000000271a6c07352f372aad20fa5b61470400

database_principal_name:⁀聒

target_server_principal_name:

target_server_principal_sid:

target_database_principal_name:

server_instance_name:⁀聒

database_name:⁀聒

schema_name:⁀聒

object_name:⁀聒

statement:⁀聒

Notes

  • This issue does not occur when the audit target is a file.

  • This issue does not occur when the instance of SQL Server 2008 is running on an x86 or x64 computer.

Resolution

Cumulative update information

Cumulative update package 6 for SQL Server 2008 SP 3

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 SP3, click the following article number to view the article in the Microsoft Knowledge Base:

2715953 Cumulative update package 6 for SQL Server 2008 SP3Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP3 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2629969 SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For more information about SQL Server Audit, go to the following MSDN website:

General information about SQL Server AuditFor more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 Naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×