none
CheckDB on Geography data RRS feed

  • Question

  • I've narrowed down a DBCC CheckDB issue to a set of tables with Geography data types.  These tables are 100s of millions of records.  The integrity checks on these tables are taking 30-40 hours to complete.  Other tables with similar row counts but no geography data type only take 10-20 minutes.  This is full checks, not physical only.  Physical only checks on these tables complete in 5-10 minutes.  I cannot find anything that would indicate why the logical check portion would take so long on tables with spatial Geography data.


    Tuesday, November 12, 2019 11:59 PM

All replies

  • Hi Guapo79,

    What is the version of SQL Server are you using?

    >> why the logical check portion would take so long on tables with spatial Geography data.

    This issue may because Geography data types are SQLCLR data types. For more details, please refer to this blog. You could try to apply latest Service Pack and latest CU for SQL Server.

    In addition, please refer to this similar thread which might help.

    Hope this could help you.

    Best Regards,

    Amelia Gu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, November 14, 2019 8:02 AM