It would be nice to include
```
SET DATEFORMAT ymd;
```
statement to SQL Server script file (maybe some other scripts also need that fix) to guarantee correct data conversion from varchar to datetime.
Right now (Chinook Database 1.4 release) conversion fails for those who have different from year/month/date culture setting and thus some tables (in particular Customer, Employee, Invoice, InvoiceLine) will remain empty after script execution (foreign key conflicts).
```
SET DATEFORMAT ymd;
```
statement to SQL Server script file (maybe some other scripts also need that fix) to guarantee correct data conversion from varchar to datetime.
Right now (Chinook Database 1.4 release) conversion fails for those who have different from year/month/date culture setting and thus some tables (in particular Customer, Employee, Invoice, InvoiceLine) will remain empty after script execution (foreign key conflicts).
