When performing schema comparisons across SQL Server databases, we have noticed that some indexes are not being seen in DB Solo.  We set up a SQL Profiler to see what query was being used to fetch the indexes for a table and found out that the reason for indexes missing was due to the criteria "
i.indid > 0 and i.indid < 255" in the following stored procedure call;
exec sp_executesql N'select i.*, f.groupname from sysindexes i, sysfilegroups f where 
i.id = @P0 and 
i.indid > 0 and i.indid < 255 and (i.status & 64) = 0 and i.groupid = f.groupid        ',N'@P0 int',99999999
We found that the missing indexes had an indid value that was greater than 255.
This looks like a bug ?