Viewing 15 posts - 1,651 through 1,665 (of 4,087 total)
Since a bit only has two values 1 or 0, yes or no, on or...
August 11, 2017 at 6:59 am
I wasn't sure if you needed to also account for holidays. I came up with this approach that would account for holidays, but it does require a calendar table. (You...
August 10, 2017 at 9:44 am
August 9, 2017 at 12:42 pm
ExhibitA - Wednesday, August 9, 2017 4:52 AMIs there a Lehmans explanation available?thanks in advance
Did you perhaps mean a "layman's explanation"?
Drew
August 9, 2017 at 8:16 am
ravikaliappan - Wednesday, August 9, 2017 3:47 AMI tried this it doesn't workSELECT CONVERT(datetime, 0x17041D49FCC2D488)
SELECT CONVERT(datetime2, 0x17041D49FCC2D488)
First, you should...
August 9, 2017 at 7:54 am
I used to use INFORMATION_SCHEMA exclusively, until I was trying to use them to quickly review the definitions of stored procedures and found out that the definitions are limited to...
August 8, 2017 at 2:29 pm
August 8, 2017 at 2:24 pm
There are two main options for this, and which one performs better depends on the typical number of records on the many side of the relationship. The CROSS APPLY works...
August 4, 2017 at 11:13 am
August 4, 2017 at 8:04 am
August 4, 2017 at 7:51 am
August 4, 2017 at 7:39 am
The problem is that you are doing an implicit CROSS JOIN. Here is the explicit version of what you are doing.
update tbl
set sequel = tbl.sequel_Inner
August 3, 2017 at 1:21 pm
Wouldn't it be easier to just use the function designed specifically for this purpose?
SELECT CAST(DATEADD(SECOND, @time, '00:00') AS TIME(0))
Drew
August 3, 2017 at 12:55 pm
The main issue is that the intervals in your second table aren't packed. Here is an article that discusses Packing Intervals.
The approach I took was to pack...
August 3, 2017 at 12:32 pm
Viewing 15 posts - 1,651 through 1,665 (of 4,087 total)