Viewing 15 posts - 3,361 through 3,375 (of 59,086 total)
Absolutely perfect. That graphic explains it all. I have a high performance idea on how to do this and I'll explore it tonight after work.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2022 at 2:24 pm
Jeff,
The above is the i/p which i receive my client which may having missing weeks data, so i need to populate 0 for missing weeks.
Also, actually it has two...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2022 at 9:10 pm
First thing I'd check for is the size of the log file being restored and then I'd check the original database to see the size and how many VLFs are...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2022 at 6:44 pm
Understood but you've not actually answered my question...
You say (or at least imply) that you want the first day of your weeks to be on Sunday. If the current date...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2022 at 6:26 pm
Hi All,
I have the below query , have set datefirst as Sunday (7), but here i am getting week 52 for Sunday and Week 53 for Monday. I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2022 at 10:11 pm
Focus first on logical I/Os, as that's usually the culprit one way or another.
You just re-stated exactly the first line of what I wrote in an earlier...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2022 at 9:03 pm
I considered submitting a request asking for a way to suppress the dark mode request.
I actually have to use DATEDIFF_BIG. The fact they couldn't be bothered to implement the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2022 at 3:45 pm
Or run the stored procedure yourself and email them the results in a spreadsheet.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2022 at 5:29 pm
Just remember that you'll end up with a rather huge transaction log file on Step 3 and it will take 2-3 times longer if you don't achieve "Minimal...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2022 at 5:20 pm
Just remember that you'll end up with a rather huge transaction log file on Step 3 and it will take 2-3 times longer if you don't achieve "Minimal Logging".
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2022 at 3:45 pm
Jeff,
My largest table has 20 million records and uses around 20 gigs but my tempdb maximum size is 192 gigs.
Regards,
That's a rather huge TempDB considering the relatively small size...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2022 at 3:42 pm
Thanks Jeff for those pointers. I am basically checking for an extended event trace definition file to track these numbers.
I never used sp_blitz and not sure how it will...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2022 at 3:33 pm
Yes it's just an encoding. How could one perform such an encoding without XML? That's the hijacked topic 🙂 As an aside: I associated the encoding with a conversion...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2022 at 4:21 pm
Thank you Jeff, for your follow-up!
The entire table might exist or not. The reason for that—versions of the particular app, so the query must be just one but run...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2022 at 6:25 am
Sounds like your transaction log being full is putting a stop to replication. There is no need to "shrink" the log file if it is just going to grow...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2022 at 6:19 am
Viewing 15 posts - 3,361 through 3,375 (of 59,086 total)