usp_AdaptiveIndexDefrag / Error converting data type bigint to numeric

Open

#312 opened on Aug 19, 2024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: sql
Domain: database

Research direction

Start with usp_AdaptiveIndexDefrag and reproduce the statistics-collection path that calls sys.dm_db_stats_properties. Investigate the bigint-to-numeric conversion reported as error 8114, using the provided output and bigint column context. Done means statistics collection completes without the conversion error and defragmentation is no longer left incomplete.

Written by the indexing model from the issue text.

Description

This seems to be happening during collection of statistics, leaving the defragmentation effort incomplete.

   Selecting a statistic to update...
   Getting information on selected statistic...
   Determining modification row counter for statistic [...] on table or view [...] of DB [...]...
     Using sys.dm_db_stats_properties DMF...
     Error 8114 has occurred while determining row modification counter. Message: Error converting data type bigint to numeric. (Line Number: 0)
     Found a row modification counter of 0.000 and 332 rows...
     No need to update statistic [...] on DB [...] and object [...]...

The relevant table has a field of type bigint which seems to be where the conflict is originating from.

Without a fix for this the tool cannot be used efficiently.

Dominant language: Jupyter Notebook
Stars: 1.6k
Forks: 749
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Batched `completeJobs`/`failJobs` are never retried: the retry loop in `batch()` exits after the first failure Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

graphile/worker#636 · Opened Sep 21, 2026
Test Failure: com.ibm.ws.jdbc.fat.sqlserver.SQLServerTest J2CA0079E Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

OpenLiberty/open-liberty#35839 · Opened Sep 21, 2026
hash join v2: 'unsupported column type for pre-alloc 225' when joining on a VECTOR column Open

affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

pingcap/tidb#71473 · Opened Sep 21, 2026
JSON_VALUE fails to parse when a RETURNING clause is present but the optional ON EMPTY/ON ERROR clause is omitted Open

Difficulty 1/5 Under an hour Newbie friendliness 92/100

antlr/grammars-v4#5014 · 1 comment · Opened Sep 21, 2026
readBinary(std::vector) throws a bare Poco::Exception (POCO_EXCEPTION code 1000) for too-large sizes instead of TOO_LARGE_ARRAY_SIZE Open

comp-query-execution fuzz

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

ClickHouse/ClickHouse#121303 · 3 comments · Opened Sep 21, 2026

More Databases issues