PDF Export Very SLOW ! MS Rerporting Services TEAM Where Are you ??

Hi,
I have a matrix report that produce 79 pages on the HTML browser in 30
seconds, but
if I try to export the report in a PDF format it take more than 1 our !!!
The system configuration is:
IBM Server with 2 Pentium Xeon of 2.4 Ghz
1 Gb of RAM
Fast network HD
Windows 2003 Server SP1 (SBS)
SQL Server 2000 SP4
Rerpoting Services SP2
Do you have any idea about this problem ?
I've saw there are some old messages about this problem on this newsgroup,
but nobody of the
Microsoft Rerpoting Service Team has reply !!!
I think this is a very important issue, that can KILL the reportin services
system on a
Serious Real World company application.
Thanks.
Cesar Augusto Flavio De Min.
MCSDEven 30 seconds for HTML is very slow. PDF definitely is much much slower.
Everything is done in RAM. 1 GB of RAM is pretty minimal. Is your data on
this server as well or just RS? Can you add more RAM to it. Perhaps bring it
up to 2 Gig. Also, an 80 page report while not huge is most likely taking
time due to complexity. You could try splitting it up into multiple reports.
I don't know if RS 2005 has improved performance of PDF rendering or not.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Cesar Augusto Flavio De Min" <cdemin_news@.yahoo.com> wrote in message
news:emEEYAO7FHA.2012@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have a matrix report that produce 79 pages on the HTML browser in 30
> seconds, but
> if I try to export the report in a PDF format it take more than 1 our !!!
> The system configuration is:
> IBM Server with 2 Pentium Xeon of 2.4 Ghz
> 1 Gb of RAM
> Fast network HD
> Windows 2003 Server SP1 (SBS)
> SQL Server 2000 SP4
> Rerpoting Services SP2
> Do you have any idea about this problem ?
> I've saw there are some old messages about this problem on this newsgroup,
> but nobody of the
> Microsoft Rerpoting Service Team has reply !!!
> I think this is a very important issue, that can KILL the reportin
> services system on a
> Serious Real World company application.
> Thanks.
> Cesar Augusto Flavio De Min.
> MCSD
>

Pausing Replication

Several times over the course of a month, our network admin team performs
necessary maintenance due to company moves and general growth. During this
time the connection between my Publisher and Distributor is disconnected. My
Subscriber and Distributor are on the same server. I have three
transactional publications set up and I would like to Pause them until the
connection is restored since I know when the connection is going down.
Is this the correct way to handle this?
From the Distributor in the enterprise manager drill down through the
replication monitor to the Distibution Agents and click on Stop Agent for
all of the publication that I have. Do I also have to Stop Agent on all of
the publications in the Log Reader Agents folder?
This also brings up the question of unplanned connection loss. If for some
reason the connection is lost late at night and I dont know about it until
the next morning do I have to recreate snapshots or re-initialize the
publication?
I would stop SQL Server agent, disable the jobs in the management folder and
then restart the agents. You should only have to stop the distributor or
merge agents.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Butler via droptable.com" <forum@.nospam.droptable.com> wrote in
message news:4FFDFDD1EDC20@.droptable.com...
> Several times over the course of a month, our network admin team performs
> necessary maintenance due to company moves and general growth. During
> this
> time the connection between my Publisher and Distributor is disconnected.
> My
> Subscriber and Distributor are on the same server. I have three
> transactional publications set up and I would like to "Pause" them until
> the
> connection is restored since I know when the connection is going down.
> Is this the correct way to handle this?
> From the Distributor in the enterprise manager drill down through the
> replication monitor to the Distibution Agents and click on "Stop Agent"
> for
> all of the publication that I have. Do I also have to "Stop Agent" on all
> of
> the publications in the Log Reader Agents folder?
> This also brings up the question of "unplanned" connection loss. If for
> some
> reason the connection is lost late at night and I don't know about it
> until
> the next morning do I have to recreate snapshots or re-initialize the
> publication?
|||Does it matter what order I do this in?
|||no, you can disable the jobs first, which will mean that if they are
scheduled they won't run the next time they are scheduled. However if they
are in continuous mode, you must stop them before or after disabling them.
Then you should bounce SQL Server agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Butler via droptable.com" <forum@.droptable.com> wrote in message
news:4FFEBB746E630@.droptable.com...
> Does it matter what order I do this in?

Path to feedback?

My team keeps emphasizing the importance of community participation and value all the feedback posted in the groups, forums and all possible channels to communicate with you all, the customers; and loop the feedback provided to improve the quality of product. I personally felt the importance after being part of the community during our SP1 release cycle, it really helped to address most of the customer impact defects in our Service Pack1; however, not all could be addressed in the first service pack and we would like to give importance to them and start gathering the impact of those defects. We will evaluate and try to address most of the commonly reported customer bugs in our next Service pack, SP2.

This can be done effectively by your active participation in providing feedback. Though there are several ways to do it, the best way to track and evaluate the impact on unaddressed issues across customers, is through reporting them through MSDN product feedback center which is incorporated in SQL Server Management Studio. You can access MSDN Product Feedback Center from Management Studio by selecting “Send Feedback” menu item under “Community” Menu or by going directly to the link

http://lab.msdn.microsoft.com/productfeedback/

By using this channel, you could log bugs directly or browse over the existing bugs that correspond to the issue you are running into and vote the importance of the fix for that bug. Our team constantly watches the incoming bugs and goes over the importance of the bug to be addressed based on number of voters and the rating of how important the fix is needed.

We are starting to plan and work on our next service pack and your input is the key factor for success of SP2!

Thanks,

Gops Dwarak, SQL Server Tools Team, MSFT

I think service pack 2 is cool.The security enhancements are important, and necessary. I had no issues with it.If your looking for tech support in CT or windows help CT there are places to go, but for service pack 2, see Microsoft.|||

Using DMO to look up the distribution publisher, the publishing db and the publication name appear to be working. This is accomplished with the TransPublication dmo object.

We receive some information from the TransSubscription object, but not the DistributionJobID.

We get the correct subscriber count, article count, publiser name, subscriber server and subscriber databasename.

The DistributionJobID is all zeros, (00000000000000000000000000000000).

SQL2005 9.00.2047 with or without the backward compatible objects installed.

The objects and code has been working with SQL2000 for two years.
It is failing during our certification of SQL2005 for our distributed application.

We cannot proceed with certification and recommending SQL2005 to our 300+ customers without resolution.

|||

Hello Clifton,

I have confirmed that this is indeed a bug in our SQL2005 code base, and as far as I can tell, the bug has been there since 2002 so I am a bit confused by your comment that SQL2005 DMO has been working fine for you for two years. It would be great if you can clarify whether you really meant SQL2000 instead of SQL2005 in that comment. At the moment, we are going through a debate internally as to which delivery vehicle (QFE or SP2) we should use for the fix and I will post again to inform you of our decision. If you want to track the progress of this issue more closely, I would encourage you to log it @. https://login.live.com/ppsecure/secure.srf?lc=1033&id=64416&ru=https://connect.microsoft.com/default.aspx&tw=3600&fs=1&kv=4&ct=1150303879&ems=1&seclog=10&ver=2.1.6000.1&rn=CYWDyHyE&tpf=504beca26541936cfbb9d9e716bf9902

Or, you can let me if you want me to log an internal bug on your behalf.

Thank you for reporting the issue and sorry for the inconvenience.

-Raymond

|||

Hello Clifton,

We have decided to deliver the fix in SQL2005 SP2, if you need the fix sooner, I would encourage you to go through the product support channels to get a QFE request in.

-Raymond

|||

Thank you for the update. My notes are incorrect in one place. We are currently on SQL 2000 in production distribution of our product. The code has been working on SQL2000 for two years.

I would like to have a hotfix /qfe if possible.

|||

I am logged in to connect. I get to the feedback page, https://connect.microsoft.com/SQLServer/Feedback, but do not see a method of submitting feedback. All I have are search options. Do I need an invitation ID in order to connect/participate in the SQL server program?

|||

Hi Clifton,

The Connect site is rather new to me too so I needed to fumble a bit to navigate to the feedback form. The following is roughly what I did after the registration page:

1) Click on the "Available Connections" link on the left pane

2) Click on the "SQL Server" link

3) Click on the "Feedback" link on the left pane

4) Click on the "Submit Feedback" link

5) The next page will force you to search the existing bug database, so just type in a few keywords and hit the Search button

6) Since there will probably nott be existing issue corresponding to yours, you can hit the "Submit Feedback" button

7) Now you have the of using either the Bug form or the Suggestion form

I know this is a bit of a hassle, but your QFE request will more likely be accepted if you go through the Microsoft product support organization (call them up) rather than logging it at the Connect site which pipes directly to the product development folks like me.

Hope that helps,

-Raymond

|||

What is the target SQL 2005 SP2 release dates?

|||

Hey

The feedback site is a bit confusing.

I can't seem to find the "Submit Feedback" link.

Any ideas?

Thanks

|||

What are the target release date(s) for MS SQL 2005 Service Pack 2?

Path to feedback?

My team keeps emphasizing the importance of community participation and value all the feedback posted in the groups, forums and all possible channels to communicate with you all, the customers; and loop the feedback provided to improve the quality of product. I personally felt the importance after being part of the community during our SP1 release cycle, it really helped to address most of the customer impact defects in our Service Pack1; however, not all could be addressed in the first service pack and we would like to give importance to them and start gathering the impact of those defects. We will evaluate and try to address most of the commonly reported customer bugs in our next Service pack, SP2.

This can be done effectively by your active participation in providing feedback. Though there are several ways to do it, the best way to track and evaluate the impact on unaddressed issues across customers, is through reporting them through MSDN product feedback center which is incorporated in SQL Server Management Studio. You can access MSDN Product Feedback Center from Management Studio by selecting “Send Feedback” menu item under “Community” Menu or by going directly to the link

http://lab.msdn.microsoft.com/productfeedback/

By using this channel, you could log bugs directly or browse over the existing bugs that correspond to the issue you are running into and vote the importance of the fix for that bug. Our team constantly watches the incoming bugs and goes over the importance of the bug to be addressed based on number of voters and the rating of how important the fix is needed.

We are starting to plan and work on our next service pack and your input is the key factor for success of SP2!

Thanks,

Gops Dwarak, SQL Server Tools Team, MSFT

I think service pack 2 is cool.The security enhancements are important, and necessary. I had no issues with it.If your looking for tech support in CT or windows help CT there are places to go, but for service pack 2, see Microsoft.|||

Using DMO to look up the distribution publisher, the publishing db and the publication name appear to be working. This is accomplished with the TransPublication dmo object.

We receive some information from the TransSubscription object, but not the DistributionJobID.

We get the correct subscriber count, article count, publiser name, subscriber server and subscriber databasename.

The DistributionJobID is all zeros, (00000000000000000000000000000000).

SQL2005 9.00.2047 with or without the backward compatible objects installed.

The objects and code has been working with SQL2000 for two years.
It is failing during our certification of SQL2005 for our distributed application.

We cannot proceed with certification and recommending SQL2005 to our 300+ customers without resolution.

|||

Hello Clifton,

I have confirmed that this is indeed a bug in our SQL2005 code base, and as far as I can tell, the bug has been there since 2002 so I am a bit confused by your comment that SQL2005 DMO has been working fine for you for two years. It would be great if you can clarify whether you really meant SQL2000 instead of SQL2005 in that comment. At the moment, we are going through a debate internally as to which delivery vehicle (QFE or SP2) we should use for the fix and I will post again to inform you of our decision. If you want to track the progress of this issue more closely, I would encourage you to log it @. https://login.live.com/ppsecure/secure.srf?lc=1033&id=64416&ru=https://connect.microsoft.com/default.aspx&tw=3600&fs=1&kv=4&ct=1150303879&ems=1&seclog=10&ver=2.1.6000.1&rn=CYWDyHyE&tpf=504beca26541936cfbb9d9e716bf9902

Or, you can let me if you want me to log an internal bug on your behalf.

Thank you for reporting the issue and sorry for the inconvenience.

-Raymond

|||

Hello Clifton,

We have decided to deliver the fix in SQL2005 SP2, if you need the fix sooner, I would encourage you to go through the product support channels to get a QFE request in.

-Raymond

|||

Thank you for the update. My notes are incorrect in one place. We are currently on SQL 2000 in production distribution of our product. The code has been working on SQL2000 for two years.

I would like to have a hotfix /qfe if possible.

|||

I am logged in to connect. I get to the feedback page, https://connect.microsoft.com/SQLServer/Feedback, but do not see a method of submitting feedback. All I have are search options. Do I need an invitation ID in order to connect/participate in the SQL server program?

|||

Hi Clifton,

The Connect site is rather new to me too so I needed to fumble a bit to navigate to the feedback form. The following is roughly what I did after the registration page:

1) Click on the "Available Connections" link on the left pane

2) Click on the "SQL Server" link

3) Click on the "Feedback" link on the left pane

4) Click on the "Submit Feedback" link

5) The next page will force you to search the existing bug database, so just type in a few keywords and hit the Search button

6) Since there will probably nott be existing issue corresponding to yours, you can hit the "Submit Feedback" button

7) Now you have the of using either the Bug form or the Suggestion form

I know this is a bit of a hassle, but your QFE request will more likely be accepted if you go through the Microsoft product support organization (call them up) rather than logging it at the Connect site which pipes directly to the product development folks like me.

Hope that helps,

-Raymond

|||

What is the target SQL 2005 SP2 release dates?

|||

Hey

The feedback site is a bit confusing.

I can't seem to find the "Submit Feedback" link.

Any ideas?

Thanks

|||

What are the target release date(s) for MS SQL 2005 Service Pack 2?

Passing row data!

Hi Team,

I am trying to build a report which compose of EmployeeName and his order assigned. First of all, I created a dataset which include all of the employee name, then I created another dataset which return all the count of the order by passing the employeeName as parameter. My question is how to pass the employee name which are generated from the first dataset and then pass to the second dataset?

Any help I will greatly appreciate.

You can refer to the value of the first parameter in the query parameter value expression of the second dataset. For example, =Parameters!<param1>.Value.