Viewing 15 posts - 6,256 through 6,270 (of 59,089 total)
Ah... almost forgot. One of the things that MS did very, VERY wrong is how they interpret the (secondary ANSI) format of YYYY-MM-DD when used for direct conversions from strings...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2020 at 3:14 am
Ugly, but this works:
DECLARE @SchedStart VARCHAR(25) = '2020-06-07-12.30.00.00000';
SELECT @SchedStart
,CAST(STUFF(STUFF(STUFF(LEFT(@SchedStart, 23), 11, 1, ' '), 14, 1, ':'), 17, 1, ':')...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2020 at 12:06 am
Just a different take on the same subject...
If the dates and times always follow the same format, which would also be required when using STUFF, then the hidden ANSI capabilities...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2020 at 12:00 am
Thanks for the correction, Scott. I plumb forgot about that aspect of CHECKs (mostly because I make end-date columns NOT NULL). They're like FK's in that aspect... they don't have...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2020 at 5:26 am
GUIDs are horrendous for clustered indexes. They fragment like crazy.
No sir... that's absolutely NOT correct. In fact, they can go for months without any page splits (not even supposed...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2020 at 5:10 am
Scott? 🙂
Sorry... had a "Scott" on my mind from a different post. Corrected my previous post.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 6:58 pm
CREATE TABLE Employee_Leave
While I agree that the original table name that the OP posted left some to be desired, so does the one you created. Wouldn't Employee_Leave_Days_Taken be more...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 6:56 pm
I'm not advocating for a freewheeling, anyone does whatever they want to do environment, either.
Totally understood. You have a heavy handed review board that seems to have gone over...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 6:30 pm
SSRS recognizes CHAR(10) as a line feed and will wrap each row in the text box.
That's good to know. Thanks, Jeffrey.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 6:15 pm
Do you have any comment on the history heap?
For a history table and with all else, "It Depends".
For example, a heap won't fragment or forward rows waste space (depending...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 6:13 pm
http://www2.cs.arizona.edu/~rts/publications.html
This also has his other books on temporal SQL, etc.
Excellent. Thanks, Joe. You've mentioned this site many times. Consider adding the link to your signature line. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 11, 2020 at 5:55 pm
Jonathan... they didn't say so in the original post but the OP is trying to do this in SSRS, not SSMS.
Great tip for SSMS, though!
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2020 at 9:02 pm
I don't know for sure but, IIRC, SSRS renders out as HTML. That might mean you need to use <br> instead of an actual character to induce a break in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2020 at 8:51 pm
You don't know how to do a data model for temporal data. Please get a copy of Rick Snodgrass's book from the University of Arizona on temporal queries in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2020 at 8:43 pm
First things, first. Tables that use Random GUIDs are a whole different animal that what I was talking about in the post you cited. They are one of the very...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2020 at 8:19 pm
Viewing 15 posts - 6,256 through 6,270 (of 59,089 total)