Showing posts with label export. Show all posts
Showing posts with label export. Show all posts

Monday, March 19, 2012

New ReportViewer Component

Hello,
It seems it is possible to export to export to pdf through ReportViewer in
SQL Server 2005 and VS 2005. Is it possible to use â'Microsoft Report Viewer
Redistributable 2005â' in VS.Net 2003 and SQL Server 2000 and use it to export
pdf automatically?The new controls are based on the 2.0 framework. VS.Net 2003 and RS 2000 are
1.1 framework. You cannot use the controls in VS 2003. Also, you cannot use
the controls against RS 2000. The VS 2005 controls only work in VS 2005 with
RS 2005 reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:F932E66E-6BC1-4579-ABD0-36F193A056E7@.microsoft.com...
> Hello,
> It seems it is possible to export to export to pdf through ReportViewer in
> SQL Server 2005 and VS 2005. Is it possible to use "Microsoft Report
> Viewer
> Redistributable 2005" in VS.Net 2003 and SQL Server 2000 and use it to
> export
> pdf automatically?
>

Wednesday, March 7, 2012

New Import/Export Wizard error

I am making the adjustment from SQL Server 2000 to SQL Server 2005. In the
past I have created named ranges in Excel that look like data tables (header
row followed by multiple data rows) and used DTS to create database tables i
n
SQL Server 2000. It has worked for several years. Now, using the SQL
Server 2005 import/export wizard, the same named ranges cause the following
error.
- Validating (Error)
Messages
Error 0xc00470fe: Data Flow Task: The product level is insufficient for
component "Source - B11Tbl" (1).
(SQL Server Import and Export Wizard)
Can anyone explain why it 'blows-up' and what I might do to fix it?
Thank you!Hi Mitch
Which version are you running?
John
"Mitch" wrote:

> I am making the adjustment from SQL Server 2000 to SQL Server 2005. In th
e
> past I have created named ranges in Excel that look like data tables (head
er
> row followed by multiple data rows) and used DTS to create database tables
in
> SQL Server 2000. It has worked for several years. Now, using the SQL
> Server 2005 import/export wizard, the same named ranges cause the followin
g
> error.
> - Validating (Error)
> Messages
> Error 0xc00470fe: Data Flow Task: The product level is insufficient f
or
> component "Source - B11Tbl" (1).
> (SQL Server Import and Export Wizard)
> Can anyone explain why it 'blows-up' and what I might do to fix it?
> Thank you!
>|||Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
I hope this gives the version info needed.
Mitch
"John Bell" wrote:
> Hi Mitch
> Which version are you running?
> John
> "Mitch" wrote:
>|||Hi
That does not tell me the edition!
You may want to test if it works with SP1.
John
"Mitch" wrote:
> Microsoft SQL Server Management Studio 9.00.1399.00
> Microsoft Analysis Services Client Tools 2005.090.1399.00
> Microsoft Data Access Components (MDAC) 2000.085.1117.00
> (xpsp_sp2_rtm.040803-2158)
> Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
> Microsoft Internet Explorer 6.0.2900.2180
> Microsoft .NET Framework 2.0.50727.42
> Operating System 5.1.2600
> I hope this gives the version info needed.
> Mitch
> "John Bell" wrote:
>|||Microsoft SQL Server Standard Edition
"John Bell" wrote:
> Hi
> That does not tell me the edition!
> You may want to test if it works with SP1.
> John
> "Mitch" wrote:
>|||Hi Mitch
Then I can't see why you are getting this message! Have you tried this
without the named ranges or a different version of Excel?
John
"Mitch" wrote:
> Microsoft SQL Server Standard Edition
> "John Bell" wrote:
>|||I'll have the IT people check the installation settings for SQL Server 2005.
The 2000 version of DTS still works just fine... The problem is only with
the 2005 version. Thank you for your help!
"John Bell" wrote:
> Hi Mitch
> Then I can't see why you are getting this message! Have you tried this
> without the named ranges or a different version of Excel?
> John
> "Mitch" wrote:
>|||Hi Mitch
SQL 2005 has most thing off by default, but I can't remember having to
change anything special for excel files, although I haven't tried named
ranges.
John
"Mitch" wrote:
> I'll have the IT people check the installation settings for SQL Server 200
5.
> The 2000 version of DTS still works just fine... The problem is only with
> the 2005 version. Thank you for your help!
> "John Bell" wrote:
>|||I get the error message several seconds after identifying the source and it
does not progress (show any more windows) from that point. The message
suggests that it is a Microsoft Jet Database Engine error message. We
watched the server during the attempt (several times) and absolutely nothing
is happening on the server end (SQL Server). My workstation has 2.0 GB RAM
so I doubt that RAM is a problem. The funny part is that the data transfer
works using SQL Server 2000 (which I no longer have installed). Any
suggestions?
"John Bell" wrote:
> Hi Mitch
> SQL 2005 has most thing off by default, but I can't remember having to
> change anything special for excel files, although I haven't tried named
> ranges.
> John
>
> "Mitch" wrote:
>|||Hi
It does sound like a driver issue, I have tested importing named ranges
without any issues.
John
"Mitch" wrote:
> I get the error message several seconds after identifying the source and i
t
> does not progress (show any more windows) from that point. The message
> suggests that it is a Microsoft Jet Database Engine error message. We
> watched the server during the attempt (several times) and absolutely nothi
ng
> is happening on the server end (SQL Server). My workstation has 2.0 GB RA
M
> so I doubt that RAM is a problem. The funny part is that the data transfe
r
> works using SQL Server 2000 (which I no longer have installed). Any
> suggestions?
> "John Bell" wrote:
>

Saturday, February 25, 2012

New export option

Hello Fellow RS
Has anyone ever heard of or tried adding to the report export list?
I've read through the BOL for report export options and searched the
web for advice. There is quite a bit of information folks have shared
on ways to export stored procedure results to a fixed length text
file. But I haven't found anything on exporting from a report to a
text file.
Is it was possible to export a report into a fixed length text file
from a Reporting Services website report?The only text based export that Reporting Services does is CSV (Comma
Delimited). On adding a type to the export list you would have to write
your own rendering extension to transform the data in the report and that
isn't an easy task. If you look in the rsreportserver.config file you'll
see a <Render> section that contains all of the various rendering
extensions available to Reporting Services.
You can find more information about creating a rendering extension here:
http://msdn2.microsoft.com/en-us/library/ms153624.aspx
One last question. When you say "Fixed length text file" do you mean a
"fixed width" text file or an actual fixed size of the text file being
produced?
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: asflp <fpetrivelli@.gmail.com>
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: New export option
> Date: Fri, 26 Oct 2007 17:12:18 -0000
> Organization: http://groups.google.com
> Hello Fellow RS
> Has anyone ever heard of or tried adding to the report export list?
> I've read through the BOL for report export options and searched the
> web for advice. There is quite a bit of information folks have shared
> on ways to export stored procedure results to a fixed length text
> file. But I haven't found anything on exporting from a report to a
> text file.
> Is it was possible to export a report into a fixed length text file
> from a Reporting Services website report?
>|||On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
wrote:
> The only text based export that Reporting Services does is CSV (Comma
> Delimited). On adding a type to the export list you would have to write
> your own rendering extension to transform the data in the report and that
> isn't an easy task. If you look in the rsreportserver.config file you'll
> see a <Render> section that contains all of the various rendering
> extensions available to Reporting Services.
> You can find more information about creating a rendering extension here:
> http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> One last question. When you say "Fixed length text file" do you mean a
> "fixed width" text file or an actual fixed size of the text file being
> produced?
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
>
> > From: asflp <fpetrive...@.gmail.com>
> > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > Subject: New export option
> > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > Organization:http://groups.google.com
> > Hello Fellow RS
> > Has anyone ever heard of or tried adding to the report export list?
> > I've read through the BOL for report export options and searched the
> > web for advice. There is quite a bit of information folks have shared
> > on ways to export stored procedure results to a fixed length text
> > file. But I haven't found anything on exporting from a report to a
> > text file.
> > Is it was possible to export a report into a fixed length text file
> > from a Reporting Services website report... Hide quoted text -
> - Show quoted text -
Thanks for your response.
I'm beginning to think that SS Integration Services would be the best
bet to accomplish this task.
(And I did mean fixed width columns in the text file.)
Thanks again!|||On Oct 26, 12:09 pm, asflp <fpetrive...@.gmail.com> wrote:
> On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
> wrote:
>
>
> > The only text based export that Reporting Services does is CSV (Comma
> > Delimited). On adding a type to the export list you would have to write
> > your own rendering extension to transform the data in the report and that
> > isn't an easy task. If you look in the rsreportserver.config file you'll
> > see a <Render> section that contains all of the various rendering
> > extensions available to Reporting Services.
> > You can find more information about creating a rendering extension here:
> >http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> > One last question. When you say "Fixed length text file" do you mean a
> > "fixed width" text file or an actual fixed size of the text file being
> > produced?
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > --
> > > From: asflp <fpetrive...@.gmail.com>
> > > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > > Subject: New export option
> > > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > > Organization:http://groups.google.com
> > > Hello Fellow RS
> > > Has anyone ever heard of or tried adding to the report export list?
> > > I've read through the BOL for report export options and searched the
> > > web for advice. There is quite a bit of information folks have shared
> > > on ways to export stored procedure results to a fixed length text
> > > file. But I haven't found anything on exporting from a report to a
> > > text file.
> > > Is it was possible to export a report into a fixed length text file
> > > from a Reporting Services website report... Hide quoted text -
> > - Show quoted text -
> Thanks for your response.
> I'm beginning to think that SS Integration Services would be the best
> bet to accomplish this task.
> (And I did mean fixed width columns in the text file.)
> Thanks again!- Hide quoted text -
> - Show quoted text -
Just an add-on comment, I followed the link and I really can't tell
you why I didn't get to that part of BOL when I was reading about the
export options. BOL certainly is vast and interesting to navigate.|||You have to know the secret code word and hand shake to be able to really
search books online :)
It's always easy to find things when you know exactly what you are looking
for. If you search for "custom rendering extension" then you'll find that
section as the first result. If you have no clue that is what it is that
you are trying to do then searching for that stuff can be quite difficult.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> From: asflp <fpetrivelli@.gmail.com>
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Subject: Re: New export option
> Date: Fri, 26 Oct 2007 19:25:57 -0000
> Organization: http://groups.google.com
> Lines: 65
> On Oct 26, 12:09 pm, asflp <fpetrive...@.gmail.com> wrote:
> > On Oct 26, 10:46 am, cal...@.online.microsoft.com (Chris Alton [MSFT])
> > wrote:
> >
> >
> >
> >
> >
> > > The only text based export that Reporting Services does is CSV (Comma
> > > Delimited). On adding a type to the export list you would have to
write
> > > your own rendering extension to transform the data in the report and
that
> > > isn't an easy task. If you look in the rsreportserver.config file
you'll
> > > see a <Render> section that contains all of the various rendering
> > > extensions available to Reporting Services.
> >
> > > You can find more information about creating a rendering extension
here:
> >
> > >http://msdn2.microsoft.com/en-us/library/ms153624.aspx
> >
> > > One last question. When you say "Fixed length text file" do you mean a
> > > "fixed width" text file or an actual fixed size of the text file being
> > > produced?
> > > --
> > > Chris Alton, Microsoft Corp.
> > > SQL Server Developer Support Engineer
> > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > > --
> >
> > > > From: asflp <fpetrive...@.gmail.com>
> > > > Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > > > Subject: New export option
> > > > Date: Fri, 26 Oct 2007 17:12:18 -0000
> > > > Organization:http://groups.google.com
> >
> > > > Hello Fellow RS
> >
> > > > Has anyone ever heard of or tried adding to the report export list?
> >
> > > > I've read through the BOL for report export options and searched the
> > > > web for advice. There is quite a bit of information folks have
shared
> > > > on ways to export stored procedure results to a fixed length text
> > > > file. But I haven't found anything on exporting from a report to a
> > > > text file.
> >
> > > > Is it was possible to export a report into a fixed length text file
> > > > from a Reporting Services website report... Hide quoted text -
> >
> > > - Show quoted text -
> >
> > Thanks for your response.
> >
> > I'm beginning to think that SS Integration Services would be the best
> > bet to accomplish this task.
> >
> > (And I did mean fixed width columns in the text file.)
> >
> > Thanks again!- Hide quoted text -
> >
> > - Show quoted text -
> Just an add-on comment, I followed the link and I really can't tell
> you why I didn't get to that part of BOL when I was reading about the
> export options. BOL certainly is vast and interesting to navigate.
>
>