Viewing 15 posts - 1 through 15 (of 53 total)
Thank you all for your help!
April 23, 2019 at 2:46 pm
Thanks for the sample. It does exactly what I expect.
What is it compatibility level? Does it work on SQL2012?
April 18, 2019 at 2:45 pm
yes I know, but some clients still use version 2012... so I cannot use it
January 16, 2019 at 6:14 am
Cool, thank you!
January 16, 2019 at 2:38 am
To make a long story short...
Tried all kinds of string encoders on the sql command before execution but that did not work.
But if I save my command to...
January 8, 2019 at 10:29 am
I suspect that when writing the command to the log file some sort of correction or formatting happens so that the command is correct when copy/pasted into SSMS???
January 8, 2019 at 9:02 am
you have to use nvarchar(2), NOT nvarchar(1)
January 8, 2019 at 8:54 am
All right, with the HAVING clause it works like it should.
Thanks
May 17, 2018 at 7:39 am
Chris, this returns also the unwanted 3rd row
May 17, 2018 at 7:38 am
Yes, this works like I want it!
Thank you so much.🙂
May 17, 2018 at 7:22 am
NULL 2018-01-01 12:00:00
2018-01-01 20:00:00 2018-01-02 08:00:00
2018-01-03 08:00:00 2018-01-03 08:00:00 This row should not be there (for my result)
2018-01-05 06:00:00 NULL
May 17, 2018 at 7:01 am
Good remark, but when there are adjacent bookings, where "till" date from booking 2 is same as "from" date of booking 3 then I also get an unwanted row (row...
May 17, 2018 at 6:57 am
Cool...
But when there are overlaps, the result is cot correct.
Please try this:
declare @t table(dBookedFrom smalldatetime, dBookedTill smalldatetime)
insert into @t
values('20180101 12:00',...
May 17, 2018 at 5:03 am
Thank you very much.
Will test it and keep you posted...
September 9, 2017 at 12:58 am
The more I examine my issue, the more complex it gets and i am starting to think there is no solution for this.
Here I have 8 rows, each row...
September 1, 2017 at 7:53 am
Viewing 15 posts - 1 through 15 (of 53 total)