We have SentryOne.  I have created a maintenance window within SentryOne.

But this is native SQL Server alerts.  I'm not sure how to create a maintenance window for those.

Jeff / Eddy,

I really appreciate the feedback and replies.  I've seen that most of our databases have LOB data.

I am preparing to talk to my manager about your suggestions.  Here...

I am still researching the cardinality estimator.  While researching that, I noticed that the database compatibility  has not changed from the migration.  In fact, it looks like it wasn't changed...

The old server was SQL Server 2008 R2.

No, I hadn't checked the latency of the log file drives.  I will check that as well.

Thanks.

Thank you. I've never used DBA tools. I did find a master server which can run things on target servers. This sounds interesting. I can run multiple...

Hey everyone,

I've been on call this week and got really busy with other production issues.  However, I wanted to follow up on this issue.

I went saw...

The original table is exportLogTable.  There are no rows in this table though.  I copied the table to exportLogTable2 in hopes to truncate the original table, create the primary key...

Not exactly considered best practice, but if you don't care which dupe gets dumped, you could consider setting IGNORE_DUP_KEY = ON on your PK to ignore dupes silently (

I tried the  IGNORE_DUP_KEY = ON  and that failed also.

I wasn't able to create the index.

The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.TableID' and the index name 'ClusteredIndex-20180604-101725'.

I can't create the clustered index with the duplicates. I've already tried that.  I have get rid of the dups first.

I guess I could write a query to...

Lynn, sorry to let you down.  I did look at the url, but I definitely missed the colons.

Scott, Thank you, thank you and again thank you.

I...

I do appreciate the thoughts and ideas.  But I checked and no triggers.  Can't remember when I was stomped by an update statement.🙂

Removing the dashes didn't seem to resolve it.  Got the same error message.

This is working with SQL Server 2016.