DECLARE  @intID    BIGINT
        ,@bridgeid BIGINT = 1
;
 UPDATE dbo.bridge 
    SET @intID...

Cluster STXL on ( MANDT, TDOBJECT, TDNAME ) instead of creating all those separate non-clus indexes.  If those key columns are not inherently unique, and you can add...

In case you want it, here's a function to prep the string as we discussed:

DECLARE @string nvarchar(max);

SET @string = '"A1","A2","A3","A4","A5"

"000066666XYZ",00002,"","","1,000,000"';

SET @string = REPLACE(@string, CHAR(13) + CHAR(10), ',');

SELECT @string, dbo.prepare_string_for_split(@string, DEFAULT,...

I look at missing index stats quite frequently.  Very often I don't add or update index based on them, but I still review the stats just in case.  Sometimes a...

Cluster STXL on ( MANDT, TDOBJECT, TDNAME ) instead of creating all those separate non-clus indexes.  If those key columns are not inherently unique, and you can add a single...

When I had to do something like this, I created a custom function that would replace commas if, and only if, they were enclosed in double quotes.  Using a function prior...

(dup post, removed)

You can't really accurately consider one index in isolation.  You need to look at all indexes on the table AND at all uses of the table.

sys.indexes will give you the...

The clus index must be unique, and it is a lot of overhead for SQL to force uniqueness, which it must do if you don't.  You then will often also...

No, if the combination of all three columns would always be unique if CHANGENR were added:

dbo.CDPOS ( OBJECTCLAS, OBJECTID, CHANGENR )

You've got the correct clustered index on CDPOS, except perhaps that it's not unique.  If adding CHANGENR to the clus index will make it UNIQUE, you should do that.

Either way,...

If you are putting NOLOCK on an INSERT, UPDATE, or DELETE query, that's not going to do anything. SQL doesn't allow NOLOCK on data change operations as it doesn't...

Surrogate keys are not necessarily bad, if chosen after proper analysis, but just automatically defaulting to using a surrogate...

IF the most critical lookup on the table is the one you've posted, and since you're deleting rows frequently, I'd suggest you consider re-clustering the table to allow clus index...

The ERD is nice, thanks for that.

But I think you need to step back and do the logical design first (designing using Entities and Attributes rather than tables and columns),...

• This reply was modified 1 years, 6 months ago by ScottPletcher.