Viewing 15 posts - 7,036 through 7,050 (of 59,072 total)
+1 Billion to Roger Plowman for his post above. I'll also add that commenting code when you're writing it is pretty simple. The first thing I normally do is to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2020 at 1:45 pm
Play with the idea of having a calendar table and then doing a set-oriented EXCEPT operator to find the missing dates and insert a row with the dummy values...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 9:09 pm
p.s. Even in SQL Server 2016, there's still a limit of the In Memory stuff of 250GB. In the databases of today, that means you have to be a wee...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 9:03 pm
I didn't mean that as a slam. It's just not possible to post general guidlines because everyone's stuff is different. I just watched the following YouTube on the subject... every...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 8:55 pm
Yep... let's go back to square one... if they were to move to Teradata and do the same types of things that they've done with their SQL Server, they'd still...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 8:47 pm
Sorry... you're not going to like this. My general guideline for things as important as Memory Optimized data is to Google for the documentation and read about it because I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 5:36 pm
Great. I wish you well on your endeavor.
As a bit of a sidebar, consider documenting the various things you did and writing an article about it here on SSC even...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 4:06 pm
You're welcome and thank you for the feedback. The question now is... do you know how it works? I ask because you're the one that is going to have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 2:29 pm
Understood. A large part of the problem may actually be the 80% Fill Factor thing you folks have done. It actually takes 25% (not just 20%) more space to store...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 2:24 pm
OK... here we go... code looks almost the same as before but added a couple of tweaks to do it just for the first of the month... I also fix...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 7:10 am
Crud... I have a bug in the code I just posted here... it missed 12/1/2019 and so I've removed the code... I'll be back soon.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 7:00 am
That's for equalities. If you have an inequality, you'll need to reverse the comparison operator if you reverse the order of the columns.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 6:51 am
Since you didn't use a variable on the left side of the "=", you've changed it to a column assignment. Since the variable had no assigned value, it went ripping...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 6:41 am
This should do the trick for you. It hasn't populated the original table with the extra rows but it creates the source we could with. I'm just not sure that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 5:55 am
Good luck on the exams, Michael. When you pass them, maybe you can teach me about XML! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2020 at 4:56 am
Viewing 15 posts - 7,036 through 7,050 (of 59,072 total)