Symptoms
When you run the Index Tuning Wizard, this error message may occur:
Server: Msg 3628, Level 16, State 1, Line 2
A floating point exception occurred in the user process. Current transaction is canceled.
Resolution
When a double was out of range from an underflow or overflow, the Index Tuning Wizard incorrectly converted the number into the maximum or minimum float value.
Symptoms
If index maintenance operations such as DROP, CREATE, or REBUILD statements occur at the time of a database or transaction log backup, subsequent attempts to load the backup may fail with the following error messages:
spid8Could not continue scan with NOLOCK due to datamovement.
spid8Error: 1511, Severity: 21, State: 5
spid8Sort cannot be reconciled with transaction log.The client receives the 1511 error message and the restore processing terminates, which leaves the database in an unrecovered state.
Resolution
Starting with Microsoft SQL Server Service Pack 1 (SP1) build 7.00.699, recovery speed was increased by enabling read ahead abilities.
The error condition is triggered when recovery is too aggressive with read ahead operations while rolling forward index maintenance activities.
Symptoms
A SELECT statement that uses the four-part name against a linked server, might generate an access violation if all of the following conditions are met:The OLE DB provider for ODBC Driver is chosen to create the linked server.
The name of one unique index (for example,PK_index) is a shortened name of another unique clustered index (for example, PK_index_1__14) on the same table.
The unique clustered index includes the columns from the other unique index as part of its key.The query fails with an error message similar to the following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 8 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection BrokenThe short stack trace seen in the errorlog for the preceding spid is:
0×00574b4c Module(sqlservr+174b4c) (CTableMetadata::GatherGroupProperties+290)0×00622298 Module(sqlservr+222298) (CTableMetadata::LoadMetadata+19c)0×006221ac Module(sqlservr+2221ac) (CCvtTree::LoadAllMetadata+7c)0×00620888 Module(sqlservr+220888) (CCvtTree::PqryFromTree+dec)0×00621d5c Module(sqlservr+221d5c) (BuildQueryFromTree+8c)0×00621ef0 Module(sqlservr+221ef0) (CStmtQuery::InitQuery+184)0×00619b08 Module(sqlservr+219b08) (CStmtSelect::Init+cc)0×0052266c Module(sqlservr+12266c) (CCompPlan::FCompileStep+b98)0×004cf1a8 Module(sqlservr+cf1a8) (CProchdr::FCompile+7f0)0×004e0580 Module(sqlservr+e0580) (CSQLSource::FTransform+384)0×004e0100 Module(sqlservr+e0100) (CSQLStrings::FTransform+208)0×004c04ec Module(sqlservr+c04ec) (CSQLStrings::Compile+8c)0×004e5180 Module(sqlservr+e5180) (CStmtPrepQuery::CStmtPrepQuery+478)0×004ea238 Module(sqlservr+ea238) (CCompPlan::FCompileStep+184)0×004cf1a8 Module(sqlservr+cf1a8) (CProchdr::FCompile+7f0)0×004e0580 Module(sqlservr+e0580) (CSQLSource::FTransform+384)0×004e0100 Module(sqlservr+e0100) (CSQLStrings::FTransform+208)0×004de68c Module(sqlservr+de68c) (CSQLSource::Execute+14c)0×004dec24 Module(sqlservr+dec24) (language_exec+638)0×41066ea4 Module(opends60+6ea4) (execute_event+7a0)0×41067524 Module(opends60+7524) (process_commands+144)0×410a3620 Module(ums+3620) (ProcessWorkRequests+154)0×410a2af0 Module(ums+2af0) (ThreadStartRoutine+16c)0×780168e8 Module(MSVCRT+168e8) (endthread+fc)0×77e6cc48 Module(KERNEL32+cc48) (lstrcmpiW+128)2000-05-26 11:58:36.76 spid8CImageHelper::GetSym Error – The specified Module could not be found.2000-05-26 11:58:38.39 spid8Error: 0, Severity: 19, State: 02000-05-26 11:58:38.39 spid8language_exec: Process 8 generated an access violation. SQL Server is terminating this process.2000-05-28 11:00:43.96 spid8Using ’sqlimage.dll’ version ‘4.0.5′ Stack Dump being sent to C:\MSSQL7\log\SQL00002.dmp2000-05-28 11:01:03.65 spid8Error: 0, Severity: 19, State: 02000-05-28 11:01:03.65 spid8SqlDumpExceptionHandler: Process 8 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Resolution
To work around this problem you can either:Select the OLE DB provider for SQL Server to create the linked server.
-or-
Change the index name.