Viewing 15 posts - 1 through 15 (of 246 total)
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...
June 30, 2020 at 2:41 pm
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...
November 18, 2019 at 5:06 pm
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.
November 18, 2019 at 4:36 pm
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...
June 5, 2019 at 3:18 pm
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...
May 24, 2019 at 4:11 pm
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.
May 24, 2019 at 1:40 pm
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...
April 12, 2019 at 8:47 pm
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...
June 7, 2018 at 10:03 am
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...
June 4, 2018 at 10:40 am
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 (
June 4, 2018 at 9:51 am
I tried the IGNORE_DUP_KEY = ON and that failed also.
June 4, 2018 at 9:48 am
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'.
June 4, 2018 at 9:23 am
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...
June 4, 2018 at 8:47 am
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.
May 8, 2018 at 7:40 am
I do appreciate the thoughts and ideas. But I checked and no triggers. Can't remember when I was stomped by an update statement.🙂
May 7, 2018 at 3:55 pm