Hello-- I have a very frustrating problem. But given that this is a development forum, I'll keep that for my 'Envelope Lickers Rehab' and instead talk about an issue I'm having. I have a very large query (line-wise) that executes in less than a minute when run from the SQL Management Studio as well as via Excel Services. It is a stored procedure with one parameter. When I try to prime the designer with this query it gives me the following message: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated." Any advice would be appreciated. I've considered cracking open the xml source and manually creating the fields, but I'd rather not go there. Thanks in advance. - Reg

Open your data source, in the Connection Properties window (click on Edit button beside Connection String pane), click on Advanced button, and then set the Time Out property to a large value. (from SaeedB http://social.msdn.microsoft.com/Forums/eu/sqlreportingservices/thread/f7eff76a-3041-445b-a23b-4d1acf604e54)Josh Ash

Open your data source, in the Connection Properties window (click on Edit button beside Connection String pane), click on Advanced button, and then set the Time Out property to a large value. (from SaeedB http://social.msdn.microsoft.com/Forums/eu/sqlreportingservices/thread/f7eff76a-3041-445b-a23b-4d1acf604e54)Josh Ash

Hello, Check out the thread below. It will help you. http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0b7fb59d-dcf9-4bbb-89a8-764a1ecee822

This did not resolve the problem. The funny thing is that I've had smaller queries (in terms of number of lines) that took longer to execute (one took 16 minutes) that were able to recognized in report builder. This query executes in a minute but is very long and it gives me the referenced error.

Checking out the links you included I worked around this issue by 'priming' report builder with the fields of the query using a single row representation of the columns with dummy data. Then I swapped out this row for the real query and I was able to trick the interface. Still would like to know how to avoid this workaround, but as it's a one time thing, I guess I'm satisfied. I'll go back to licking envelopes now.

Checking out the links you included I worked around this issue by 'priming' report builder with the fields of the query using a single row representation of the columns with dummy data. Then I swapped out this row for the real query and I was able to trick the interface. Still would like to know how to avoid this workaround, but as it's a one time thing, I guess I'm satisfied. I'll go back to licking envelopes now.

Hello RegDwight, You can refer to the following article about Setting Time-out Values for Report and Shared Dataset Processing, please see: http://technet.microsoft.com/en-us/library/ms155782.aspx Regards, Bin LongBin Long TechNet Community Support

Hello RegDwight, You can refer to the following article about Setting Time-out Values for Report and Shared Dataset Processing, please see: http://technet.microsoft.com/en-us/library/ms155782.aspx Regards, Bin LongBin Long TechNet Community Support