How to fix Error 13143 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 13143 (Partition Function Conflict)

Why This Error Happens

Error 13143 typically occurs when a Transact-SQL statement attempts to modify or drop a partition function that is still referenced by one or more partition schemes or tables. SQL Server 2025 enforces strict dependency validation, so any existing object binding (such as an active partition scheme or indexed table) will block the operation until the dependency chain is cleared. This is often triggered by incomplete cleanup scripts or outdated migration logic carried over from previous SQL Server versions.

Step-by-Step Resolution Guide

Step 1: Identify Dependent Objects

  • Run the following query to locate schemes bound to the function:
    SELECT * FROM sys.partition_schemes WHERE function_id = (SELECT function_id FROM sys.partition_functions WHERE name = 'YourFunctionName');
  • Check sys.partitions to see if any tables currently hold data within the partition boundaries defined by this function.
  • Note the names of all dependent schemes and tables for the next step.

Step 2: Detach or Modify Dependent Schemes

  • If a partition scheme is using the function, you must alter the underlying table to use a different scheme or drop the index that enforces the partitioning.
  • Use ALTER TABLE [YourTable] DROP CONSTRAINT [ClusteredIndexName] WITH (MOVE TO [PRIMARY]) to move data off the partitioned structure if you intend to fully deprecate the function.
  • Verify no “ghost” records exist by running DBCC CHECKTABLE on the previously partitioned table.

Step 3: Correct the Partition Function Syntax

  • If the error stems from a mismatched data type (a common cause in Windows Server 2025 environments due to collation updates), verify the function definition matches the column type exactly.
  • Re-create the function using the corrected boundary values:
    CREATE PARTITION FUNCTION [NewPartFunc](int) AS RANGE LEFT FOR VALUES (100, 200, 300);
  • Ensure the file groups referenced in the scheme exist and are online by checking the SQL Server Configuration Manager.

Step 4: Restart the SQL Server Service

  • Open Services.msc on Windows Server 2025.
  • Locate SQL Server (MSSQLSERVER) and select Restart to clear any cached execution plans that might be holding a stale lock on the function metadata.
  • Confirm the service status returns to “Running” before proceeding.

Alternative or Verification Steps

  • Verification: Execute sp_helptext 'YourFunctionName' in SQL Server Management Studio (SSMS) to confirm the new boundary values have been saved correctly without throwing Error 13143.
  • Alternative: If the error persists, use the Database Engine Tuning Advisor to generate a fresh partitioning strategy script, bypassing the manually corrupted dependency links entirely.