Home Forums SQL Server 2005 T-SQL (SS2K5) cannot insert duplicate key row in object 'tablename' with unique index 'indexname' RE: cannot insert duplicate key row in object 'tablename' with unique index 'indexname'

  • Chris Morris (4/22/2009)


    Hi Venki

    Can you post the script for the table please? This will allow future posters to evaluate the problem.

    Chris,

    I am sending the script for the table.

    USE [WKO]

    GO

    /****** Object: Table [dbo].[tblCostBuildUp] Script Date: 04/22/2009 18:46:29 ******/

    SET ANSI_NULLS ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    CREATE TABLE [dbo].[tblCostBuildUp](

    [CostProjCode] [nvarchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

    [CostCAOCode] [nvarchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

    [CostWorkOrder] [nvarchar](8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,

    [CostCAODescription] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

    [CostOriginalBudget] [real] NULL CONSTRAINT [DF__Temporary__CostO__4F7CD00D] DEFAULT (0),

    [CostEstimatedCost] [real] NULL CONSTRAINT [DF__Temporary__CostE__5070F446] DEFAULT (0),

    [CostRealCost] [float] NULL CONSTRAINT [DF__Temporary__CostR__5165187F] DEFAULT (0),

    [CostOriginalHours] [smallint] NULL CONSTRAINT [DF__Temporary__CostO__52593CB8] DEFAULT (0),

    [CostEstimatedHours] [smallint] NULL CONSTRAINT [DF__Temporary__CostE__534D60F1] DEFAULT (0),

    [CostRealHours] [smallint] NULL CONSTRAINT [DF__Temporary__CostR__5441852A] DEFAULT (0),

    [CostComments] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

    [CostStatus] [bit] NULL CONSTRAINT [DF__Temporary__CostS__5535A963] DEFAULT (0),

    [CostChargeType] [bit] NULL CONSTRAINT [DF__Temporary__CostC__5629CD9C] DEFAULT (0),

    [CostType] [nvarchar](3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

    CONSTRAINT [aaaaatblCostBuildUp4_PK] PRIMARY KEY NONCLUSTERED

    (

    [CostProjCode] ASC,

    [CostCAOCode] ASC,

    [CostWorkOrder] ASC

    ) ON [PRIMARY]

    ) ON [PRIMARY]

    GO

    USE [WKO]

    GO

    ALTER TABLE [dbo].[tblCostBuildUp] WITH NOCHECK ADD CONSTRAINT [tblCostBuildUp_FK00] FOREIGN KEY([CostCAOCode])

    REFERENCES [dbo].[tblCAO] ([CAOCode])

    ON UPDATE CASCADE

    GO

    ALTER TABLE [dbo].[tblCostBuildUp] CHECK CONSTRAINT [tblCostBuildUp_FK00]

    GO

    ALTER TABLE [dbo].[tblCostBuildUp] WITH NOCHECK ADD CONSTRAINT [tblCostBuildUp_FK01] FOREIGN KEY([CostProjCode])

    REFERENCES [dbo].[tblProject] ([ProjCode])

    ON UPDATE CASCADE

    ON DELETE CASCADE

    GO

    ALTER TABLE [dbo].[tblCostBuildUp] CHECK CONSTRAINT [tblCostBuildUp_FK01]

    CostWorkOrder column is have the Unique nonClustered index. So If I remove this index will it be any problem for the rest of the tables and will the application work? This is my question, please give any clues to start from where.

    Thank You