Data Processing Extension for ADO.NET?

Is there a data processing extension for use with an ADO.NET provider? MSDN
lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
omission.
The extension interfaces (IDbConnection, etc) are all similar to ADO.NET's.
I could write a pretty thin custom extension wrapper around an ADO.NET
provider, but why should I have to?Ah, it says you can use a .NET data provider directly from Reporting
Services, without a data processing extension. However, how do you let
Reporting Services know about your provider?
"Daniel Michaeloff" wrote:
> Is there a data processing extension for use with an ADO.NET provider? MSDN
> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> omission.
> The extension interfaces (IDbConnection, etc) are all similar to ADO.NET's.
> I could write a pretty thin custom extension wrapper around an ADO.NET
> provider, but why should I have to?|||When using a managed provider, you can either use it directly or write a
custom data extension which internally uses the provider. In general you can
use most .NET data providers (which implement System.Data.IDBConnection,
etc.). A .NET data provider would need to be registered in both,
rsReportDesigner.config and rsReportServer.config.
Lets assume your .NET provider has the assembly name "MyAssembly" and the
actual class that implements IDBConnection is called
"MyAssembly.MyConnection". Here is how you would register it:
* RSReportServer.config:
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
* RSReportDesigner.config
The registration for report designer would need to happen in two places - in
the <Data> section and in the <Designer> section.
<Data>
...
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
</Data>
<Designer>
...
<Extension Name="MyProvider"
Type="MyAssembly.MyConnection,MyAssembly"/>
</Designer>
After registering, you will get a new entry "MyProvider" in the data source
type drop-down list.
See also:
http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> Is there a data processing extension for use with an ADO.NET provider?
> MSDN
> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> omission.
> The extension interfaces (IDbConnection, etc) are all similar to
> ADO.NET's.
> I could write a pretty thin custom extension wrapper around an ADO.NET
> provider, but why should I have to?|||Correction to my posting below - the <Designer> element in
RSReportDesigner.config should have the following contents:
<Designer>
...
<Extension Name="MyProvider"
Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
</Designer>
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> When using a managed provider, you can either use it directly or write a
> custom data extension which internally uses the provider. In general you
> can use most .NET data providers (which implement
> System.Data.IDBConnection, etc.). A .NET data provider would need to be
> registered in both, rsReportDesigner.config and rsReportServer.config.
> Lets assume your .NET provider has the assembly name "MyAssembly" and the
> actual class that implements IDBConnection is called
> "MyAssembly.MyConnection". Here is how you would register it:
> * RSReportServer.config:
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> * RSReportDesigner.config
> The registration for report designer would need to happen in two places -
> in the <Data> section and in the <Designer> section.
> <Data>
> ...
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> </Data>
> <Designer>
> ...
> <Extension Name="MyProvider"
> Type="MyAssembly.MyConnection,MyAssembly"/>
> </Designer>
> After registering, you will get a new entry "MyProvider" in the data
> source type drop-down list.
> See also:
> http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
>> Is there a data processing extension for use with an ADO.NET provider?
>> MSDN
>> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
>> omission.
>> The extension interfaces (IDbConnection, etc) are all similar to
>> ADO.NET's.
>> I could write a pretty thin custom extension wrapper around an ADO.NET
>> provider, but why should I have to?
>|||Thanks Robert, this is what I needed.
However, is there a way to avoid putting our provider assemblies in the
global assembly cache?
"Robert Bruckner [MSFT]" wrote:
> Correction to my posting below - the <Designer> element in
> RSReportDesigner.config should have the following contents:
> <Designer>
> ...
> <Extension Name="MyProvider"
> Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> </Designer>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > When using a managed provider, you can either use it directly or write a
> > custom data extension which internally uses the provider. In general you
> > can use most .NET data providers (which implement
> > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > registered in both, rsReportDesigner.config and rsReportServer.config.
> >
> > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > actual class that implements IDBConnection is called
> > "MyAssembly.MyConnection". Here is how you would register it:
> > * RSReportServer.config:
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> >
> > * RSReportDesigner.config
> > The registration for report designer would need to happen in two places -
> > in the <Data> section and in the <Designer> section.
> >
> > <Data>
> > ...
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> > </Data>
> > <Designer>
> > ...
> > <Extension Name="MyProvider"
> > Type="MyAssembly.MyConnection,MyAssembly"/>
> > </Designer>
> >
> > After registering, you will get a new entry "MyProvider" in the data
> > source type drop-down list.
> >
> > See also:
> > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> >
> >
> > --
> > Robert M. Bruckner
> > Microsoft SQL Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
> >
> > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> >> Is there a data processing extension for use with an ADO.NET provider?
> >> MSDN
> >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> >> omission.
> >>
> >> The extension interfaces (IDbConnection, etc) are all similar to
> >> ADO.NET's.
> >> I could write a pretty thin custom extension wrapper around an ADO.NET
> >> provider, but why should I have to?
> >
> >
>
>|||Actually, I'm not getting Report Designer to pick up my assembly from the
GAC, and I don't see anything like "Microsoft.ReportingServices" in the GAC
either. I've also tried dropping my dll in Report Designer's main directory.
Where does Report Designer / Reporting Services look for extensions?
"Daniel Michaeloff" wrote:
> Thanks Robert, this is what I needed.
> However, is there a way to avoid putting our provider assemblies in the
> global assembly cache?
> "Robert Bruckner [MSFT]" wrote:
> > Correction to my posting below - the <Designer> element in
> > RSReportDesigner.config should have the following contents:
> >
> > <Designer>
> > ...
> > <Extension Name="MyProvider"
> > Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> > </Designer>
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> > news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > > When using a managed provider, you can either use it directly or write a
> > > custom data extension which internally uses the provider. In general you
> > > can use most .NET data providers (which implement
> > > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > > registered in both, rsReportDesigner.config and rsReportServer.config.
> > >
> > > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > > actual class that implements IDBConnection is called
> > > "MyAssembly.MyConnection". Here is how you would register it:
> > > * RSReportServer.config:
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > >
> > > * RSReportDesigner.config
> > > The registration for report designer would need to happen in two places -
> > > in the <Data> section and in the <Designer> section.
> > >
> > > <Data>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > </Data>
> > > <Designer>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > </Designer>
> > >
> > > After registering, you will get a new entry "MyProvider" in the data
> > > source type drop-down list.
> > >
> > > See also:
> > > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> > >
> > >
> > > --
> > > Robert M. Bruckner
> > > Microsoft SQL Server Reporting Services
> > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >
> > >
> > >
> > > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> > >> Is there a data processing extension for use with an ADO.NET provider?
> > >> MSDN
> > >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> > >> omission.
> > >>
> > >> The extension interfaces (IDbConnection, etc) are all similar to
> > >> ADO.NET's.
> > >> I could write a pretty thin custom extension wrapper around an ADO.NET
> > >> provider, but why should I have to?
> > >
> > >
> >
> >
> >|||Okay, I tried actually following that link you gave. Sorry.
"Daniel Michaeloff" wrote:
> Actually, I'm not getting Report Designer to pick up my assembly from the
> GAC, and I don't see anything like "Microsoft.ReportingServices" in the GAC
> either. I've also tried dropping my dll in Report Designer's main directory.
> Where does Report Designer / Reporting Services look for extensions?
> "Daniel Michaeloff" wrote:
> > Thanks Robert, this is what I needed.
> >
> > However, is there a way to avoid putting our provider assemblies in the
> > global assembly cache?
> >
> > "Robert Bruckner [MSFT]" wrote:
> >
> > > Correction to my posting below - the <Designer> element in
> > > RSReportDesigner.config should have the following contents:
> > >
> > > <Designer>
> > > ...
> > > <Extension Name="MyProvider"
> > > Type="Microsoft.ReportDesigner.Design.GQDQueryDesigner,Microsoft.ReportingServices.Designer"/>
> > > </Designer>
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > > "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> > > news:%23qgs5sXXFHA.3280@.TK2MSFTNGP09.phx.gbl...
> > > > When using a managed provider, you can either use it directly or write a
> > > > custom data extension which internally uses the provider. In general you
> > > > can use most .NET data providers (which implement
> > > > System.Data.IDBConnection, etc.). A .NET data provider would need to be
> > > > registered in both, rsReportDesigner.config and rsReportServer.config.
> > > >
> > > > Lets assume your .NET provider has the assembly name "MyAssembly" and the
> > > > actual class that implements IDBConnection is called
> > > > "MyAssembly.MyConnection". Here is how you would register it:
> > > > * RSReportServer.config:
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > >
> > > > * RSReportDesigner.config
> > > > The registration for report designer would need to happen in two places -
> > > > in the <Data> section and in the <Designer> section.
> > > >
> > > > <Data>
> > > > ...
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > > </Data>
> > > > <Designer>
> > > > ...
> > > > <Extension Name="MyProvider"
> > > > Type="MyAssembly.MyConnection,MyAssembly"/>
> > > > </Designer>
> > > >
> > > > After registering, you will get a new entry "MyProvider" in the data
> > > > source type drop-down list.
> > > >
> > > > See also:
> > > > http://msdn.microsoft.com/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> > > >
> > > >
> > > > --
> > > > Robert M. Bruckner
> > > > Microsoft SQL Server Reporting Services
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > > rights.
> > > >
> > > >
> > > >
> > > > "Daniel Michaeloff" <DanielMichaeloff@.discussions.microsoft.com> wrote in
> > > > message news:BD89B815-BC0E-4ABD-9A36-07F7B31A303B@.microsoft.com...
> > > >> Is there a data processing extension for use with an ADO.NET provider?
> > > >> MSDN
> > > >> lists ones for SQL Server, OLEDB, Oracle, and ODBC.. ADO.NET is a glaring
> > > >> omission.
> > > >>
> > > >> The extension interfaces (IDbConnection, etc) are all similar to
> > > >> ADO.NET's.
> > > >> I could write a pretty thin custom extension wrapper around an ADO.NET
> > > >> provider, but why should I have to?
> > > >
> > > >
> > >
> > >
> > >

Data not display in dropdown lists

I have 2 drop down lists in my report. When you select an item from
the 1st list, the 2nd list gets populated accordingly. For some
records in list 1 you get only a single record in the 2nd drop down.
In these cases, you don't see the item in the drop downlist, but I
tried checking in the source of the page n could see the particular
item. Any idea why this is happening?On Mar 1, 10:01 am, cham...@.gmail.com wrote:
> I have 2 drop down lists in my report. When you select an item from
> the 1st list, the 2nd list gets populated accordingly. For some
> records in list 1 you get only a single record in the 2nd drop down.
> In these cases, you don't see the item in the drop downlist, but I
> tried checking in the source of the page n could see the particular
> item. Any idea why this is happening?
It sounds kind of like you are returning a null value in the 2nd drop-
down list (and possibly the correct one after that). Have you checked
the dataset to determine what the possibilities are for the second
drop-down list given the first one's values?
Enrique Martinez
Sr. SQL Server Developer

Data Missing from Report

I have created a RS report that contains 2 datasets and 2 lists. This is a
consolidated corporate report grouped to return data for 53 companies (one
page per company). Both datasets return data for all 53 companies when
viewing from the data pane. However, when the report is viewed in the
preview pane (or rendered), the 1st dataset returns data for all 53
companies, but there are 8 of the companies missing data from the 2nd dataset.
The problem varies in severity depending on the Begin and End date
parameters used to generate the report. What is strange is that a narrower
date range (several days) leaves off more data than a broader date range
(full month).
Anyone have any ideas?Has anyone out there ever experienced data missing from a RS generated report
that is returned when the same query is run in Query Analyzer?
"Lynn" wrote:
> I have created a RS report that contains 2 datasets and 2 lists. This is a
> consolidated corporate report grouped to return data for 53 companies (one
> page per company). Both datasets return data for all 53 companies when
> viewing from the data pane. However, when the report is viewed in the
> preview pane (or rendered), the 1st dataset returns data for all 53
> companies, but there are 8 of the companies missing data from the 2nd dataset.
> The problem varies in severity depending on the Begin and End date
> parameters used to generate the report. What is strange is that a narrower
> date range (several days) leaves off more data than a broader date range
> (full month).
> Anyone have any ideas?
>
>