Release 1.0 known issues: index creation order; 10-min. timeout


The following are known issues for Release 1.0. I've been informed by the developer(s) that these issues will be remedied with the next release, slated for 2008 Q4. The next release will also provide support for SQL Server 2008.
  • There is no order enforced when building indexes, whereas it would be advantageous to create clustered indexes before creating nonclustered indexes on a non-empty table.
  • Issued statements are given 10 minutes to run before failing with a time-out error. For example, if an individual index requires more than 10 minutes to create, an error will occur at the 10-minute mark. The remedy is to explicitly set the ServerConnection.StatementTimeout property to an appropriate value higher than the default value; the default value for this property is 600 (seconds, or 10 minutes).
    Thanks to the developer(s) for such a valuable utility.
Closed Feb 23, 2009 at 7:25 PM by Stuarto
Fixed with Release 2.0