i have the same problem. but i'm concerned about something else. I have an table with 2 indexes, one clustered and one non-clustered. I have a lot of inserts -...

i have the same problem. but i'm concerned about something else. I have an table with 2 indexes, one clustered and one non-clustered. I have a lot of inserts -...

Yeah, I know. I have code to replace cursors with table variables, but this solution is assumed to be only for building or test environment. On product environment i have no cursors.

Hi there,

I think this solution will satisfy you:

First, I made a table with your records -

/*-- -Object: table [dbo].[tHouses]    -------*/

CREATE TABLE [dbo].[tHouses] (

 [ID] [smallint] IDENTITY (1,1) NOT NULL,

 [Street] [nvarchar](50)...

In fact, I am killing cache database connections made by other third party applications than the master application. So it is ok and my customer is happy 'cause the sql...

Good job, Leo!

Finnaly, I found an stored procedure which kills the db connections, KILL_DB_CONNECTIONS. But, not in the end, your logical schema was one of mine used in production...

another solution:

SELECT     field, COUNT(*) AS cnt

FROM         dbo.table

GROUP BY field

HAVING      (COUNT(*) > 1)

this will displays the field duplicated and how many is duplicated.

Thank you very much Lowell!

It works fine!