Viewing 15 posts - 7,156 through 7,170 (of 59,091 total)
"p.s. I agree with the concept that running for offices has become more of a financial contest and deters (along with a sick press) good people from running. Apparently,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2020 at 2:45 pm
With that, I have to ask, since MD5 returns a 16 Byte result and you convert that to BIGINT, which is an 8 Byte result (which is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2020 at 2:35 pm
While I agree that a "Shift-Left" instruction at the register level uses fewer CPU cycles than an "Add" instruction, I don't see the advantage in large data sets that will...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2020 at 2:30 pm
BWAAA-HAAA!!! I guessed wrong and "Dax a fact Jack" ! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2020 at 5:36 am
The formatting of lines was a render issue. Old coding v new coding, and it took time to fix. Despite what you see here, this isn't a high priority...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 4:13 pm
Orange one wasn't a criticism at all merely a descriptor.
Like I said, I have no great love for the man but "orange one" isn't just a "descriptor" . It's...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 3:26 pm
Heh... the most correct answer wasn't available, which would be "The source of a lot of XML that requires a lot of extra processing to derive information from in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 2:56 pm
I have seen an uuid generator written in Assembler a while ago (which I cannot find anymore unfortunately) but an approach like this is what I'd go for...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 2:52 pm
A recent database I created involves tables where the natural unique keys are several columns wide. Rather than using an IDENTITY or other incremental ID, for the surrogate key...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 2:50 pm
So why did the "new" forum software suddenly quadruple-space old posts? Why does the new forum software not even come close to the right color coding of SQL code especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2020 at 1:28 am
It's ironic that the best forums on SQL Server in the world are also the worst. I've given up on making suggestions. If it were the usability of the forums...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2020 at 6:27 pm
Simply amazing!!
My next question is, is there a good book you would recommend to teach me all these tricks?
Thank you!!
CROSSTABs are a bit of an ancient "Black Arts" method...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 6, 2020 at 3:00 pm
... start date will always be the month of July. The user will select a @p_startmonth,@p_startyear and @p_endmonth,@p_endyear. ...
I just noticed this. If the start date will always...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2020 at 4:31 pm
Like this?
WHERE site_code = @p_site_code
AND datepart(month,observ_date) = @p_startmonth
AND DATEPART(YEAR,observ_date)= @p_startyear
AND DATEPART(MONTH,observ_date) <= @p_endmonth
AND DATEPART(YEAR,observ_date)= @p_endyear
Not SARGable. Answer the question I just posted and let's put this problem to bed.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2020 at 3:32 pm
I know how to get data between just startdate and enddate, but I need to select it between just month and year, start month is previous July and current...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 5, 2020 at 3:31 pm
Viewing 15 posts - 7,156 through 7,170 (of 59,091 total)