Exporting report to multiple PDF's

Is it possile for a report to be exported to multiple PDF files, each pdf file would be for a group in the report and would ideally use field information for the group to construct the pdf filename?

The purpose of this is to provide a separate PDF for access over the web, so for example we have a scheduled report that generates a report grouped by sales region we would end up with SalesRegionA.PDF, SalesRegionB.PDF etc.

Hi Hugh,

What you can do is have a parameter in your report which will have the groups...ie you can have a parameter for Sales Region, then what you can do is run batch script, which has a command that calls a .rss file passing in some values -which will export your values to pdf...

you can create a batch script that calls the .rss file like below...

rs -i RunReports.rss -s http:..localhost/reportserver -1 0 -v directory="%1 -v reportname= "Name of report" -v filename="Name of file.pdf" -v format="pdf" -v params="this is were the parameter value goes" -v debug.

rs -i RunReports.rss -s http:..localhost/reportserver -1 0 -v directory="%1 -v reportname= "Name of report 2" -v filename="Name of file.pdf 2" -v format="pdf" -v params="this is were the parameter 2 value goes" -v debug.

(note you can have mutiple statements, allowing you to pass different values in the reportname, params section...

Your .rss file will use these values to render through the reports and export the files, i beleive there are examples on the Web of this.

Or what you can do is use a data driven subscription which is much easier (you will have to create the parameter in your report still). You have to create a table in your SQL Server DB, to hold the parameters ie all the Sales Region and use the Subscription to look at this tables..to do this go to subscriptions in report manager (when viewing the report), then go to data driven subscriptions, then follow the steps which are pretty simple...

Hope this helps.

|||Thans for your suggestions, I'd sort of moved in the direction of a a data driven subscription anyway but I think there's still quite a bit more to do, especially working out how to trigger the subscription from an application - I've started looking at the fireevent api.

Exporting Groups to Excel

I have a group set up woth page breaks at the end. When I export it to Excel
it generates a separate sheet (tab) for each page. Is there a way to get it
to export into one sheet, with page breaks in the correct locations?
--
-MTThere appears to be no way around this if <PageBreakAtEnd> is true when
exporting to Excel. When a report is exported to Excel, each page in the
report becomes a worksheet (and you can't name the worksheets either).
--
Adrian M.
MCP
"MT" <MT@.discussions.microsoft.com> wrote in message
news:7552EDA9-F6F9-4008-B902-8A8FA5FFC1C6@.microsoft.com...
>I have a group set up woth page breaks at the end. When I export it to
>Excel
> it generates a separate sheet (tab) for each page. Is there a way to get
> it
> to export into one sheet, with page breaks in the correct locations?
> --
> -MTsql

exporting from SQL to an Outlook group or Dist List?

I need to export a list of name and email address fields from a SQL
table, in some format so that a user can take the file I generate and
Import it into Outlook and it will keep all the names together in a
Group or Distribution List rather than dumping them into the user's
main address book. Any ideas?

Francesco"Francesco" <francesco@.neurodesign.com> wrote in message
news:8b6199d0.0307310928.73359d1e@.posting.google.c om...
> I need to export a list of name and email address fields from a SQL
> table, in some format so that a user can take the file I generate and
> Import it into Outlook and it will keep all the names together in a
> Group or Distribution List rather than dumping them into the user's
> main address book. Any ideas?
> Francesco

Assuming you have SQL2000, you can use BCP or DTS to create a CSV file, or a
file in some other delimited format. As to how you import that into Outlook,
you will get a better response posting in an Outlook newsgroup - there are
several microsoft.public.outlook.* groups.

Simon

Export to PDF - crashing for larger sets of data

Hi Group,
I posted this problem two days ago, but it went unanswered, so here I am,
giving it another try - it's really important for us !
Reformulation :
We have a report that we can run in ReportManager. It takes about 15-20
second to generate, but it displays the html on the screen.
It lets us navigate to the last page and back without any problem.
The problem comes when we try to export this report to PDF format : once I
click the export link, it waits for 60 to 90 seconds, then it displays the
error message :
*************************************************************
Server Application Unavailable
The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web browser
to retry your request.
Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.
***************************************************************
Other information :
- the same report, for smaller amounts of data, works fine when exported to
pdf.
- the same report, when exported to either XML or CSV, works fine - the
files are created.
- we have a lot of other reports working fine when exported to pdf
The only connection we were able to make is related to the amount of data
selected to generate the report...
So I'm guessing it could be related to timeout settings, so I tried changing
in
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config the following keys :
<Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
nothing changed
<Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
nothing changed
I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\web.config
the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
value looks big enough...
The configuration is as follows :
win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
We need a solution to this problem, because our whole application is based
on these reports, and if the reports fail to generate PDFs for larger sets
of data, then I can say our work was quite useless...:(
I appreciate any advice that could point us in the right direction !
Thanks,
Andrei.
I also tried running the report from the RS interface
(http://localhost/Reports). It generates the html view for the faulty
report, but when it comes to export to PDF format, the same error message
pops up.
Note : if I try to export the report to xml or csv, the operation completes
successfuly.
What could be the problem ? Please help !We did a lot of work in SP2 of Reporting Services to improve rendering. I
would suggest installing Service Pack 2 of Reporting Services and trying
this again.
If it continues to be a problem, then contact Microsoft PSS. If it is
indeed a bug, which it sounds like it is, all fees will be reimbursed.
--
| From: "andrei" <andrei.toma@.era-environmental.com>
| Subject: Export to PDF - crashing for larger sets of data
| Date: Thu, 29 Sep 2005 09:26:31 -0400
| Lines: 83
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
| Message-ID: <OSdxGqPxFHA.1132@.TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: modemcable233.195-200-24.mc.videotron.ca 24.200.195.233
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:53351
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Hi Group,
|
| I posted this problem two days ago, but it went unanswered, so here I am,
| giving it another try - it's really important for us !
| Reformulation :
|
| We have a report that we can run in ReportManager. It takes about 15-20
| second to generate, but it displays the html on the screen.
| It lets us navigate to the last page and back without any problem.
|
| The problem comes when we try to export this report to PDF format : once I
| click the export link, it waits for 60 to 90 seconds, then it displays the
| error message :
| *************************************************************
| Server Application Unavailable
| The web application you are attempting to access on this web server is
| currently unavailable. Please hit the "Refresh" button in your web
browser
| to retry your request.
|
| Administrator Note: An error message detailing the cause of this specific
| request failure can be found in the application event log of the web
server.
| Please review this log entry to discover what caused this error to occur.
| ***************************************************************
|
| Other information :
| - the same report, for smaller amounts of data, works fine when exported
to
| pdf.
| - the same report, when exported to either XML or CSV, works fine - the
| files are created.
| - we have a lot of other reports working fine when exported to pdf
|
| The only connection we were able to make is related to the amount of data
| selected to generate the report...
|
| So I'm guessing it could be related to timeout settings, so I tried
changing
| in
| C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
| Services\ReportServer\RSReportServer.config the following keys :
| <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
| nothing changed
| <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720
-
| nothing changed
|
| I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
| Services\ReportServer\web.config
| the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
| value looks big enough...
|
| The configuration is as follows :
| win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
|
| We need a solution to this problem, because our whole application is based
| on these reports, and if the reports fail to generate PDFs for larger sets
| of data, then I can say our work was quite useless...:(
|
| I appreciate any advice that could point us in the right direction !
|
| Thanks,
|
| Andrei.
|
|
|
|
|
|
|
|
|
| I also tried running the report from the RS interface
| (http://localhost/Reports). It generates the html view for the faulty
| report, but when it comes to export to PDF format, the same error message
| pops up.
|
| Note : if I try to export the report to xml or csv, the operation
completes
| successfuly.
|
| What could be the problem ? Please help !
|
|
|
|
|
||||We are having EXACTLY the same problem!
Questions:
1) did you upgrade to SP2?
2) did it solve your problem (sure hope so)
Thanks so much!
Al
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||This has to do with some timeout settings on the web server. Rendering to
PDF takes much longer than HTML. 20 seconds with HTML could take minutes
with PDF (Depends on the number of rows, the complexity etc). I think it
might be the web server itself, not a RS configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> We are having EXACTLY the same problem!
> Questions:
> 1) did you upgrade to SP2?
> 2) did it solve your problem (sure hope so)
> Thanks so much!
> Al
> "andrei" wrote:
>> Hi Group,
>> I posted this problem two days ago, but it went unanswered, so here I am,
>> giving it another try - it's really important for us !
>> Reformulation :
>> We have a report that we can run in ReportManager. It takes about 15-20
>> second to generate, but it displays the html on the screen.
>> It lets us navigate to the last page and back without any problem.
>> The problem comes when we try to export this report to PDF format : once
>> I
>> click the export link, it waits for 60 to 90 seconds, then it displays
>> the
>> error message :
>> *************************************************************
>> Server Application Unavailable
>> The web application you are attempting to access on this web server is
>> currently unavailable. Please hit the "Refresh" button in your web
>> browser
>> to retry your request.
>> Administrator Note: An error message detailing the cause of this specific
>> request failure can be found in the application event log of the web
>> server.
>> Please review this log entry to discover what caused this error to occur.
>> ***************************************************************
>> Other information :
>> - the same report, for smaller amounts of data, works fine when exported
>> to
>> pdf.
>> - the same report, when exported to either XML or CSV, works fine - the
>> files are created.
>> - we have a lot of other reports working fine when exported to pdf
>> The only connection we were able to make is related to the amount of data
>> selected to generate the report...
>> So I'm guessing it could be related to timeout settings, so I tried
>> changing
>> in
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\RSReportServer.config the following keys :
>> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> nothing changed
>> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> -
>> nothing changed
>> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\web.config
>> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
>> value looks big enough...
>> The configuration is as follows :
>> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> We need a solution to this problem, because our whole application is
>> based
>> on these reports, and if the reports fail to generate PDFs for larger
>> sets
>> of data, then I can say our work was quite useless...:(
>> I appreciate any advice that could point us in the right direction !
>> Thanks,
>> Andrei.
>>
>>
>>
>>
>> I also tried running the report from the RS interface
>> (http://localhost/Reports). It generates the html view for the faulty
>> report, but when it comes to export to PDF format, the same error message
>> pops up.
>> Note : if I try to export the report to xml or csv, the operation
>> completes
>> successfuly.
>> What could be the problem ? Please help !
>>
>>
>>|||Thanks,
Any idea which settings to try?
Sometimes even the large sets complete OK, but usually not.
"Bruce L-C [MVP]" wrote:
> This has to do with some timeout settings on the web server. Rendering to
> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
> with PDF (Depends on the number of rows, the complexity etc). I think it
> might be the web server itself, not a RS configuration.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> > We are having EXACTLY the same problem!
> >
> > Questions:
> > 1) did you upgrade to SP2?
> > 2) did it solve your problem (sure hope so)
> >
> > Thanks so much!
> >
> > Al
> >
> > "andrei" wrote:
> >
> >> Hi Group,
> >>
> >> I posted this problem two days ago, but it went unanswered, so here I am,
> >> giving it another try - it's really important for us !
> >> Reformulation :
> >>
> >> We have a report that we can run in ReportManager. It takes about 15-20
> >> second to generate, but it displays the html on the screen.
> >> It lets us navigate to the last page and back without any problem.
> >>
> >> The problem comes when we try to export this report to PDF format : once
> >> I
> >> click the export link, it waits for 60 to 90 seconds, then it displays
> >> the
> >> error message :
> >> *************************************************************
> >> Server Application Unavailable
> >> The web application you are attempting to access on this web server is
> >> currently unavailable. Please hit the "Refresh" button in your web
> >> browser
> >> to retry your request.
> >>
> >> Administrator Note: An error message detailing the cause of this specific
> >> request failure can be found in the application event log of the web
> >> server.
> >> Please review this log entry to discover what caused this error to occur.
> >> ***************************************************************
> >>
> >> Other information :
> >> - the same report, for smaller amounts of data, works fine when exported
> >> to
> >> pdf.
> >> - the same report, when exported to either XML or CSV, works fine - the
> >> files are created.
> >> - we have a lot of other reports working fine when exported to pdf
> >>
> >> The only connection we were able to make is related to the amount of data
> >> selected to generate the report...
> >>
> >> So I'm guessing it could be related to timeout settings, so I tried
> >> changing
> >> in
> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> Services\ReportServer\RSReportServer.config the following keys :
> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> >> nothing changed
> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
> >> -
> >> nothing changed
> >>
> >> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> Services\ReportServer\web.config
> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> >> value looks big enough...
> >>
> >> The configuration is as follows :
> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> >>
> >> We need a solution to this problem, because our whole application is
> >> based
> >> on these reports, and if the reports fail to generate PDFs for larger
> >> sets
> >> of data, then I can say our work was quite useless...:(
> >>
> >> I appreciate any advice that could point us in the right direction !
> >>
> >> Thanks,
> >>
> >> Andrei.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> I also tried running the report from the RS interface
> >> (http://localhost/Reports). It generates the html view for the faulty
> >> report, but when it comes to export to PDF format, the same error message
> >> pops up.
> >>
> >> Note : if I try to export the report to xml or csv, the operation
> >> completes
> >> successfuly.
> >>
> >> What could be the problem ? Please help !
> >>
> >>
> >>
> >>
> >>
> >>
>
>|||I see that you are on 2000 which I assume is IIS 5? I am on 2003 which is
IIS 6 so how you do things is totally different. Sorry,
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Al Sherman" <AlSherman@.discussions.microsoft.com> wrote in message
news:80482824-1EFA-4C14-9823-91648365607E@.microsoft.com...
> Thanks,
> Any idea which settings to try?
> Sometimes even the large sets complete OK, but usually not.
> "Bruce L-C [MVP]" wrote:
>> This has to do with some timeout settings on the web server. Rendering to
>> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
>> with PDF (Depends on the number of rows, the complexity etc). I think it
>> might be the web server itself, not a RS configuration.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
>> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
>> > We are having EXACTLY the same problem!
>> >
>> > Questions:
>> > 1) did you upgrade to SP2?
>> > 2) did it solve your problem (sure hope so)
>> >
>> > Thanks so much!
>> >
>> > Al
>> >
>> > "andrei" wrote:
>> >
>> >> Hi Group,
>> >>
>> >> I posted this problem two days ago, but it went unanswered, so here I
>> >> am,
>> >> giving it another try - it's really important for us !
>> >> Reformulation :
>> >>
>> >> We have a report that we can run in ReportManager. It takes about
>> >> 15-20
>> >> second to generate, but it displays the html on the screen.
>> >> It lets us navigate to the last page and back without any problem.
>> >>
>> >> The problem comes when we try to export this report to PDF format :
>> >> once
>> >> I
>> >> click the export link, it waits for 60 to 90 seconds, then it displays
>> >> the
>> >> error message :
>> >> *************************************************************
>> >> Server Application Unavailable
>> >> The web application you are attempting to access on this web server is
>> >> currently unavailable. Please hit the "Refresh" button in your web
>> >> browser
>> >> to retry your request.
>> >>
>> >> Administrator Note: An error message detailing the cause of this
>> >> specific
>> >> request failure can be found in the application event log of the web
>> >> server.
>> >> Please review this log entry to discover what caused this error to
>> >> occur.
>> >> ***************************************************************
>> >>
>> >> Other information :
>> >> - the same report, for smaller amounts of data, works fine when
>> >> exported
>> >> to
>> >> pdf.
>> >> - the same report, when exported to either XML or CSV, works fine -
>> >> the
>> >> files are created.
>> >> - we have a lot of other reports working fine when exported to pdf
>> >>
>> >> The only connection we were able to make is related to the amount of
>> >> data
>> >> selected to generate the report...
>> >>
>> >> So I'm guessing it could be related to timeout settings, so I tried
>> >> changing
>> >> in
>> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> >> Services\ReportServer\RSReportServer.config the following keys :
>> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> >> nothing changed
>> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> >> -
>> >> nothing changed
>> >>
>> >> I also checked in C:\Program Files\Microsoft SQL
>> >> Server\MSSQL\Reporting
>> >> Services\ReportServer\web.config
>> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it,
>> >> the
>> >> value looks big enough...
>> >>
>> >> The configuration is as follows :
>> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> >>
>> >> We need a solution to this problem, because our whole application is
>> >> based
>> >> on these reports, and if the reports fail to generate PDFs for larger
>> >> sets
>> >> of data, then I can say our work was quite useless...:(
>> >>
>> >> I appreciate any advice that could point us in the right direction !
>> >>
>> >> Thanks,
>> >>
>> >> Andrei.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> I also tried running the report from the RS interface
>> >> (http://localhost/Reports). It generates the html view for the faulty
>> >> report, but when it comes to export to PDF format, the same error
>> >> message
>> >> pops up.
>> >>
>> >> Note : if I try to export the report to xml or csv, the operation
>> >> completes
>> >> successfuly.
>> >>
>> >> What could be the problem ? Please help !
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>>|||Hi Bruce:
Actually, we are running on a 2003 system, which is running IIS 6
I'm going to give Brad's suggestion a shot and upgrade to SP2.
I'll post a message as to whether or not this solves the problem
Thanks,
Al
"Bruce L-C [MVP]" wrote:
> I see that you are on 2000 which I assume is IIS 5? I am on 2003 which is
> IIS 6 so how you do things is totally different. Sorry,
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Al Sherman" <AlSherman@.discussions.microsoft.com> wrote in message
> news:80482824-1EFA-4C14-9823-91648365607E@.microsoft.com...
> > Thanks,
> >
> > Any idea which settings to try?
> >
> > Sometimes even the large sets complete OK, but usually not.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This has to do with some timeout settings on the web server. Rendering to
> >> PDF takes much longer than HTML. 20 seconds with HTML could take minutes
> >> with PDF (Depends on the number of rows, the complexity etc). I think it
> >> might be the web server itself, not a RS configuration.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Al Sherman" <Al Sherman@.discussions.microsoft.com> wrote in message
> >> news:44A9AA81-DE65-44F5-85A7-3A266DCCA248@.microsoft.com...
> >> > We are having EXACTLY the same problem!
> >> >
> >> > Questions:
> >> > 1) did you upgrade to SP2?
> >> > 2) did it solve your problem (sure hope so)
> >> >
> >> > Thanks so much!
> >> >
> >> > Al
> >> >
> >> > "andrei" wrote:
> >> >
> >> >> Hi Group,
> >> >>
> >> >> I posted this problem two days ago, but it went unanswered, so here I
> >> >> am,
> >> >> giving it another try - it's really important for us !
> >> >> Reformulation :
> >> >>
> >> >> We have a report that we can run in ReportManager. It takes about
> >> >> 15-20
> >> >> second to generate, but it displays the html on the screen.
> >> >> It lets us navigate to the last page and back without any problem.
> >> >>
> >> >> The problem comes when we try to export this report to PDF format :
> >> >> once
> >> >> I
> >> >> click the export link, it waits for 60 to 90 seconds, then it displays
> >> >> the
> >> >> error message :
> >> >> *************************************************************
> >> >> Server Application Unavailable
> >> >> The web application you are attempting to access on this web server is
> >> >> currently unavailable. Please hit the "Refresh" button in your web
> >> >> browser
> >> >> to retry your request.
> >> >>
> >> >> Administrator Note: An error message detailing the cause of this
> >> >> specific
> >> >> request failure can be found in the application event log of the web
> >> >> server.
> >> >> Please review this log entry to discover what caused this error to
> >> >> occur.
> >> >> ***************************************************************
> >> >>
> >> >> Other information :
> >> >> - the same report, for smaller amounts of data, works fine when
> >> >> exported
> >> >> to
> >> >> pdf.
> >> >> - the same report, when exported to either XML or CSV, works fine -
> >> >> the
> >> >> files are created.
> >> >> - we have a lot of other reports working fine when exported to pdf
> >> >>
> >> >> The only connection we were able to make is related to the amount of
> >> >> data
> >> >> selected to generate the report...
> >> >>
> >> >> So I'm guessing it could be related to timeout settings, so I tried
> >> >> changing
> >> >> in
> >> >> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> >> >> Services\ReportServer\RSReportServer.config the following keys :
> >> >> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> >> >> nothing changed
> >> >> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
> >> >> -
> >> >> nothing changed
> >> >>
> >> >> I also checked in C:\Program Files\Microsoft SQL
> >> >> Server\MSSQL\Reporting
> >> >> Services\ReportServer\web.config
> >> >> the key <httpRuntime executionTimeout = "9000" /> - didn't change it,
> >> >> the
> >> >> value looks big enough...
> >> >>
> >> >> The configuration is as follows :
> >> >> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> >> >>
> >> >> We need a solution to this problem, because our whole application is
> >> >> based
> >> >> on these reports, and if the reports fail to generate PDFs for larger
> >> >> sets
> >> >> of data, then I can say our work was quite useless...:(
> >> >>
> >> >> I appreciate any advice that could point us in the right direction !
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Andrei.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> I also tried running the report from the RS interface
> >> >> (http://localhost/Reports). It generates the html view for the faulty
> >> >> report, but when it comes to export to PDF format, the same error
> >> >> message
> >> >> pops up.
> >> >>
> >> >> Note : if I try to export the report to xml or csv, the operation
> >> >> completes
> >> >> successfuly.
> >> >>
> >> >> What could be the problem ? Please help !
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Hi Brad:
We've experienced the exact same problem.
I upgraded SQL Server to SP4 and Reporting Services to SP2 and the problem
persists.
How can I contact MS PSS?
Thanks a bunch!
Al
""Brad Syputa - MS"" wrote:
> We did a lot of work in SP2 of Reporting Services to improve rendering. I
> would suggest installing Service Pack 2 of Reporting Services and trying
> this again.
> If it continues to be a problem, then contact Microsoft PSS. If it is
> indeed a bug, which it sounds like it is, all fees will be reimbursed.
> --
> | From: "andrei" <andrei.toma@.era-environmental.com>
> | Subject: Export to PDF - crashing for larger sets of data
> | Date: Thu, 29 Sep 2005 09:26:31 -0400
> | Lines: 83
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
> | Message-ID: <OSdxGqPxFHA.1132@.TK2MSFTNGP10.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: modemcable233.195-200-24.mc.videotron.ca 24.200.195.233
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:53351
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Hi Group,
> |
> | I posted this problem two days ago, but it went unanswered, so here I am,
> | giving it another try - it's really important for us !
> | Reformulation :
> |
> | We have a report that we can run in ReportManager. It takes about 15-20
> | second to generate, but it displays the html on the screen.
> | It lets us navigate to the last page and back without any problem.
> |
> | The problem comes when we try to export this report to PDF format : once I
> | click the export link, it waits for 60 to 90 seconds, then it displays the
> | error message :
> | *************************************************************
> | Server Application Unavailable
> | The web application you are attempting to access on this web server is
> | currently unavailable. Please hit the "Refresh" button in your web
> browser
> | to retry your request.
> |
> | Administrator Note: An error message detailing the cause of this specific
> | request failure can be found in the application event log of the web
> server.
> | Please review this log entry to discover what caused this error to occur.
> | ***************************************************************
> |
> | Other information :
> | - the same report, for smaller amounts of data, works fine when exported
> to
> | pdf.
> | - the same report, when exported to either XML or CSV, works fine - the
> | files are created.
> | - we have a lot of other reports working fine when exported to pdf
> |
> | The only connection we were able to make is related to the amount of data
> | selected to generate the report...
> |
> | So I'm guessing it could be related to timeout settings, so I tried
> changing
> | in
> | C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> | Services\ReportServer\RSReportServer.config the following keys :
> | <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> | nothing changed
> | <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720
> -
> | nothing changed
> |
> | I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> | Services\ReportServer\web.config
> | the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> | value looks big enough...
> |
> | The configuration is as follows :
> | win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> |
> | We need a solution to this problem, because our whole application is based
> | on these reports, and if the reports fail to generate PDFs for larger sets
> | of data, then I can say our work was quite useless...:(
> |
> | I appreciate any advice that could point us in the right direction !
> |
> | Thanks,
> |
> | Andrei.
> |
> |
> |
> |
> |
> |
> |
> |
> |
> | I also tried running the report from the RS interface
> | (http://localhost/Reports). It generates the html view for the faulty
> | report, but when it comes to export to PDF format, the same error message
> | pops up.
> |
> | Note : if I try to export the report to xml or csv, the operation
> completes
> | successfuly.
> |
> | What could be the problem ? Please help !
> |
> |
> |
> |
> |
> |
>|||Hi Andrei:
We had a problem that sounded exactly the same.
Our report was using a Table Control with multiple "groups" to implement a
report with multiple output lines per result-set row.
I solved the problem by revising the report to use a List Control instead.
I'd appreciate knowing the answers to the following questions:
1) Was your report also using a Table Control?
2) Did it have multiple Groups?
Thanks,
Al
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||I had the exact same problem. For me, the problem was caused by ASP.Net
process recycling options. There is a setting in ASP.Net (under which RS
runs) that controls when a web application is assumed to be performing badly
and hogging too much memory. Once this threshold is reached, ASP.Net kills
the web app and starts a new one - existing requests are left dangling and
IIS returns the "Server Application Unavailable" message.
PDF export consumes large amounts of memory - the rendering is done in
memory. If the report is large, this process recycling limit can be reached.
It is expressed as a percentage of total physical memory. You can find the
setting in <windir>\Microsoft.Net\Framework\v1.14322\config.machine.config.
Look for the "processModel" element's "memoryLimit" attribute. By default it
is "60" - this indicates that the ASP.Net process (which includes RS) will be
recycled when it takes up 60% of the physical memory.
In order to avoid your problem, here are your choices:
1. up this setting
2. Install more memory
"andrei" wrote:
> Hi Group,
> I posted this problem two days ago, but it went unanswered, so here I am,
> giving it another try - it's really important for us !
> Reformulation :
> We have a report that we can run in ReportManager. It takes about 15-20
> second to generate, but it displays the html on the screen.
> It lets us navigate to the last page and back without any problem.
> The problem comes when we try to export this report to PDF format : once I
> click the export link, it waits for 60 to 90 seconds, then it displays the
> error message :
> *************************************************************
> Server Application Unavailable
> The web application you are attempting to access on this web server is
> currently unavailable. Please hit the "Refresh" button in your web browser
> to retry your request.
> Administrator Note: An error message detailing the cause of this specific
> request failure can be found in the application event log of the web server.
> Please review this log entry to discover what caused this error to occur.
> ***************************************************************
> Other information :
> - the same report, for smaller amounts of data, works fine when exported to
> pdf.
> - the same report, when exported to either XML or CSV, works fine - the
> files are created.
> - we have a lot of other reports working fine when exported to pdf
> The only connection we were able to make is related to the amount of data
> selected to generate the report...
> So I'm guessing it could be related to timeout settings, so I tried changing
> in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config the following keys :
> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
> nothing changed
> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to 720 -
> nothing changed
> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\web.config
> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
> value looks big enough...
> The configuration is as follows :
> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
> We need a solution to this problem, because our whole application is based
> on these reports, and if the reports fail to generate PDFs for larger sets
> of data, then I can say our work was quite useless...:(
> I appreciate any advice that could point us in the right direction !
> Thanks,
> Andrei.
>
>
>
>
> I also tried running the report from the RS interface
> (http://localhost/Reports). It generates the html view for the faulty
> report, but when it comes to export to PDF format, the same error message
> pops up.
> Note : if I try to export the report to xml or csv, the operation completes
> successfuly.
> What could be the problem ? Please help !
>
>
>|||This is great information. Thanks for sharing. I have saved your response to
provide to others in the newsgroup at a later date.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Billy Boy" <billyboyo_laptio@.hotmail.com_no_spam> wrote in message
news:CB2112AB-801E-4008-9EF1-60B7FB1C74C5@.microsoft.com...
>I had the exact same problem. For me, the problem was caused by ASP.Net
> process recycling options. There is a setting in ASP.Net (under which RS
> runs) that controls when a web application is assumed to be performing
> badly
> and hogging too much memory. Once this threshold is reached, ASP.Net kills
> the web app and starts a new one - existing requests are left dangling and
> IIS returns the "Server Application Unavailable" message.
> PDF export consumes large amounts of memory - the rendering is done in
> memory. If the report is large, this process recycling limit can be
> reached.
> It is expressed as a percentage of total physical memory. You can find the
> setting in
> <windir>\Microsoft.Net\Framework\v1.14322\config.machine.config.
> Look for the "processModel" element's "memoryLimit" attribute. By default
> it
> is "60" - this indicates that the ASP.Net process (which includes RS) will
> be
> recycled when it takes up 60% of the physical memory.
> In order to avoid your problem, here are your choices:
> 1. up this setting
> 2. Install more memory
> "andrei" wrote:
>> Hi Group,
>> I posted this problem two days ago, but it went unanswered, so here I am,
>> giving it another try - it's really important for us !
>> Reformulation :
>> We have a report that we can run in ReportManager. It takes about 15-20
>> second to generate, but it displays the html on the screen.
>> It lets us navigate to the last page and back without any problem.
>> The problem comes when we try to export this report to PDF format : once
>> I
>> click the export link, it waits for 60 to 90 seconds, then it displays
>> the
>> error message :
>> *************************************************************
>> Server Application Unavailable
>> The web application you are attempting to access on this web server is
>> currently unavailable. Please hit the "Refresh" button in your web
>> browser
>> to retry your request.
>> Administrator Note: An error message detailing the cause of this specific
>> request failure can be found in the application event log of the web
>> server.
>> Please review this log entry to discover what caused this error to occur.
>> ***************************************************************
>> Other information :
>> - the same report, for smaller amounts of data, works fine when exported
>> to
>> pdf.
>> - the same report, when exported to either XML or CSV, works fine - the
>> files are created.
>> - we have a lot of other reports working fine when exported to pdf
>> The only connection we were able to make is related to the amount of data
>> selected to generate the report...
>> So I'm guessing it could be related to timeout settings, so I tried
>> changing
>> in
>> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\RSReportServer.config the following keys :
>> <Add Key="SQLCommandTimeoutSeconds" Value="60"/> from 60 to 300 -
>> nothing changed
>> <Add Key="DatabaseQueryTimeout" Value="120"/> from 120 to
>> -
>> nothing changed
>> I also checked in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
>> Services\ReportServer\web.config
>> the key <httpRuntime executionTimeout = "9000" /> - didn't change it, the
>> value looks big enough...
>> The configuration is as follows :
>> win2000sp4, Visual Studio 2003, SQL2000sp3, RS-no sp
>> We need a solution to this problem, because our whole application is
>> based
>> on these reports, and if the reports fail to generate PDFs for larger
>> sets
>> of data, then I can say our work was quite useless...:(
>> I appreciate any advice that could point us in the right direction !
>> Thanks,
>> Andrei.
>>
>>
>>
>>
>> I also tried running the report from the RS interface
>> (http://localhost/Reports). It generates the html view for the faulty
>> report, but when it comes to export to PDF format, the same error message
>> pops up.
>> Note : if I try to export the report to xml or csv, the operation
>> completes
>> successfuly.
>> What could be the problem ? Please help !
>>
>>
>>

Export to Excel with Expand/Collapse Feature

Hello,
I've searched the news group postings and have not found an answer. The
question is:
Is it possible to export a report from RS into excel and have the
expand/collapse feature in excel work?
Thanks,
RossIf your report has drill down the resulting Excel spreadsheet will have
expand/collapse
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ross_co" <ross_co@.discussions.microsoft.com> wrote in message
news:060EB67A-BB2E-47C3-8400-D088AEC095F1@.microsoft.com...
> Hello,
> I've searched the news group postings and have not found an answer. The
> question is:
> Is it possible to export a report from RS into excel and have the
> expand/collapse feature in excel work?
> Thanks,
> Ross|||I have 2 levels of drill down. The first level does expand/collapse. The
second level, the details, do not get exported unless that section was
already open in the report. I am using Excel XP.
Any ideas?
Thanks,
Neil
"Bruce L-C [MVP]" wrote:
> If your report has drill down the resulting Excel spreadsheet will have
> expand/collapse
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ross_co" <ross_co@.discussions.microsoft.com> wrote in message
> news:060EB67A-BB2E-47C3-8400-D088AEC095F1@.microsoft.com...
> > Hello,
> >
> > I've searched the news group postings and have not found an answer. The
> > question is:
> >
> > Is it possible to export a report from RS into excel and have the
> > expand/collapse feature in excel work?
> >
> > Thanks,
> > Ross
>
>|||I got the same problem but with Excel 2003.
"Neil Gould" wrote:
> I have 2 levels of drill down. The first level does expand/collapse. The
> second level, the details, do not get exported unless that section was
> already open in the report. I am using Excel XP.
> Any ideas?
> Thanks,
> Neil
> "Bruce L-C [MVP]" wrote:
> > If your report has drill down the resulting Excel spreadsheet will have
> > expand/collapse
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "ross_co" <ross_co@.discussions.microsoft.com> wrote in message
> > news:060EB67A-BB2E-47C3-8400-D088AEC095F1@.microsoft.com...
> > > Hello,
> > >
> > > I've searched the news group postings and have not found an answer. The
> > > question is:
> > >
> > > Is it possible to export a report from RS into excel and have the
> > > expand/collapse feature in excel work?
> > >
> > > Thanks,
> > > Ross
> >
> >
> >|||I have the same problem with RS2000 SP2, the drill down works on web, but
export to excel has no expand and collapse.
"Neil Gould" wrote:
> I have 2 levels of drill down. The first level does expand/collapse. The
> second level, the details, do not get exported unless that section was
> already open in the report. I am using Excel XP.
> Any ideas?
> Thanks,
> Neil
> "Bruce L-C [MVP]" wrote:
> > If your report has drill down the resulting Excel spreadsheet will have
> > expand/collapse
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "ross_co" <ross_co@.discussions.microsoft.com> wrote in message
> > news:060EB67A-BB2E-47C3-8400-D088AEC095F1@.microsoft.com...
> > > Hello,
> > >
> > > I've searched the news group postings and have not found an answer. The
> > > question is:
> > >
> > > Is it possible to export a report from RS into excel and have the
> > > expand/collapse feature in excel work?
> > >
> > > Thanks,
> > > Ross
> >
> >
> >|||I'm having a similiar issue - We have a report where with 2 levels where the
top is collapsable. It's fine when you view the report, but when you export
the report to Excel, it no longer has the collapsable operation - it jus
tlists each sub-item with ########.
Any ideas?
"Bruce L-C [MVP]" wrote:
> If your report has drill down the resulting Excel spreadsheet will have
> expand/collapse
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ross_co" <ross_co@.discussions.microsoft.com> wrote in message
> news:060EB67A-BB2E-47C3-8400-D088AEC095F1@.microsoft.com...
> > Hello,
> >
> > I've searched the news group postings and have not found an answer. The
> > question is:
> >
> > Is it possible to export a report from RS into excel and have the
> > expand/collapse feature in excel work?
> >
> > Thanks,
> > Ross
>
>|||Sorry, forgot to mention, this is for SRS 2005.

Export to excel - table headers disappear

Hi All,

When I export a multi page report (page breaks are set at the end of each group, say product group in a sales report) to excel table header dissapear. so I dont see column headings in XL.

When viewed via web browser everything is fine.

any ideas?

Thanks

Sonny

What is the intention to post your question on SQL Server Forum. Is it using SQL Server Reporting service.

What function/logic are you using to export from WEB to Excel?

|||It sounds very much like you're viewing a Reporting Services report.

When you've exported to Excel, are the column headers there at all, or simply not repeated on each page? If it's the latter, check the Page Setup information (in Excel), to find out what gets repeated.

Good luck.

Rob|||

thanks

you are right I'm in the wrong forum. this is reporting services issue

sonny

export tables from SQL Server to external drive and linking

I hope this is the correct group for this question, if not I hope someone can
direct me to the correct one..
I have a co-working that is running Sql Server on a desktop and she has 3
tables that are extremely large. The files are so large she has no disk
space let to work, At the current time it is not possible to replace the
internal drive. She has a 320gig external drive that she wants to move these
tables and then link to them to run her queries.
Is this something that is possible in Sql Server?
Thanks
Andrea ,
thank you for the help.. I will pass long this information.
Raj
"Andrea Montanari" wrote:

> hi,
> Raj wrote:
> you can detach the database via sp_detach_db system stored procedure
> (http://msdn2.microsoft.com/en-us/library/ms188031.aspx), move the relative
> database files to the external drive and reattach the database via CREATE
> DATABASE ... FOR ATTACH; statement
> (http://msdn2.microsoft.com/en-us/library/ms176061.aspx) like
> USE [master]
> GO
> CREATE DATABASE [Raj] ON
> ( FILENAME = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Data\Raj.mdf' ),
> ( FILENAME = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Data\Raj_log.LDF' )
> FOR ATTACH
> GO
> where you obviously modify the path to the external drive...
> please keep in mind that you always have to detach the database(s) before
> removing the external drive to prevent database corruptions so that it
> becomes suspect and unavailable...
> you obviously can incur in security problems (database loss in case of hot
> drive removing) and reduced performances becouse of the limited I/O speed of
> external drives (like USB2 and the like, that provide limited transfer
> rates)...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>