SQLPartitionMgmt Work Item Rss Feed

Created Issue: bug in exception management [9870]

smurru — Thu, 24 Jan 2013 10:12:27 GMT

A new bug was introduced in ManagePartition.exe version 3.0.

The bug is located in the Run() method exceptionn handler at line number 235

```
}
catch (Exception e)
{
sc.Disconnect();
sc = null;
Console.WriteLine(e);
}
sc.Disconnect();
sc = null;

```
when an exception occurs, the exception handler sets sc = null
then the sc.Disconnect(); following the catch block fails with an "Object reference not set to an instance of an object", that is caught in the Main() exception handler level, instead of the real exception.

in version 2.0 a there was a throw at the end of the catch block.

```
catch (Exception ex)
{
sc.Disconnect();
sc = null;
throw ex;
}
sc.Disconnect();
sc = null;

```

Closed Issue: Invalid Constraints when server not using US format dates [5782]

Stuarto — Thu, 29 Nov 2012 04:46:22 GMT

Hello,
 
Love this util. But I had a major issue with it. Being outside the US of A, I don't use MM/dd/YYYY format dates. Because I run into a lot of US dates format/converting problems I set all my SQL servers to use ISO like date format, yyyy-MM-dd. Also avoids user confusion with reports..
 
I found that your util can create invalid constraints on the slide out tables (and presumable will do the same on the staging) as it inserts the constraints in American style formatted dates. This causes the util to create a slide out table that can't have partition data switched to. I've updated the CreateStgPartitionCheck() in the source code so that if the partition column is SqlDateType.DateTime (The only sql data type I use for partitioning..) then it will properly format the string and works ok for me now.
 
So now the construct for the min value predicate looks a little like this: 
 
// Construct the minimum value predicate string in the check constraint definition
 if (partitionNumber > 1)
 // 2010-01-22 Added By Yussuf Khan so it can cope with non US format DateTime formats (I don't use other datatypes for my partition columns so only coding datetime)
 if (partitionColumnType == SqlDataType.DateTime)
 {
 //now it seems for datetime it will return this in US format, dd/MM/yyyy
 //need to convert to more universal standard, yyyy-MM-dd , which SQL server detects ok no matter what the locale (well in my experience anyways!)
 dtDateBuilder = (DateTime)pf.RangeValues[partitionNumber - 2];
 strDateBuilder = dtDateBuilder.ToString("yyyy-MM-dd hh:mm:ss.fff");
 leftBoundary = partitionColumnName + ((pf.RangeType == RangeType.Right) ? ">=" : ">") + "N'" + strDateBuilder + "'";
 }
 else if (
 (partitionColumnType == SqlDataType.Date) ||
 (partitionColumnType == SqlDataType.Time) ||
 
I've done a similiar thing to the Max value string constraint builder too. I'm not really a .Net developer, and I've only tested a couple of times. But this does seem to fix. Any chance you can incorporate something like this fully?

Comments:

Fixed in Version 3.0

Closed Issue: compression on partitions seems to be ignored [5338]

Stuarto — Wed, 21 Nov 2012 22:27:46 GMT

Scripting a partitioned temp/staging table does not include reference to source table's level of page level compression.

Comments:

I verified that this is not a problem in Partition Management Utility version 2. If you are continuing to find issues in compression being set correctly, please send me a script of original objects and the script of objects created by the tool.

Closed Issue: Partition functions with a '.' in its name are not handled properly (and maybe so do the partition schemes). [5337]

Stuarto — Wed, 21 Nov 2012 22:26:07 GMT

You can create a partition function with CREATE PARTITION FUNCTION [Person.PF_Address](int) RANGE LEFT FOR VALUES (10000, 20000, 30000);
 
This function will not be handled properly due to the dot ('.') in the name. It should work if you quote the name of the partition function with '[' and ']'. Maybe the same error will rise with a partition scheme with a dot inside the name.
 
Workaround: Changing the name of the partition function (e.g. replace all '.' with '_').

Comments:

I verified that this is not a problem with Partition Management Utility Version 2. Partition functions and schemes with "." characters are handled fine. If you have a continuing problem please send specific script with repro details.

Commented Issue: Invalid Constraints when server not using US format dates [5782]

Stuarto — Wed, 27 Jan 2010 16:20:51 GMT

Hello,

Love this util. But I had a major issue with it. Being outside the US of A, I don't use MM/dd/YYYY format dates. Because I run into a lot of US dates format/converting problems I set all my SQL servers to use ISO like date format, yyyy-MM-dd. Also avoids user confusion with reports..

I found that your util can create invalid constraints on the slide out tables (and presumable will do the same on the staging) as it inserts the constraints in American style formatted dates. This causes the util to create a slide out table that can't have partition data switched to. I've updated the CreateStgPartitionCheck() in the source code so that if the partition column is SqlDateType.DateTime (The only sql data type I use for partitioning..) then it will properly format the string and works ok for me now.

So now the construct for the min value predicate looks a little like this:

// Construct the minimum value predicate string in the check constraint definition
if (partitionNumber > 1)
// 2010-01-22 Added By Yussuf Khan so it can cope with non US format DateTime formats (I don't use other datatypes for my partition columns so only coding datetime)
if (partitionColumnType == SqlDataType.DateTime)
{
//now it seems for datetime it will return this in US format, dd/MM/yyyy
//need to convert to more universal standard, yyyy-MM-dd , which SQL server detects ok no matter what the locale (well in my experience anyways!)
dtDateBuilder = (DateTime)pf.RangeValues[partitionNumber - 2];
strDateBuilder = dtDateBuilder.ToString("yyyy-MM-dd hh:mm:ss.fff");
leftBoundary = partitionColumnName + ((pf.RangeType == RangeType.Right) ? ">=" : ">") + "N'" + strDateBuilder + "'";
}
else if (
(partitionColumnType == SqlDataType.Date) ||
(partitionColumnType == SqlDataType.Time) ||

I've done a similiar thing to the Max value string constraint builder too. I'm not really a .Net developer, and I've only tested a couple of times. But this does seem to fix. Any chance you can incorporate something like this fully?
Comments: ** Comment from web user: Stuarto **

Thank you for the feedback. I was surprised to see that the pf.RangeValue was not already formatted in the locale-specific formulation. I will incorporate this change in a subsequent build after testing more completely.

Created Issue: Invalid Constraints when server not using US format dates [5782]

WeeeBob — Fri, 22 Jan 2010 16:06:26 GMT

Created Issue: compression on partitions seems to be ignored [5338]

binarymechanic — Mon, 26 Oct 2009 19:11:28 GMT

Scripting a partitioned temp/staging table does not include reference to source table's level of page level compression.

Created Issue: Partition functions with a '.' in its name are not handled properly (and maybe so do the partition schemes). [5337]

MiSchroe — Mon, 26 Oct 2009 17:00:49 GMT

You can create a partition function with CREATE PARTITION FUNCTION [Person.PF_Address](int) RANGE LEFT FOR VALUES (10000, 20000, 30000);

This function will not be handled properly due to the dot ('.') in the name. It should work if you quote the name of the partition function with '[' and ']'. Maybe the same error will rise with a partition scheme with a dot inside the name.

Workaround: Changing the name of the partition function (e.g. replace all '.' with '_').

Closed Issue: Release 1.0 known issues: index creation order; 10-min. timeout

Stuarto — Mon, 23 Feb 2009 20:25:48 GMT

The following are known issues for Release 1.0. I've been informed by the developer(s) 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.

* 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.

* 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; the default value for this property is 600 (seconds, or 10 minutes).

Thanks to the developer(s) for such a valuable utility.
Comments: Fixed with Release 2.0

Created Issue: Release 1.0 known issues: index creation order; 10-min. timeout

TJY — Thu, 09 Oct 2008 03:03:46 GMT