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

by

Troubleshooting Guide: SQL Server Error 513 – Rule Conflict on Column Insert/Update

Why This Error Happens

This error occurs when a legacy CREATE RULE object is still bound to a column or user-defined data type via sp_bindrule, and the data being inserted or updated violates the logic defined in that rule. Since Microsoft deprecated rules in favor of CHECK constraints, this issue is most commonly seen in databases migrated or restored from older SQL Server instances (2016 and earlier) into SQL Server 2025. The conflict is a data integrity block, not a corruption issue, meaning the engine is correctly rejecting the transaction based on outdated schema logic that likely doesn’t match current application input.

Step-by-Step Resolution Guide

Step 1: Identify the Offending Rule and Table

  • Open SSMS (SQL Server Management Studio 21 or later) and connect to the affected instance.
  • Run the following query to locate the specific object causing the conflict: SELECT OBJECT_NAME(major_id), * FROM sys.extended_properties WHERE class = 1;
  • Alternatively, expand Programmability > Rules in Object Explorer under the specific database to view legacy rule definitions manually.

Step 2: Inspect the Rule Definition

  • Right-click the specific Rule object identified in Step 1 and select “Script Rule as > CREATE To > New Query Window.”
  • Analyze the T-SQL logic (e.g., @value IN (1, 2, 3) or @value LIKE '[0-9]%') to determine why the specific data payload is failing.
  • Cross-reference this logic with the application code currently attempting the write operation to confirm a mismatch.

Step 3: Unbind or Modify the Rule

  • If the rule is obsolete, run sp_unbindrule 'TableName.ColumnName'; to remove the restriction immediately.
  • If the rule is required for business logic, you must modify the incoming data to comply, or drop the rule and replace it with a modern constraint using: ALTER TABLE TableName ADD CONSTRAINT CK_ColumnName CHECK (Condition);
  • Execute DROP RULE RuleName; only after confirming no other columns or data types are bound to it via sp_help 'RuleName'.

Step 4: Restart Related Services

  • Navigate to Windows Services (services.msc) on the Windows Server 2025 host.
  • Restart the SQL Server (MSSQLSERVER) service to clear any cached execution plans that might still reference the old rule schema.
  • Verify the SQL Server Agent service is also running if the write operation was triggered by a scheduled job.

Alternative or Verification Steps

  • Verification: Re-run the exact INSERT or UPDATE statement that triggered the original Error 513; a successful execution with a “(1 row affected)” message confirms the fix.
  • Alternative: If unbinding the rule is not permitted by data governance policies, modify the application’s business logic layer to sanitize or validate input data before it reaches the SQL Server 2025 engine, ensuring compliance with the existing rule.