<?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>Renaming Olap Databases Issues within Analysis Services</title><link>http://blogs.msdn.com/b/sqlcat/archive/2007/07/30/renaming-olap-databases-issues-within-analysis-services.aspx</link><description>If you are view the XMLA script that is generated for an Analysis Services database, you will notice that there are both ID and NAME attributes. The reason Analysis Services has this differentiation is so one could rename an Olap database (which you could</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Analysis Services Synchronization Best Practices</title><link>http://blogs.msdn.com/b/sqlcat/archive/2007/07/30/renaming-olap-databases-issues-within-analysis-services.aspx#8238232</link><pubDate>Sun, 16 Mar 2008 07:19:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8238232</guid><dc:creator>Technical Notes</dc:creator><description>&lt;p&gt;Authors : Denny Lee, Edward Melomed, Mike Vovchik Contributors: Duy Vuong, Greg Washburn Reviewers :&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8238232" width="1" height="1"&gt;</description></item></channel></rss>