The following is the structure of the table:
CREATE TABLE [dbo].[xactControlPoint](
[xactControlPointID] [int] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
[xactControlPointTypeID] [int] NOT NULL,
[call_id] [int] NOT NULL,
[contr_id] [int] NULL,
[xactTransactionIDValue] [varchar](50) NULL,
[beginDate] [datetime] NOT NULL,
[userName] [varchar](250) NULL,
[notes] [varchar](2000) NULL,
[reservationFlg] [bit] NULL,
[rowUpdateDate] [datetime] NULL,
[rowUpdateID] [int] NULL,
[Target_Followup_Date] [datetime] NULL,
CONSTRAINT [PK_xactControlPoint] PRIMARY KEY CLUSTERED
(
[xactControlPointID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [FG1]
) ON [FG1]
The following are the indexes:
index_nameindex_descriptionindex_keys
IDX__xactControlPoint__Callid_xactControlPointTypeIDnonclustered located on FG2call_id, xactControlPointTypeID
IN_CallIDnonclustered located on FG2call_id
IN_ContrIDnonclustered located on FG2contr_id
IX_ControlPointTypeIDnonclustered located on FG1xactControlPointTypeID
IX_xactControlPoint__K3_K4nonclustered located on FG2call_id, contr_id
PK_xactControlPointclustered, unique, primary key located on FG1xactControlPointID
Besides adding the begin date to the Primary Key, what other indexes should be created?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/