�α��

Select the product you need help with

FIX: Error message when you restore a transaction log for a database by using the STANDBY option in SQL Server 2005: "The transaction log for database '<DatabaseName>' is full"

Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.

�� Ȯ�� | ��

��

When you restore a transaction log for a database by using the STANDBY option in Microsoft SQL Server 2005, you receive the following error message:

Msg 9002, Level 17, State 4, Line 1
The transaction log for database 'DatabaseName' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

If you restore the transaction log by using the RECOVERY option or the NORECOVERY option instead of by using the STANDBY option, the restore operation is completed successfully.

�� | �ǵ��

�ذ� ��

Cumulative update information

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.

The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

956854

(http://support.microsoft.com/kb/956854/LN/ )

Cumulative update package 10 for SQL Server 2005 Service Pack 2

Note 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 2005 fix release. Microsoft recommends 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:

937137

(http://support.microsoft.com/kb/937137/LN/ )

The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.

The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

959195

(http://support.microsoft.com/kb/959195/LN/ )

Cumulative update package 1 for SQL Server 2005 Service Pack 3

�� 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 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. �߰� �� ȣ�� Ŭ��Ͽ� Microsoft �� ڷῡ�� Ȯ��Ͻʽÿ�:

960598

(http://support.microsoft.com/kb/960598/LN/ )

The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

�� | �ǵ��

��

Microsoft�� "�� ǰ�� ˴ϴ�." �� Microsoft ��ǰ�� Ȯ��߽��ϴ�.

�� | �ǵ��

�ذ� ��

To work around this issue, restore the transaction log by using the NORECOVERY option, and then use the STANDBY option to recover the database for read-only access for the next transaction log.

�� | �ǵ��

�߰� ��

This issue is only related to the restore functionality. This issue does not affect the reliability or the viability of the existing transaction log backup files. This issue only occurs when the transaction log of a source database is close to saturation. This issue only occurs in very rare conditions.For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

956854

(http://support.microsoft.com/kb/956854/LN/ )

Cumulative update package 10 for SQL Server 2005 Service Pack 2

�� | �ǵ��

��

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

937137

(http://support.microsoft.com/kb/937137/LN/ )

List of the builds that are available after SQL Server 2005 Service Pack 2 was released

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

935897

(http://support.microsoft.com/kb/935897/LN/ )

An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

913089

(http://support.microsoft.com/kb/913089/LN/ )

How to obtain the latest service pack for SQL Server 2005

For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?LinkId=71711

(http://go.microsoft.com/fwlink/?LinkId=71711)

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

(http://support.microsoft.com/kb/822499/LN/ )

New 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

(http://support.microsoft.com/kb/824684/LN/ )

Microsoft ��Ʈ�� Ʈ�� ϴ� �� Ǵ� ǥ��  ��

�� | �ǵ��

�Ӽ�

�� ڷ�: 958554 - �� : 2008�� 12�� 20�� - ��: 4.0

�� ǰ�� ˴ϴ�.

Microsoft SQL Server 2005 Standard Edition
Microsoft SQL Server 2005 Developer Edition
Microsoft SQL Server 2005 Enterprise Edition
Microsoft SQL Server 2005 Standard X64 Edition
Microsoft SQL Server 2005 Standard Edition for Itanium Based Systems
Microsoft SQL Server 2005 Enterprise X64 Edition
Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
Microsoft SQL Server 2005 Workgroup Edition

kbmt kbsql2005engine kbfix kbqfe kbexpertiseadvanced KB958554 KbMtko

��

�߿�: �� ƴ϶� Microsoft �� Ʈ�� Դϴ�. Microsoft�� ϹǷ� Microsoft �� ڷῡ �ִ� �� ѱ۷� �� ֽ��ϴ�. �׷�� ׻� �Ϻ�� ƴմϴ�. �� ġ �ܱ�� ѱ�� Ǽ�� ϴ� ��ó�� , �� Ǵ� �� ֽ��ϴ�. Microsoft�� Ǵ� Microsoft �� ̷�� ν� �߻��ϴ� �� Ȯ��, �� Ǵ� ��ؿ� �� å�� ʽ��ϴ�. Microsoft�� ̷�� ذ��ϱ� �� Ʈ�� �� Ʈ�ϰ� �ֽ��ϴ�.

�� .

�� | �ǵ��

�ǵ��

��

�� ڷ� ��

United States (English)

Select the product you need help with

FIX: Error message when you restore a transaction log for a database by using the STANDBY option in SQL Server 2005: "The transaction log for database '<DatabaseName>' is full"

Cumulative update information

SQL Server 2005 Service Pack 2

SQL Server 2005 Service Pack 3

�� ������ ������ ������ ��ǰ�� ����˴ϴ�.

Ű����:?

��� �ڷ� ����

�� ǰ�� ˴ϴ�.

Ű��:?

�� ڷ� ��