making reports with xml data source

Can i make a report from non sql-server data source ?
To be specific:
I have an xml data source, and i built the dataset from the xml,by VIsual
Studio -DotNet [by Code],
can i bound reporting services 2000 to this dataset as datasource?
if NO, can we do it in sql server Reporting Services 2005?
thanks in advanced
Oren.On Sun, 10 Apr 2005 00:11:05 -0700, Oren Said <Oren
Said@.discussions.microsoft.com> wrote:
>Can i make a report from non sql-server data source ?
>To be specific:
>I have an xml data source, and i built the dataset from the xml,by VIsual
>Studio -DotNet [by Code],
>can i bound reporting services 2000 to this dataset as datasource?
>if NO, can we do it in sql server Reporting Services 2005?
>thanks in advanced
>Oren.
See, "Using an External Dataset with Reporting Services" in BOL for RS
2000.
Andrew Watt
MVP - InfoPath|||The new controls (available with beta 2 of Widbey) should allow this. Unitl
the controls are out and being used I'm not guaranteeing that but it is my
understanding that they will allow this (both a web and winform control
will be available).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Oren Said" <Oren Said@.discussions.microsoft.com> wrote in message
news:B8E667B7-78EA-4A2F-92FC-9B230ABCCE6A@.microsoft.com...
> Can i make a report from non sql-server data source ?
> To be specific:
> I have an xml data source, and i built the dataset from the xml,by VIsual
> Studio -DotNet [by Code],
> can i bound reporting services 2000 to this dataset as datasource?
> if NO, can we do it in sql server Reporting Services 2005?
> thanks in advanced
> Oren.|||Here are some options for today:
Customize your own XML datasource for SQL Server 2000, and cosume the
webservice from SQL and acces those objects from the report (SQLRS)
Customize you own BOL for use XML as datasources, (make sure your BOL
support more than 10k records)
Wait for SQL 2005, certainly MS will have something available (its the
promess)
Thanks
Jerry
--
Call a WebService from SQL Server 2000
http://www.rdlcomponents.com/EXSP/default.aspx
WebService Data Processing Extension
http://www.rdlcomponents.com/DTE/Default.aspx
"Bruce L-C [MVP]" wrote:
> The new controls (available with beta 2 of Widbey) should allow this. Unitl
> the controls are out and being used I'm not guaranteeing that but it is my
> understanding that they will allow this (both a web and winform control
> will be available).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Oren Said" <Oren Said@.discussions.microsoft.com> wrote in message
> news:B8E667B7-78EA-4A2F-92FC-9B230ABCCE6A@.microsoft.com...
> >
> > Can i make a report from non sql-server data source ?
> >
> > To be specific:
> >
> > I have an xml data source, and i built the dataset from the xml,by VIsual
> > Studio -DotNet [by Code],
> > can i bound reporting services 2000 to this dataset as datasource?
> >
> > if NO, can we do it in sql server Reporting Services 2005?
> >
> > thanks in advanced
> >
> > Oren.
>
>sql

Making a create statement from existing database

We have a Peoplesoft application built over MS server 2000. The peoplesoft
application has created a table in ms server via its application designer
where the field types, sizes, indexes are automatically generated from the
data dictionary and search keys etc.
What I would like to know is how can I inquire via query analyser the
structure of these tables ( sort of reverse enginering the SQL DDL statement
s
) so that I can then end up with an SQL create statement etc.
thanks.listTableColumns should get you pretty close:
http://www.aspfaq.com/2177
"JD" <JD@.discussions.microsoft.com> wrote in message
news:56C8824E-D60E-4965-A62F-55B893D8F7F4@.microsoft.com...
> We have a Peoplesoft application built over MS server 2000. The peoplesoft
> application has created a table in ms server via its application designer
> where the field types, sizes, indexes are automatically generated from the
> data dictionary and search keys etc.
> What I would like to know is how can I inquire via query analyser the
> structure of these tables ( sort of reverse enginering the SQL DDL
> statements
> ) so that I can then end up with an SQL create statement etc.
> thanks.|||"JD" <JD@.discussions.microsoft.com> wrote in message
news:56C8824E-D60E-4965-A62F-55B893D8F7F4@.microsoft.com...
> We have a Peoplesoft application built over MS server 2000. The peoplesoft
> application has created a table in ms server via its application designer
> where the field types, sizes, indexes are automatically generated from the
> data dictionary and search keys etc.
> What I would like to know is how can I inquire via query analyser the
> structure of these tables ( sort of reverse enginering the SQL DDL
> statements
> ) so that I can then end up with an SQL create statement etc.
> thanks.
Take a look at INFORMATION_SCHEMA in the Books Online. In particular, you
will want to pay attention to INFORMATION_SCHEMA.TABLES and .COLUMNS.
As for the indexes and so forth, that will be a bit more tricky.
Rick Sawtell
MCT, MCSD, MCDBA|||If you can use Enterprise Manager, there is a wizard that generates scripts.
You can pick the specific table you're interested in and save it creation
script. There's options to include indexes, primary keys, etc.
Joe
"Aaron Bertrand [SQL Server MVP]" wrote:

> listTableColumns should get you pretty close:
> http://www.aspfaq.com/2177
>
> "JD" <JD@.discussions.microsoft.com> wrote in message
> news:56C8824E-D60E-4965-A62F-55B893D8F7F4@.microsoft.com...
>
>|||Try Creating a SQL Script from Enterprise Manager. Save it and then open it
up with Query Analyzer
"JD" <JD@.discussions.microsoft.com> escribi en el mensaje
news:56C8824E-D60E-4965-A62F-55B893D8F7F4@.microsoft.com...
> We have a Peoplesoft application built over MS server 2000. The peoplesoft
> application has created a table in ms server via its application designer
> where the field types, sizes, indexes are automatically generated from the
> data dictionary and search keys etc.
> What I would like to know is how can I inquire via query analyser the
> structure of these tables ( sort of reverse enginering the SQL DDL
> statements
> ) so that I can then end up with an SQL create statement etc.
> thanks.

Major difficulties deploying a custom data extension

I have been trying for days to get a custmized data extension that I
built using the example at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/RSDSetEx3.asp
to be recognized by the report server on a Windows 2003 box. It is
recognized and works well on my development machine. I have followed
the recommended steps outlined below:
1) Create an entry in RSReportServer.config:
<Extension Name="Dataset"
Type="DataSetExtension.DSXConnection,RSCustomData"/>
DatesetExtension.DSXConnection is the correct namespace (I customized
it), RSCustomData.dll is the name of the assembly which has been placed
in the following folder:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin
2) Create a new code group entry in rssrvpolicy.config. This
potentially could be the source of the problem, as I have received
conflicting recommendations on where in the code group heirarchy I
should place the new entry. I am currently placing it under the
"Url="$CodeGen$/*" entry
3) Restarted IIS and restarted SQLServer. Is there any reason why the
PC should have to be restarted? When does RSReportServer.config and
rssrvpolicy.config get loaded?
I then created a web service client and called the ListExtensions
method of the resportservice.asmx web service. It only lists the
original 4 data extensions - SQL, OLEDB, ORACLE and ODBC. After
dozends of attempts over several days and after reinstalling Reporting
Services, I still am having no luck getting the data extension to be
recognized on the server. Even though it works great on the dev
machine and I can step through the code without a problem.
Bonus question: One post mentioned the
<securityPolicy>
<trustLevel name="RosettaSrv" policyFile="rssrvpolicy.config"
/>
</securityPolicy>
<trust level="RosettaSrv" originUrl="" />
entry in web.config as a potential source of the problem. Searches on
google for RosettaSrv turn up almost nothing. Does this have any
effect on giving permissions to custom assemblies?
Thanks in advance for your help.I worked with Microsoft and got the problem solved. It was a
permissions issue on the assembly that I copied from my development
machine to the reporting server. We used filemon.exe to show that the
assembly was not being loaded. Other notes from Microsoft:
"Resolution:
By adding read & execute permissions to the Report Server directory for
the Users group, and allowing parent permissions to propagate to the
custom dll in the bin directory, the report server was able to load the
custom dll and display the custom data extension. In resolving this
case we used FileMon from SysInternals.com.