I've done this sort of thing many a time in Access, but SQL Server gives me errors when I try...<P>We have a table for company employees:<P>Employees<BR> * EmpID (key)<BR> * EmpFirstName<BR> * ...
In earlier versions of SQL Server, after selecting a join algorithm, SQL Server had to process it even if a better alternative might be available. In SQL Server 2017, the query optimizer can now sense ...