%menu.branch% System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception: The network path was not found --- End of inner exception stack trace --- at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open() at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at Logic.Hoopla.DataInterface.RunProcedure(String Command, Hashtable Parameters) --- End of inner exception stack trace --- at Logic.Hoopla.DataInterface.RunProcedure(String Command, Hashtable Parameters) at Logic.Hoopla.Tags.Menu.createXmlMenuObject() at Logic.Hoopla.Tags.Menu.processMenu_Branch() at Logic.Hoopla.Tags.Processor.GetTagContent(String TagCode) at Logic.Hoopla.Tags.Extractor.internalProcessContent(String UnprocessedContent, String StartTag, String EndTag) -->

The Future

There is little doubt that the long term future of port and estuary hydrographic surveying may well lie with multibeam (swath) echo sounding; the big question is, at what point will the present rapid developments in this field allow it to be all things to all men? For some time now, this type of equipment has opened up the possibility of carrying out extensive surveys in deep water and now manufacturers are looking towards extending its capabilities into large-scale shallow water surveying.

With the recent rapid advancements in computer technology, there is no longer a problem in the collection and processing of vast data sets (up to 30,000 data points per second can be produced by a swath multibeam system!) The swath system is also particularly suited to the production of almost 'photographic' views of the seabed and, in addition, because of its large area of view, it can be used in a 'sideways looking' mode to inspect jetties, piers, breakwaters etc. It can also be used a tool to search a large area for wreck location, it has obvious coverage advantages over a conventional echo-sounder, these advantages only previously being equalled by a side-scan sonar.