I read "Pragmatic Version Control: Using Subversion" before reading "Version Control with Subversion". For most people, I would say that is the correct order in which to approach these two books. The Pragmatic book is much more readable, but "Version Control with Subversion" goes into greater depth, answering some of the questions that the Pragmatic book doesn't. It still contains tutorial material, but also feels like a more authoritative reference.
Most developers think reading about version control is a waste of their time (surely they should be reading about C# or Python or the latest webby thing instead?). I disagree with that - there is little point developing fantastic code if you then lose your greatest work because version control isn't being used correctly. However, I am also realistic about how much time most developers can be persuaded to spend reading about subjects such as version control. Therefore, I would suggest that most developers on a team using Subversion should read the Pragmatic book, as that will give them enough detail to do what they need to, but without being too long or being heavy to read. However, I think it is worth a couple of developers at each site spending the extra time required to also read "Version Control with Subversion" in order to sort out the organisation and practices to follow at that site, including development of any scripts that might be required to support those practices. "Version Control with Subversion" gives extra detail about the differences between version 1.4 and 1.5 of Subversion, more detail on the pros and cons of using properties, use of externals etc. Most developers don't need to know these things, but a few do.
So, a good book, a bit heavier to read than the Pragmatic book, but still worth the effort for those developers who need to get involved in version control a bit more deeply.