Normal
Evidently the dependency on SQL Browser is not adequate. I assumed that it was needed in addition to the dependency on SQL Server itself. If that is not the case, then the command to set the dependency should be:Unfortunately, I rejoiced too soon; on subsequent reboots, the added dependency has disappeared each time, so I am going back to the workaround solution of using "Automatic (Delayed Start)". So far, that has worked reliably. BTW, the DB connection dialog still says SQL Server "2005". Since it has been proven that the DB I/F works with later versions of SQL Server, i suggest deleting "2005" to avoid confusing the uninitiated ;-)
Evidently the dependency on SQL Browser is not adequate. I assumed that it was needed in addition to the dependency on SQL Server itself. If that is not the case, then the command to set the dependency should be:
Unfortunately, I rejoiced too soon; on subsequent reboots, the added dependency has disappeared each time, so I am going back to the workaround solution of using "Automatic (Delayed Start)". So far, that has worked reliably. BTW, the DB connection dialog still says SQL Server "2005". Since it has been proven that the DB I/F works with later versions of SQL Server, i suggest deleting "2005" to avoid confusing the uninitiated ;-)
