> We recently upgraded from Sybase 4.9 to Sybase 11. We are now having a
> problem with table scans, something which did not occur in 4.9. Our large
> table contains a column with NULLS not allowed. Our small table contains
> a column with NULLS allowed. With Sybase 4.9, the optimizer would join
> these two tables using indexes, but with Sybase 11 the optimizer table scans
> the large table. Our resolution has been to bcp out the small table, change
> the column to not allow NULLS and bcp the table back in. Does anyone know of
> a better fix than this, or if this is a bug?
> Much thanks.
is 91387), Does the query do an outer join on the two tables
(large and small)?
Sybase seems to roll out the fix for this problem in