Hi opc.three,

Thanks for the feedback so far. Really appreciate your time.

Actual execution plan of a currently running query is what I'm looking to get, I'll take a look at profiler, SST options.

In one of your responses, you said: "I'm guessing that it would be a bad idea",

Did you mean to say: "wouldn't be a bad idea"?

Answers to your follow up questions on FF:

- It is not clustered

- The GUIDs are generated/managed by the application. Here are some examples:

b3d4a540-0c4e-1000-8029-a571dc530000

b3d4a541-0c4e-1000-8029-a571dc530000

b3d4a542-0c4e-1000-8029-a571dc530000

b3d4a543-0c4e-1000-8029-a571dc530000

b3d4a544-0c4e-1000-8029-a571dc530000

b3d4a545-0c4e-1000-8029-a571dc530000

b3d4a546-0c4e-1000-8029-a571dc530000

Here are some examples of the QUALIFIED IDs:

1-12TVTL1

1-1CDYQZQ

1-HDPSS4

Here is DDL for table and index:

CREATE TABLE [dbo].[M_C_CONTACT] (

[GUID] [nvarchar](50) NOT NULL,

[QUALIFIED_ID] [nvarchar](30) NOT NULL

) ON [PRIMARY]

CREATE UNIQUE NONCLUSTERED INDEX [M_C_CONTACT_U1] ON [dbo].[M_C_CONTACT]

(

[GUID] ASC,

[QUALIFIED_ID] ASC

) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 95) ON [PRIMARY]