<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>SQLPartitionMgmt Work Item Rss Feed</title><link>http://www.codeplex.com/SQLPartitionMgmt/WorkItem/List.aspx</link><description>SQLPartitionMgmt Work Item Rss Description</description><item><title>Created Issue: compression on partitions seems to be ignored [5338]</title><link>http://sqlpartitionmgmt.codeplex.com/WorkItem/View.aspx?WorkItemId=5338</link><description>Scripting a partitioned temp&amp;#47;staging table does not include reference to source table&amp;#39;s level of page level compression.&lt;br /&gt;</description><author>binarymechanic</author><pubDate>Mon, 26 Oct 2009 19:11:28 GMT</pubDate><guid isPermaLink="false">Created Issue: compression on partitions seems to be ignored [5338] 20091026071128P</guid></item><item><title>Created Issue: Partition functions with a '.' in its name are not handled properly (and maybe so do the partition schemes). [5337]</title><link>http://sqlpartitionmgmt.codeplex.com/WorkItem/View.aspx?WorkItemId=5337</link><description>You can create a partition function with CREATE PARTITION FUNCTION &amp;#91;Person.PF_Address&amp;#93;&amp;#40;int&amp;#41; RANGE LEFT FOR VALUES &amp;#40;10000, 20000, 30000&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;This function will not be handled properly due to the dot &amp;#40;&amp;#39;.&amp;#39;&amp;#41; in the name. It should work if you quote the name of the partition function with &amp;#39;&amp;#91;&amp;#39; and &amp;#39;&amp;#93;&amp;#39;. Maybe the same error will rise with a partition scheme with a dot inside the name.&lt;br /&gt;&lt;br /&gt;Workaround&amp;#58; Changing the name of the partition function &amp;#40;e.g. replace all &amp;#39;.&amp;#39; with &amp;#39;_&amp;#39;&amp;#41;.&lt;br /&gt;</description><author>MiSchroe</author><pubDate>Mon, 26 Oct 2009 17:00:49 GMT</pubDate><guid isPermaLink="false">Created Issue: Partition functions with a '.' in its name are not handled properly (and maybe so do the partition schemes). [5337] 20091026050049P</guid></item><item><title>Closed Issue: Release 1.0 known issues: index creation order; 10-min. timeout</title><link>http://www.codeplex.com/sql2005partitionmgmt/WorkItem/View.aspx?WorkItemId=3214</link><description>The following are known issues for Release 1.0. I&amp;#39;ve been informed by the developer&amp;#40;s&amp;#41; that these issues will be remedied with the next release, slated for 2008 Q4. The next release will also provide support for SQL Server 2008.&lt;br /&gt;&lt;br /&gt;&amp;#42; There is no order enforced when building indexes, whereas it would be advantageous to create clustered indexes before creating nonclustered indexes on a non-empty table.&lt;br /&gt;&lt;br /&gt;&amp;#42; Issued statements are given 10 minutes to run before failing with a time-out error. For example, if an individual index requires more than 10 minutes to create, an error will occur at the 10-minute mark. The remedy is to explicitly set the ServerConnection.StatementTimeout property to an appropriate value higher than the default value&amp;#59; the default value for this property is 600 &amp;#40;seconds, or 10 minutes&amp;#41;.&lt;br /&gt;&lt;br /&gt;Thanks to the developer&amp;#40;s&amp;#41; for such a valuable utility.&lt;br /&gt;Comments: Fixed with Release 2.0</description><author>Stuarto</author><pubDate>Mon, 23 Feb 2009 20:25:48 GMT</pubDate><guid isPermaLink="false">Closed Issue: Release 1.0 known issues: index creation order; 10-min. timeout 20090223082548P</guid></item><item><title>Created Issue: Release 1.0 known issues: index creation order; 10-min. timeout</title><link>http://www.codeplex.com/sql2005partitionmgmt/WorkItem/View.aspx?WorkItemId=3214</link><description>The following are known issues for Release 1.0. I&amp;#39;ve been informed by the developer&amp;#40;s&amp;#41; that these issues will be remedied with the next release, slated for 2008 Q4. The next release will also provide support for SQL Server 2008.&lt;br /&gt;&lt;br /&gt;&amp;#42; There is no order enforced when building indexes, whereas it would be advantageous to create clustered indexes before creating nonclustered indexes on a non-empty table.&lt;br /&gt;&lt;br /&gt;&amp;#42; Issued statements are given 10 minutes to run before failing with a time-out error. For example, if an individual index requires more than 10 minutes to create, an error will occur at the 10-minute mark. The remedy is to explicitly set the ServerConnection.StatementTimeout property to an appropriate value higher than the default value&amp;#59; the default value for this property is 600 &amp;#40;seconds, or 10 minutes&amp;#41;.&lt;br /&gt;&lt;br /&gt;Thanks to the developer&amp;#40;s&amp;#41; for such a valuable utility.&lt;br /&gt;</description><author>TJY</author><pubDate>Thu, 09 Oct 2008 03:03:46 GMT</pubDate><guid isPermaLink="false">Created Issue: Release 1.0 known issues: index creation order; 10-min. timeout 20081009030346A</guid></item></channel></rss>