Mark, just going through some of your content since you contacted me today. All I can say is that we use a lot of text table views, and are often working with hundreds of thousands of rows of data--and I have never noticed this issue, including when I have increased the maximum number of columns showing.
Are you utilizing an extract that is automatically refreshed periodically? I would think this would alleviate any processing problems like this on Server, but I could be misunderstanding the problem.
Have you contacted support on this one?
Thanks for resurfacing this one--as I had never closed it on the forums. I actually did contact Tableau support. The issue was limited to the Google Chrome and Mozilla Firefox browsers, Internet Explorer handled it OK, and support helped me correct the issue.
In Tableau 8, viz rendering defaults to be pushed out to the browser level. In Tableau 7, it always occurred on the server side. There is a url parameter (?:render=false) that be added to the url of the view to control case by case the setting of rendering at the browser level and essentially force the server to render the viz. When I added that url to my, everything worked just fine.
Additionally, there is a way to set up Tableau Server so that ALL vizzes (sp?) on the server render on the server side using a couple Tabadmin controls (must Run as Administrator command prompt on server, and change directory to the Tableau Server bin directory):
1. Tabadmin Stop
2. Tabadmin set vizqlserver.browser.render false
3. Tabadmin configure
4. Tabadmin Start
The issue was not related to the additional dimension pills allowed on the text view.