padding property RS 2005

Anyone notice that the padding property doesn't seem to work as nice as RS 2000? When I select more than one cell or row, and try to set the padding to 1,1,1,1, by typing the values in the property field (as opposed to expanding it and entering it in each side), it sometimes it gives me the following error:

'RptPaddingConverter' is unable to convert 'Microsoft.ReportDesigner.Drawing.ReportPadding' to 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.

Other times it works. This has always worked in RS 2000. It is more of a time-consuming annoyance than anything because then I have to go into each cell individually and change the padding, one by one.

This issue was fixed in SQL 2005 SP1|||Great. We were going to install it this week anyway. Thanks.|||Hello,

I can't confirm that the problem is solved. I work with SQL Server 2005 Standard Edition with Service Pack 1 installed. When selecting more than one cell in a table and modifying any of the padding-properties I get the error message (freely adapted from the german error message): "invalid property value". The details: RptPaddingConverter cannot convert Microsoft.ReportDesigner.Drawing.ReportPadding to System.ComponentModel.Design.Serialization.InstanceDescriptor.

regards,
Gerald

|||Please check version of Report Designer (in Help -> About)|||Microsoft Visual Studio 2005
Version 8.0.507277.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
SQL Server Reporting Services
Designer for Microsoft SQL Server Reporting Services
Version 9.00.2047.00

padding property RS 2005

Anyone notice that the padding property doesn't seem to work as nice as RS 2000? When I select more than one cell or row, and try to set the padding to 1,1,1,1, by typing the values in the property field (as opposed to expanding it and entering it in each side), it sometimes it gives me the following error:

'RptPaddingConverter' is unable to convert 'Microsoft.ReportDesigner.Drawing.ReportPadding' to 'System.ComponentModel.Design.Serialization.InstanceDescriptor'.

Other times it works. This has always worked in RS 2000. It is more of a time-consuming annoyance than anything because then I have to go into each cell individually and change the padding, one by one.

This issue was fixed in SQL 2005 SP1|||Great. We were going to install it this week anyway. Thanks.|||Hello,

I can't confirm that the problem is solved. I work with SQL Server 2005 Standard Edition with Service Pack 1 installed. When selecting more than one cell in a table and modifying any of the padding-properties I get the error message (freely adapted from the german error message): "invalid property value". The details: RptPaddingConverter cannot convert Microsoft.ReportDesigner.Drawing.ReportPadding to System.ComponentModel.Design.Serialization.InstanceDescriptor.

regards,
Gerald

|||Please check version of Report Designer (in Help -> About)|||Microsoft Visual Studio 2005
Version 8.0.507277.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
SQL Server Reporting Services
Designer for Microsoft SQL Server Reporting Services
Version 9.00.2047.00sql

Padding Issue

We are creating hierarchical report showing line of sight for given Organization. The report data is tree structure. Each node is a row in the report. Each row in the report is nested by using padding expression. Padding expression is based on Node Level. When we print report or create PDF padding is removed and all the rows appear aligned. It looks like reporting Services treat padding as white space. We tried several options like using gif images and rectangle but failed.

The report appears fine when we export to Web Archive, the working sample and sample with issue are as attached.

This issue occurs both in report viewer control and report services url.

Does "Padding expression" mean that you insert whitespace based on the node level?

There is another way of doing this: Every textbox has a Padding.Left property. Assuming that the node level is available as a numeric field value, you could set the Padding.Left property dynamically: =CStr(4 * Fields!NodeLevel.Value) & " pt"

-- Robert

|||

Thanks for the reply

I have tried both padding.left and padding.right. When report is rendered padding appears fine but on print or export to pdf, padding is removed.

|||

Which version of Reporting Services are you using? Did you install the latest service packs for that version?

-- Robert

Package failure still causing partial load

I have a package that is failing because of a truncation error. Now, by default (and I leave this for ALL my packages) if one row fails processing the entire package should fail and nothing gets loaded into db. But instead I am actually getting a partial db load.

I have confirmed the "Rows per btach" value (blank) and the "Maximum insert commit size" value (0) for the OLE DB Destination Editor so I have no idea what is going on. Are there any other properties I should be checking?

Thanks.

Jason

Why are you surprised that there is a partial load? You'll have to set MICS to equal to or greater than the number of rows coming into the source to have it such that if one row is bad, the whole batch is aborted.

The settings you have now are likely committing each row as they are inserted.|||According to the documentation, a "value of 0 indicates that all data is committed in a single batch after all rows have been processed". This, to me, tells me that all rows will be written or none. Since I am getting a truncation error, should I not be getting zero rows written?|||Well, I'm not so sure that SQL Server can accept an arbitrarily large bulk load. That is, I believe there's a limit to the size of the batch, and if it's exceeded, it will have to issue a commit or fail. I'm not sure.

You could redirect error rows out of the OLE DB command and try to see where that error occurs (row number or something).|||

Thanks for the responses Phil.

I know exactly where the error is happening. Just that in the past (with other packages) the execution loaded everything or nothing. (No matter the number of rows in the source.) It is just that the behavior for this package is not what I am used to and I cannot figure out why it is doing a partial load when the settings (as far as I can tell) are telling it not to.

- Jason

|||

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

|||

Rafael Salas wrote:

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

I think that SQL Server can only handle a batch size of 256 MB.

http://msdn2.microsoft.com/en-us/library/ms143432.aspx