The generally accepted practice is to use an unambiguous date format - which would be interpreted by SQL Server correctly all the time.
The problem is that several date formats are subject to the language - and will be interpreted differently. For example - in US English systems the date 01/12/2022 will be interpreted at January 12th, 2022 - but on a British English system it will be interpreted as December 1st, 2022.
However - on both systems the date format YYYYMMDD will always be interpreted correctly. So 20220112 will be interpreted as December 1st, 2022 regardless of the language setting.
The format YYYY-MM-DD is problematic when using the DATETIME data type, as it will be interpreted as YYYY-MM-DD on US English and YYYY-DD-MM on British English. However, for the DATE, DATETIME2 and DATETIMEOFFSET data types it will always be interpreted as YYYY-MM-DD.