Cannot INSERT into partitioned view ‘%.*ls’ because table ‘%.*ls’ has an IDENTITY constraint.

Error Message:
Msg 4433, Level 16, State 4, Line 2
Cannot INSERT into partitioned view ‘%.*ls’ because table ‘%.*ls’ has an IDENTITY constraint.

Severity level:
16.

Description:
This error message appears when you try to insert into a partitioned view, but at least one of its member tables has an IDENTITY constraint.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Errors of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. The member tables of a partitioned view cannot have IDENTITY constraints.

Versions:
This error message was introduced with SQL Server 2000.

Example(s):
IF OBJECT_ID (‘dbo.T’) IS NOT NULL
    DROP TABLE dbo.T;
GO
IF OBJECT_ID (‘dbo.T1′) IS NOT NULL
    DROP TABLE dbo.T1;
GO
IF OBJECT_ID (‘dbo.V’) IS NOT NULL
    DROP VIEW dbo.V;
GO

CREATE TABLE dbo.T
(
    c1 int PRIMARY KEY CHECK (c1 BETWEEN 1 AND 10),
    c2 int IDENTITY
)
GO
CREATE TABLE dbo.T1
(
    c1 int PRIMARY KEY CHECK (c1 BETWEEN 11 AND 20),
    c2 int
)
GO

CREATE VIEW dbo.V
AS
SELECT
    c1, c2
FROM
    dbo.T
UNION ALL
SELECT
    c1, c2
FROM
    dbo.T1
GO

INSERT INTO dbo.V (c1, c2) VALUES (1, 1);

Remarks:
In the above example we try to insert into the view dbo.V. Because dbo.T has an IDENTITY constraint, the error is raised.




Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |