konradh
Still never use it.

Same here.
I've often thought I must be missing something by not using it but never discovered what that something was, even after reading this thread!

I use Console View only if I need to find all tracks where I use some plugin, or something like that, involving plugins or routing, and many tracks simultaneously, some technical application or fixing. For other tasks CV is unusable for me. One of the reasons is that I rely on folders for structuring my projects, often I even don't name my tracks, only folders, and it make it impossible to find tracks in CV without folders in it.

I definitely use it.
- you can open and close all Pro Channel strips at once by ctrl+clicking
- You can monitor the PC clip indicator on lots of tracks at once, including busses and output
- You can access the wave form view of one track when you use the partial view and put one track at the top of the screen.
- The Concrete Limiter only shows the max limiting measure when it's in view during playback. Other effects work similarly giving feedback only when visible. 
- When things are side-chained... say a kick sent to compressor on a pad or a bass... you can see that the compressor triggers with the kick hit.
 
It's not the best view for working with envelopes or entering midi data. :-)
 
But for me having the channel strip opened side by side with the Pro Channel has obvious value. No need for ctrl+i to switch between strip views like in Track View.
 
Console View is my preferred view when sending sound to monitors so the singers can hear themselves. 

I always use the console view. It's on my left monitor, the rest is on my right. I think it is good way of getting an overview of the different channels volume, effects and send.

Two monitors one on track view - one on console view...

You don't need to use console view, as it mostly duplicates what's in track view. I used only track view until the X-series. Now I split my time between track view and console view, courtesy of the "D" keyboard shortcut.
 
Console view puts me in a space that's more conducive to mixing. I find Track View more conducive to tracking and editing. However I also like that you can access a console-like view with Track View thanks to the Inspector.
 
One of SONAR's big strengths is that it offers so many ways to do similar tasks, which means you can choose what's most comfortable for you. However, I do recommend "forcing" yourself to use some features for a certain period of time so you know their strengths and limitations, as that can help in choosing the right tool for the right job.
 
 

I use it to copy settings from one track to another.
And when the client is in the office. Looks good.

For many years, I rarely used the Console View as most of my workflow was laying down tracks, working with clips and manipulating automation on a track-by-track basis.  When I started using Sonar as the "mixing console" for live venues, I started using the Console View regularly.  It was then I discovered that I could use the Console View to much more effectively perform some tasks that I was previously doing using only the Track View.
 
As a result, I currently use the Console View as a regular part of my normal workflow.
 
Paul

I never use Console View. I tried having it in the multidock but it's like trying to work through a letter box.

For me, it's about spending the last 25 years mixing live shows on a real console. Mixing in Sonar with the console view just feels at home to me.
 
Recording and editing are done in track view, of course. Way easier there.