Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapper now INTERNAL - by ExtinctPencil

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 549045 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/6/2010 8:35:58 AM
Access Restriction Public

Description

Hi I have a requirement to apply security filtering (column and row level) above and beyond the capabilities of SSRS Model security. in 2005 and 2008 I achieved this by creating a data Extension and tweaking the Command text and execute reader methods, and all was Well with the world. Now all I wanted was a bit of customisation of the SQL data Extension  (SQL Connection Wrapper)... of course its Sealed so couldn't inherit, so I composite / wrapped it... and all was well with the world......  Now along comes SQL2008 R2 .... and someone has discovered the internal Keyword !  now everything is locked down.  the Constructor of SQL Connection Wrapper  is internal Luckily my code is not yet producion code, and I know Microsoft are completely within their rights ... but why ... all is not good with the world.

Any suggestions how to implement a minor customisation to SQL data Extension, without reimplementing the whole of the dataExtensions DLL !

Any chance the decison might be reversed ?   
Sign in to post a comment.
Posted by Microsoft on 8/17/2010 at 1:22 PM
We are closing the issue on our side.
Feel free to file a new connect item or re-activate this one if you have further questions.
-Thanks
Posted by Microsoft on 8/9/2010 at 12:25 PM
Hi,
Thanks for filing the issue. The SQL extension is internal data extension and is changed to internal in KJ. If customization is needed, you will need to implement a new data extension. There is no other way to achieve this.
Please let us know if you have further questions.
-Thanks
Posted by 一炷香的时间 on 8/1/2010 at 7:13 AM
Extinctpencil的问题非常常见:Reporting Service在数据处理过程中,加一些自己的处理逻辑很正常,而不是重新把整个接口都自己实现一遍!!难道就没有针对在处理过程中加入自定义处理逻辑的扩展机制?这种机制对于微软来说应该不难吧!
Posted by 一炷香的时间 on 8/1/2010 at 7:00 AM
Resolved?? how? why no comments?