That is a good idea.  I can do that.  Thanks.

Thanks for that both of you.

1.  I had tried the FROM EXTERNAL PROVIDER.  But I got an error message.

Msg 15006, Level 16, State 5, Line 1

'domain\BIDevelopers' is not a valid...

I do appreciate all of the feedback.  However, you are fussing at the DBA who is the low man on the totem pole.  AVPs and managers have already made the...

Oh my goodness thank you.

I have been trying various things to no end.  I tried the snap in, but you outlined more steps.

Thank you so much.  I am trying it...

Great information.

During patching, both servers are in the same group to be rebooted.  We never thought about separating the servers that are involved in an AG and then insuring the...

Thanks, but I was afraid of that.

We have over 30 servers that have critical alerts implemented.  That would be disabling six alerts per server.

That is a lot to do each...

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.