Viewing 15 posts - 6,961 through 6,975 (of 59,102 total)
We have something that works great! We don't do continuous deployments to prod! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 8:02 pm
Ummm... why does KSA come first in #1 results?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 8:00 pm
Just to set expectations, I never backup to the server I'm backing up from. I backup to a NAS. My 1TB database takes about 30 minutes and I'm not splitting...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 7:57 pm
If most of your indexes have a "0" (equivalent to a 100 Fill Factor) and you rebuilt or reorganized them and the tables don't have an "ever-increasing" key on all...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 5:36 pm
p.s. If you're doing any index maintenance because of logical fragmentation on any index that has a "0" Fill Factor, you're only making fragmentation worse and, in fact, perpetuating it. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 4:15 pm
I have to agree with Sergiy. I'll also add that, if it is he index maintenance job, it's usually because of the "Death by Deframentation" horror that goes by the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2020 at 4:07 pm
What I've found is that "Data" is always correct. "Information" derived from the data is not. And even if the "Data" is skewed, it is still correct but...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2020 at 3:03 pm
If you really want to stress test some hardware, just migrate your existing code to it. That's when you'll find out two things... your code really is crap and all...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 11:49 pm
What I've found is that "Data" is always correct. "Information" derived from the data is not. And even if the "Data" is skewed, it is still correct but incomplete.
I love...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 11:37 pm
Thee are several methods for doing this but they're all too long to post here with any understanding. My recommendation is that you do a search for it and pick...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 7:19 pm
can moderator please delete my post with all html above? I apologize for that.
It would be quicker if you just edited the post and deleted the code block with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 7:14 pm
I have no idea why Microsoft has kept that option in the product - auto shrink will cause massive fragmentation of the database every time it shrinks. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 7:11 pm
Just to confirm, COALESCE won't provide an improvement in performance over CASE, although it will make the code a whole lot easier. Behind the scenes, the optimizer converts a COALESCE...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 3:20 pm
I have no idea why Microsoft has kept that option in the product - auto shrink will cause massive fragmentation of the database every time it shrinks. It is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 2:57 pm
DECLARE @DateString nvarchar(100)='Wed Jun 29 15:57:45 2019'
SELECT CONVERT(datetime,SUBSTRING(@DateString,5,100))
I've always been astounded by the implicit conversions of strings to DateTime that SQL Server handles correctly. It seriously...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 6, 2020 at 2:08 pm
Viewing 15 posts - 6,961 through 6,975 (of 59,102 total)