More information can be found on Dwight's desk.

(In case this is too obscure: https://www.youtube.com/watch?v=6bTmKHNdS-o)

For Unix tools, the usual convention is that a single dash is for 1-letter parameters, and the double-dash for full named parameters (e.g. -h and --help, or -v / --verbose)

SSMS 17.9 and SQL 2019:

Funny thing is that the query runs (and gives the expected result).

SSMS won't work, at least not with SSMS 17.9:

Shouldn't the query read 'WHERE uc.UserID = 8'?

I assume genomes were mapped, not gnomes...

The question isn't "What is the easiest way" but "what should I do". And adding an extra file and migrating the data works.

SQL 2015?

---

Without calculating:
- 7E1 is odd, 7E2 is even, so it has to be 7E2
- 2018 is fairly close to 2048, a power of 2, so there's a few...

I've made some modifications to allow Point-In-Time restores. Code to convert the date_time variable to a format that STOPAT understands is rather ugly however, perhaps someone with a better understanding...

I think it stores the dates as floats, not ints.