Viewing 15 posts - 8,596 through 8,610 (of 59,072 total)
TF 1118 and 1117 are automatically implemented in 2016. You can turn them off for all databases except for TempDB. I wouldn't turn 1118 off anywhere but I...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2019 at 8:55 pm
I agree with the others about MAXDOP and Cost Threshold for Parallelism (CTP from here on) being more of an observational art rather than a science. I also agree that...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2019 at 3:44 pm
I have a suspicion that the same behavior would have been seen in SQL2016, but no proof and no reason to personally research it at the moment. BTW...we are...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 24, 2019 at 2:51 pm
Hi,
I am doing STUFF in my query which is concatenating the blank data too and data looks like below. Sometimes there is space+comma and sometimes only comma in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2019 at 10:13 pm
Thanks for the detailed followup. Just to be sure, though... the problem/observations that I posted appear to be the same problem and it's with 2016, not 2017. Did I "get...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2019 at 9:53 pm
Not heaps. They do have clustered indexes as primary keys.
Most are BULK inserted to.
Rebuilding the indexes does help to recapture the space, but it only starts building again, which...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2019 at 4:00 pm
Thanks for the feedback, Paul. The articles of yours that I provided a link to are awesome. I'm still testing a bunch of things based on your excellent documentation. Thank...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 23, 2019 at 3:08 pm
No. Not quite right. I hope you've recently taken a full backup. If so, then you can take your log file backup and then immediately do a shrink if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2019 at 3:34 am
Ok... first of all, you didn't say anywhere else that this was a "UAT" box. I thought it was a prod box because you were talking about licensing costs, etc. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 9:23 pm
This is a duplicate post and it's actually incomplete. Please, no replies here. See the following post instead. It's also been answered but don't let that stop you if you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 7:06 pm
And now I see that you've posted while I was constructing a response. You can't actually insert into a TIMESTAMP datatype in SQL Server. With that in mind, which RDBMS...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 7:03 pm
Here's one simple method provided those are actual NULLs and not just a word of '[NULL]':
SELECT ProcessID
,IsCompleted...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 6:56 pm
Oh... almost forget... your question was...
My question is, if all the queries are poorly performing. In that case, where do I start my troubleshooting.
The answer is, the system knows. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 5:19 pm
I'd worry about memory but not in the way you distributed it. You have a fair number of fairly large databases. Adding memory is generally the single best hardware improvement...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 5:06 pm
My first observation is that there is no index to support this query even if the "table" was in good shape. You could try the following indexes to see if...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 21, 2019 at 4:05 pm
Viewing 15 posts - 8,596 through 8,610 (of 59,072 total)