Viewing 15 posts - 16 through 30 (of 163 total)
Is there an explanation why 0x20 (32) results in 107 milliseconds?
November 7, 2017 at 1:47 am
July 19, 2017 at 4:14 am
July 6, 2017 at 6:35 am
Tiny comment about the explanation. It is not true that nothing can trigger the job: you can trigger the job manually.
July 3, 2017 at 1:27 am
It is just a typo. The explanation show the correct syntax 42 -> x.
April 26, 2017 at 5:42 am
Technically the answer is incorrect.This is because there UPDATE query will fail, because Price is not a field in the table, so the second query will just run normally.
Maybe...
March 8, 2017 at 3:30 am
I gave the "correct" answer, but I think it is not correct. AUTO is not an option as far as I see, it is a value that you can use...
March 3, 2017 at 4:32 am
February 8, 2017 at 2:45 am
I had the right answer, but was doubting, since the question specifically mentioned SSMS 2016.x.
As far as I know this is already possible since SSMS 2008 (R2).
November 14, 2016 at 4:11 am
Theoretically none of the answers are correct, since all results should have been exported as specified in the question, and not just the top 10. 😀
November 9, 2016 at 1:44 am
Magnus Ahlkvist (9/15/2016)
When I try to update a view (defined using WITH CHECK OPTION) with a value which makes the row fall outside...
September 15, 2016 at 1:45 am
The title of the question gave a small hint on what the answer had to be... 😀
August 3, 2016 at 9:14 am
TomThomson (6/1/2016)
June 1, 2016 at 5:41 am
Viewing 15 posts - 16 through 30 (of 163 total)