Sort operation SQL Server 2012
First off, the sort operation on a simple query like this will probably always be the most costly.  That's because it's an operation that has to run after it has all of the data returned.  That being said, there are no clustered indexes on the tables.  That means they are heaps and they are storing the data totally unsorted on the disk.  Without adding a clustered index to those tables where your sort is applied, it's unlikely that any changes to your query will improve performance.  

The only other thing that might help(might being a very big might), is move the 'WHERE type = 4' part into the corresponding join statement that it belongs to.  So instead of WHERE type = 4 it would be added to the JOIN ON for ArchiveConfig (I think that's where type comes from at least) as AND type = 4.  The other ON clause for that join seems redundant.  Keep in mind, I doubt very much that this change will actually improve performance but it will make your code a bit cleaner.  

As the others have said, I don't know if it's a good idea to use the (NOLOCK) hint.  I doubt it will improve performance in this case and might result in bad data being returned.