x

Migrating a custom data extension to SQL Server 2008 R2 Reporting Services

We are in the process of migrating from SQL Server 2008 Reporting Services to SQL Server 2008 R2 Reporting Services. The only issue I have is migrating a custom data extension. I copied the custom dll to the bin files and made the changes to the various config files. The custom extension doesn’t appear in the data source type drop down in Report Manager. Does the dll need to be recompiled and then copied to the bin folders? If so, what steps are required to recompile the dll so the SQL Server 2008 R2 Reporting Services can use it? Thanks for any help on this.
more ▼

asked Sep 11 '12 at 06:33 PM in Default

PAMatt gravatar image

PAMatt
0 1 1 1

(comments are locked)
10|1200 characters needed characters left

2 answers: sort voted first

There is a details article on MSDN that gives you step-by-step instructions.

Let us know how it goes.

more ▼

answered Sep 12 '12 at 07:27 AM

sp_lock gravatar image

sp_lock
9k 24 27 30

(comments are locked)
10|1200 characters needed characters left

Followed all these steps to a tee... the bottom line being that the dll was created under 2008 and I believe it needs to be recompiled under 2008 r2. Running the upgrade advisor on the old SQL Server 2008 reporting services instance seems to confirm this.

The MSDN article doesn’t mention that custom data extensions probably need to be recompiled. Here’s a copy of the section that addresses this:

If your installation includes custom report items, assemblies, or extensions, you must redeploy the custom components. If you are not using custom components, skip to "Configure the Report Server".

To redeploy the custom components, do the following:

  1. Determine whether the assemblies are supported or need recompilation: • Custom authentication extensions created for the SQL Server 2000 release must be recompiled. • Custom rendering extensions for SQL Server 2008 Reporting Services must be rewritten using the Rendering Object Model (ROM). • HTML 3.2 and HTML OWC renderers are not supported in SQL Server 2008 Reporting Services. • Other custom assemblies should not require recompilation.
That said, I am working with the applications developer group to try the recompile.
more ▼

answered Sep 12 '12 at 11:31 AM

PAMatt gravatar image

PAMatt
0 1 1 1

Did you add the Extension elements in RSReportServer.config for the report server and RSReportDesigner.config for Report Designer?
Sep 12 '12 at 11:41 AM Usman Butt

Sure did...

We've been using custom data extensions for years and the migration from 2005 to 2008 went smoothly. I did see some postings that indicated some changes between how SQL Server 2008 and SQL Server 2008 R2 use/manage custom data extensions.

I'm going to try the recompile and see what happens.
Sep 12 '12 at 11:50 AM PAMatt
(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x535

asked: Sep 11 '12 at 06:33 PM

Seen: 826 times

Last Updated: Sep 12 '12 at 12:30 PM