Peter Heller - Monday, February 12, 2018 5:42 AM
SysDateTime() returns more bytes, which isn't necessary here because you're dumping the result to a variable with the DATE datatype.
As a bit of a sidebar and , SysDateTime() is relatively crippled because it returns a DATETIME2() datatype compared to GETDATE() which uses the powerful DATETIME datatype. DATETIME supports incredibly easy to use direct date/time math for period calculations (which is in the ISO standards) where DATETIME2() does not (at least not in SQL Server because they screwed it up). If you use it to support supposed "portable code", true portability is a myth and can't actually be accomplished to any great degree.
--Jeff Moden
Change is inevitable... Change for the better is not.