You might be familiar with the sparse file problem that Bob Dorr has blogged about in the past. http://blogs.msdn.com/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx . We wanted to update you with the work we have been involved in the past few months. There are several fixes that we plan to release or already released to address the different aspects of this problem. The list provided below summarizes all of the documentation and fix available for you regarding this problem. We will keep this list updated as we come across more information or changes.
|
Product & Version
|
Release Vehicle
|
KB Article #
|
Title
|
Description of problem and fix
|
|
Windows Server 2003, 2008
Windows Vista
|
|
|
A heavily fragmented file in an NTFS volume may not grow beyond a certain size
|
The article explains the root cause of this problem and the technical details of the limitation.
|
|
|
|
|
|
|
|
Windows Server 2008 RTM
Windows Vista SP1
|
Regular QFE
|
|
Error status message from the ntfs.sys driver when some applications update very large files in Windows Server 2008 or in Windows Vista systems: "0xc0000427 STATUS_FILE_SYSTEM_LIMITATION"
|
Windows Vista RTM and Win 20008 RTM had a problem that reduces the attribute limits to a much smaller number than what Windows 2003 had. This hotfix increases the attribute limitation in Windows 2008 and Vista OS and brings it on par with the Windows 2003 limit. If you are running Windows Vista or Windows 2008 and you encounter this problem, the first step is to apply this fix.
|
|
|
|
|
|
|
|
SQL Server 2005
|
SP2 CU12
|
|
FIX: The SQL Server service stops when you run one of the DBCC CHECK commands on a SQL Server 2005 database or when you create a database snapshot for a SQL Server 2005 database
|
When running DBCC CHECKDB command and if you run into this limitation, you could encounter Out Of Memory errors in SQL Server. This is because the children threads associated with the DBCC CHECKDB command starts accumulating error messages relating to the internal snapshot failures and quickly consumes all the available memory configured for the SQL Server instance. Under such conditions, you will notice that MEMORYCLERK_SQLGENERAL consuming a big portion of the SQL Server memory. Applying this fix will make sure that such memory consumption will not happen.
|
|
SQL Server 2005
|
SP3 CU1
|
|||
|
SQL Server 2008
|
RTM
|
|||
|
|
|
|
|
Microsoft
