Forum Replies Created
Viewing 15 posts - 16 through 30 (of 233 total)
-
Reply To: The JSON Table
Disappointed!
Just because you're right doesn't mean everybody else is wrong. -
Reply To: SQL MI Stop/Start Billing
Aleksandr Furman wrote:The way this question is asked it would be 11 hours, but I do get the confusion: that's what happens when British people try to Americanize the question, LOL....
Just because you're right doesn't mean everybody else is wrong. -
Reply To: SQL MI Stop/Start Billing
chris.mackenzie 149 wrote:What should we do when the answers are flawed like this? I also went for 9 hours because I assumed that was the intended correct response...
We wait until the...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: SQL MI Stop/Start Billing
17-7 = 10, and then some minutes. Given that billing is per started hour, I'd venture that the available answers fall short.
Just because you're right doesn't mean everybody else is wrong. -
Reply To: DOP Feedback Compatibilty
I'm not even going to begin trying to figure out what the question is. My guess is at least half the text is missing.
Just because you're right doesn't mean everybody else is wrong. -
Reply To: More ANSI_PADDING Tables
Scott Arendt wrote:I noticed that the actual answer did not appear in the results. I tried to guess the intent of the question, but was wrong.
There are two results that can...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: More ANSI_PADDING Tables
The correct answer to this will depend on the setting of ANSI_NULL_DFLT_ON, since the NULLability of the CHAR column isn't specified.
Just because you're right doesn't mean everybody else is wrong. -
Reply To: The VALUES Limit
George Vobr wrote:The question is asked clearly: "What is the limit for rows in a Table Valued Constructor?". The documentation states that there is a limit. So there is nothing left...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: The VALUES Limit
A table valued constructor is only limited to 1000 rows when used directly as a source for an insert statement. When used to create a derived table there is no...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: Necessary Insert Columns
Steve Jones - SSC Editor wrote:Part of the QotD is knowing defaults. This was left off, as many people do this and the default is to allow NULLs.
As a good practice, however, I agree....
Just because you're right doesn't mean everybody else is wrong. -
Reply To: Necessary Insert Columns
Just to nit-pick: This will depend on the settings of ANSI_NULL_DEFAULT_OFF / ANSI_NULL_DEFAULT_ON for the session, or by the ANSI_NULL_DEFAULT database option. By default, these will be set such that...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: EXCEPT
Carlo Romagnano wrote:Of course the isolation level of the database should be as in the image
Of course! That's obviously clear from the question😋
Just because you're right doesn't mean everybody else is wrong. -
Reply To: EXCEPT
I would argue that in principle the explanation is correct. However, in the example given, this would result in zero rows, unless a very specific set of conditions are met....
Just because you're right doesn't mean everybody else is wrong. -
Reply To: Changing the TDE Encryption
Maybe it's a good idea to refrain from answering this until the correct answer has been reviewed...
Just because you're right doesn't mean everybody else is wrong. -
Reply To: My New Resolution
leonardo.ssantos79 wrote:But the question was ONLY the year, and the year function (getdate()) doesn't do that?
It does, but there are two problems with that:
- It's not among the given alternatives
...
Just because you're right doesn't mean everybody else is wrong.
Viewing 15 posts - 16 through 30 (of 233 total)