So I see all these great posts during the week and I think, “I wonder if everyone else is seeing this

Pingback from  Tour Guide at the Khajuraho temples India 2007

Pingback from  SQL Server 2008 White Paper: Analysis Services Performance Guide | Kasper de Jonge BI Blog

Author: Carl Rabeler Contributor: Josh Caplan Reviewers: Prem Mehra, Denny Lee, John Desch, Wayne Robertson

I have recently downloaded the SSAS Performance Guide 2008 from microsoft.com.

As I started reading the document, and trying to get deeper into things, I however found that some of the links were dead.

The reason for this is, that all (correct me if I'm wrong) self-referencing links (links to anchors in the same document) is refering to a document on a local machine with the given path of: C:\Users\Beth\Documents\Vend\Docs\SQL White papers\SSASPerfGuide2008_v1_(2).docx

The issue is not critical, but I thought I'd let you know.

SQL Server Technical Article Authors : Denny Lee, Kay Unkroth Contributor : James Podgorski Technical

Quick question. The whitepaper recommends using a network packet size of 32K, but the figure shows a packet size of 32767 which would be 1 byte less than 32K. Is there a particular reason to use 32767 instead of 32768?

I ask because our engineering team wants to use a packet size of 32240. When I asked why they want to use a non-even packet size, they referenced a different whitepaper that recommends a packet size of 32K but then shows 32240 in the picture. I suggested they use this whitepaper instead for reference, but I am curious about thy the demonstrated value isn't exactly 32K.