<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Microsoft SQL Server Development Customer Advisory Team : SQL Server Analysis Service</title><link>http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Analysis+Service/default.aspx</link><description>Tags: SQL Server Analysis Service</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Ultimate guide to upgrading to SQL Server 2008</title><link>http://blogs.msdn.com/sqlcat/archive/2008/12/08/ultimate-guide-to-upgrading-to-sql-server-2008.aspx</link><pubDate>Mon, 08 Dec 2008 03:57:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9182995</guid><dc:creator>denny.lee</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/sqlcat/comments/9182995.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlcat/commentrss.aspx?PostID=9182995</wfw:commentRss><description>&lt;P&gt;For the ultimate guide to upgrading to SQL Server 2008, please refer to the &lt;A target=_blank href="http://www.microsoft.com/downloads/details.aspx?FamilyID=66d3e6f5-6902-4fdd-af75-9975aea5bea7&amp;amp;displaylang=en" mce_href="http://www.microsoft.com/downloads/details.aspx?FamilyID=66d3e6f5-6902-4fdd-af75-9975aea5bea7&amp;amp;displaylang=en"&gt;SQL Server 2008 Upgrade Technical Reference Guide&lt;/A&gt;.&lt;/P&gt;
&lt;DIV class=downloadInfo&gt;&lt;A name=Description&gt;&lt;/A&gt;&lt;SPAN&gt;A successful upgrade to SQL Server 2008 should be smooth and trouble-free. To achieve that smooth transition, you must devote plan sufficiently for the upgrade, and match the complexity of your database application. Otherwise, you risk costly and stressful errors and upgrade problems. Like all IT projects, planning for every contingency and then testing your plan gives you confidence that you will succeed. But if you ignore the planning process, you increase the chances of running into difficulties that can derail and delay your upgrade. This document covers the essential phases and steps involved in upgrading existing SQL Server 2000 and 2005 instances to SQL Server 2008 by using best practices. These include preparation tasks, upgrade tasks, and post-upgrade tasks. 
&lt;UL&gt;
&lt;LI&gt;Chapter 1 gives an overview of the technical issues and decisions that are involved in an upgrade to SQL Server 2008, as well as recommendations for planning and deploying an upgrade. 
&lt;LI&gt;Chapter 2 addresses issues related to upgrading to SQL Server 2008 Management Tools. 
&lt;LI&gt;Chapters 3 through 8 focus on upgrade issues for SQL Server relational databases. 
&lt;LI&gt;Chapter 9 addresses upgrading to SQL Server 2008 Express. 
&lt;LI&gt;Chapters 10 through 14 focus on upgrading to SQL Server 2008 Business Intelligence components: Analysis Services, Data Mining, Integration Services, and Reporting Services. 
&lt;LI&gt;Chapter 15 addresses the implications of upgrading to SQL Server 2008 for other Microsoft applications and platforms. 
&lt;LI&gt;Appendix 1 contains a table of allowed SQL Server 2008 version and edition upgrade paths. 
&lt;LI&gt;Appendix 2 contains an upgrade planning checklist. &lt;/LI&gt;&lt;/UL&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9182995" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Best+Practices/default.aspx">SQL Server Best Practices</category><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SSIS/default.aspx">SSIS</category><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Reporting+Services/default.aspx">SQL Server Reporting Services</category><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Analysis+Service/default.aspx">SQL Server Analysis Service</category></item><item><title>New Best Practices Articles Published - Running Microsoft SQL Server 2008 Analysis Services on Windows Server 2008 vs. Windows Server 2003 and Memory Preallocation: Lessons Learned</title><link>http://blogs.msdn.com/sqlcat/archive/2008/07/16/new-best-practices-articles-published-running-microsoft-sql-server-2008-analysis-services-on-windows-server-2008-vs-windows-server-2003-and-memory-preallocation-lessons-learned.aspx</link><pubDate>Wed, 16 Jul 2008 21:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8739754</guid><dc:creator>carl.rabeler</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sqlcat/comments/8739754.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlcat/commentrss.aspx?PostID=8739754</wfw:commentRss><description>&lt;P&gt;Due to the improvements in the Windows Server 2008 memory manager related to the change in the algorithm for scanning pages in memory, SQL Server 2008 Analysis Services performed equally well during both partition and dimension processing with or without memory preallocation when running on Windows Server 2008. However, SQL Server 2008 Analysis Services performed substantially better during both partition and dimension processing with the use of the memory preallocation configuration setting when running on Windows Server 2003. Specifically, the processing performance of Analysis Services 2008 without memory preallocation on Windows Server 2008 was virtually identical to the processing performance of Analysis Services 2008 on Windows Server 2003 with memory preallocation. With the hardware that we used in our tests and with the Analysis Services objects that we processed, we observed a performance benefit of approximately 100% during partition processing and a performance benefit of between 30-40% during dimension processing.&lt;/P&gt;
&lt;P&gt;If you use memory preallocation with SQL Server 2008 (or SQL Server 2005), use a value that is low enough to ensure that sufficient memory remains for other processes on the computer (avoiding paging) and high enough for Analysis Services (use the peak value for the Process: Private Bytes counter for the msmdsrv instance to establish this value).&lt;/P&gt;
&lt;P&gt;&lt;B&gt;Note&lt;/B&gt;: While we did not specifically test SQL Server 2005 Analysis Services for this technical note, the results discussed here apply to Analysis Services 2005 as well as to Analysis Services 2008 because the underlying code base for the portion of Analysis Services 2008 that we tested has not changed. &lt;/P&gt;
&lt;P&gt;&lt;A href="http://sqlcat.com/technicalnotes/archive/2008/07/16/running-microsoft-sql-server-2008-analysis-services-on-windows-server-2008-vs-windows-server-2003-and-memory-preallocation-lessons-learned.aspx"&gt;http://sqlcat.com/technicalnotes/archive/2008/07/16/running-microsoft-sql-server-2008-analysis-services-on-windows-server-2008-vs-windows-server-2003-and-memory-preallocation-lessons-learned.aspx&lt;/A&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8739754" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Best+Practices/default.aspx">SQL Server Best Practices</category><category domain="http://blogs.msdn.com/sqlcat/archive/tags/SQL+Server+Analysis+Service/default.aspx">SQL Server Analysis Service</category></item></channel></rss>