Comments (0)

Symptoms
When a database is in the full recovery model, and you try to back up the transaction log files with either a NO_LOG or TRUNCATE_ONLY option, the following message is logged in the Application Log of the Event Viewer:

Event Type: Error Event
Source: MSSQLSERVER
Event Category: 6
Event ID: 17055
User: <User name>
Computer: <Computer name>
Description:
18278 :
Database log truncated: Database: <Database name>.
Note The same message is also logged in the SQL Server 2000 error log.
If you use SQL Server 2005, the following message is logged in the Application event log:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 8309
Description:
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.For more information, see Help and Support Center at http://support.microsoft.com.
Resolution
This warning message may be logged because the NO_LOG and TRUNCATE_ONLY options of the BACKUP statement truncate the transaction log files, and you might need transaction logs for the full recovery of the database.

Comments (0)

Symptoms
This article describes the following about this hotfix release: The issues that are fixed by this hotfix packageThe prerequisites for applying this hotfix packageWhether you must restart the computer after you apply this hotfix packageWhether this hotfix package is replaced by any other hotfix packageWhether you must make any registry changes after you apply this hotfix packageThe files that are contained in this hotfix package
Resolution
In Microsoft SQL Server 2000, the synchronization process may take a long time when you synchronize merge replication publications. You may experience this problem if you have created many generations of the publication since the last time that you synchronized the merge replications.
For a list of all publicly released SQL Server 2000 post-service pack hotfixes, see the following article in the Microsoft Knowledge Base:
894905?(http://support.microsoft.com/kb/894905/) Cumulative list of the hotfixes that are available for SQL Server 2000 SP4

Comments (0)

Symptoms
This article describes the steps that you must follow when the transaction logs expand to an unacceptable limit. The expansion of the transaction logs can make your Microsoft SQL Server database unusable. Thisarticle also provides the options that you can use to stop the transaction logs from growing unexpectedly.

Resolution
In SQL Server 2000 and in SQL Server 2005, each database contains at least one data file and one transaction log file. SQL Server stores the data physically in the data file. The transaction log file stores the details of all the modifications that you perform on your SQL Server database and the details of the transactions that performed each modification. Because thetransactional integrity is considered a fundamental and intrinsic characteristic of SQL Server, logging the details of the transactions cannot be turned off in SQL Server.
The transaction log file is logically divided into smaller segments that are referred to as virtual log files.In SQL Server 2000, you can configure the transaction log file to expand as needed. The transaction log expansion can be governed by the user or can be configured to use all the available disk space. Any modifications that SQL Server makes to the size of the transaction log file, such as truncating the transaction log files or growing the transaction log files, are performed in units of virtual log files.
If the transaction log file that corresponds to a SQL Server database is filled and if you have set the option for the transaction log files to grow automatically, the transaction log file grows in units of virtual log files. Sometimes, the transaction log filemay become very large and you may run out of disk space. When a transaction log file grows until the log file uses all the available disk space and cannot expand any more, you can no longer perform any data modification operations on your database. Additionally, SQL Server may mark your database assuspect because of the lack of space for the transaction log expansion.
For additional information about the scenarios that may cause the transaction log file to grow unexpectedly, click the following article number to view the article in the Microsoft Knowledge Base:
317375?(http://support.microsoft.com/kb/317375/) Transaction log grows unexpectedly or becomes full on SQL Server
Reduce the size of the transaction logsTo recover from a situation where the transaction logs grow to an unacceptable limit, you must reduce the size of the transaction logs. To do this, you must truncate the inactive transactions in your transaction log and shrink the transaction log file.
Note The transaction logs are very important to maintain the transactional integrity of the database. Therefore, you must not delete the transaction log files even after you make a backup of your database and the transaction logs.
Truncate the inactive transactions in your transaction log When the transaction logs grow to an unacceptable limit, you must immediately back up your transaction log file. While thebackup of your transaction log files is created, SQL Server automatically truncates the inactive part of the transaction log. The inactive part of the transaction log file contains the completed transactions, and therefore, the transaction log file is no longer used by SQL Server during the recovery process. SQL Server reuses this truncated, inactive space in the transaction log instead of permitting the transaction log to continue to grow and to use more space.
For additional information about the issues that you must consider when you make a backup of the transaction logs and the issues that you must consider when you restore the transaction log backups, visit the following topics in SQL Server Books Online:Transaction log backupsTransaction log backup and restoreYou can also delete the inactive transactions from a transaction log file by using the Truncate method. For additional information about truncating the transaction logs, see the “Truncating the transaction log” topic in SQL Server Books Online.
Important After you manually truncate the transaction log files, you must create a full database backup before you create a transaction log backup.
For additional information about the issues that may occur when you truncate the transaction log files, click the following article number to view the article in the Microsoft Knowledge Base:
62866?(http://support.microsoft.com/kb/62866/) Reasons why SQL transaction log is not being truncatedShrink the transaction log file The backup operation or the Truncate method does not reduce the log file size. To reduce the size of the transaction log file, you must shrink the transaction log file. To shrink a transaction log file to the requested size and to remove the unused pages, you must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE Transact-SQL statement can only shrink the inactive partinside the log file.
Note The DBCC SHRINKFILE Transact-SQL statement cannot truncate the log and shrink the used space inside the log file on its own.
For more information about shrinking the transaction log files, see the following topics in SQL Server Books Online:Shrinking the transaction logDBCC SHRINKFILEFor additional information about how to shrink the transaction log files in SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:
272318?(http://support.microsoft.com/kb/272318/) Shrinking the transaction log in SQL Server 2000 with DBCC SHRINKFILEFor additional information about the problems that may occur when you shrink the transaction log files, click the following article numbers to view the articles in the Microsoft Knowledge Base:
814574?(http://support.microsoft.com/kb/814574/) PRB: Error message: “Cannot shrink log file …” occurs when you shrink the transaction log file
324432?(http://support.microsoft.com/kb/324432/) PRB: DBCC SHRINKFILE and SHRINKDATABASE commands may not work because of sparsely populated text, ntext, or image columns
Prevent thetransaction log files from growing unexpectedlyTo prevent thetransaction log files from growing unexpectedly, consider using one of the following methods:Set the size of the transaction log files to a large value to avoid the automatic expansion of the transaction log files. Configure the automatic expansion of transaction log files by using memory units instead of a percentage after you thoroughly evaluate the optimum memory size.
For additional information about the issues to consider when you configure the autogrow option, click the following article number to view the article in the Microsoft Knowledge Base:
315512?(http://support.microsoft.com/kb/315512/) Considerations for autogrow and autoshrink configurationChange the recovery model. If a disaster or data corruption occurs, you must recover your database so that the data consistency and the transactional integrity of the database are maintained. Based on how critical the data in your database is, you can use one of the following recovery models to determine how your data is backed up and what your exposure to the data loss is:Simple recovery modelFull recovery modelBulk-logged recovery modelBy using the simple recovery model, you can recover your database to themost recent backup of your database. By using the full recovery model or the bulk-logged recovery model, you can recover your database to the point when the failure occurred by restoring your database with the transaction log file backups.
By default, in SQL Server 2000 and in SQL Server 2005, the recovery model for a SQL Server database is set to the Full recovery model. With the full recovery model, regular backups of the transaction log are used to prevent the transaction log file size from growing out of proportion to the database size. However, if the regular backups of the transaction log are not performed, the transaction log file grows to fill the disk, and you may not be able to perform any data modification operations on the SQL Server database.
You canchange the recovery model from full to simple if you do not want to use the transaction log files during a disaster recovery operation.Back up the transaction log files regularly to delete the inactive transactions in your transaction log.Design the transactions to be small.Make sure that no uncommitted transactions continue to run for an indefinite time.Schedule the Update Statistics option to occur daily.To defragment the indexes to benefit the workload performance in your production environment, use the DBCC INDEXDEFRAG Transact-SQL statement instead of the DBCC DBREINDEX Transact-SQL statement. If you run the DBCC DBREINDEX statement, the transaction log may expand significantly when your SQL Server database is in Full recovery mode. Additionally, the DBCC INDEXDEGRAG statement does not hold the locks for a long time, unlike the DBCC DBREINDEX statement.
For additional information about defragmenting the indexes in SQL Server 2000, see the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc966523.aspx(http://technet.microsoft.com/en-us/library/cc966523.aspx) If you must run the DBCC DBREINDEX statement as a job that is a part of the database maintenance plan, you must break up the job into multiple jobs. Additionally, you must take the frequent backups for the transaction logs between the execution of thejobs.

Comments (0)

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by this hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changes The files that are contained in the hotfix package
Resolution
When an encrypted logon packet is received in two network reads, you may receive an exception access violation in Microsoft SQL Server 2000. This problem occurs when the following conditions are true: The Ssnetlib.dll file is build 818 or a later build.Encryption is supported, and both the client computer and the server computer have Secure Sockets Layer (SSL) certificates.The client computer does not force encryption during the connection. The client computer forces encryption only when the client computer logs on.After the logon packet is encrypted, the encrypted logon packet is large enough to be broken up by the network.For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
810185?(http://support.microsoft.com/kb/810185/) SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a