Showing posts with label release. Show all posts
Showing posts with label release. Show all posts

Monday, March 19, 2012

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew

Changes in Katmai

I've got a number of questions about the forthcoming release which hopefully can be answered:

1) What version of Excel will 2008 export too? Currently exported Excel files are in native 2000/2003 format. Please don't tell me they will only export in 2007 format!

2) Can you give any details on changes we can expect to the report viewer (web version) control? In particular will it behave better in an update panel? Also we have found the only way of getting the height property to set correctly with this control is to use some very (I'm mean very) dodgy java script. This seems to be a common problem looking through various forums.

3) Will we have the option of opening linked reports through the report viewer in a new window/tab (this is common complaint from my users currently).

4) In the code window of the report designer is there any chance of getting some IntelliSense?

5) Will there be support for stored procedures that return multiple recordsets?

Thanks

Simon

Hi Simon,

I can answer #1 of your questions. Reporting Services 2008 will export to the same Excel format as before. The XLS format can be used on Excel 2000-2007.

Best regards,
Chris|||

#5: It's not on the list for SSRS 2008.

Could you please explain in more detail why this is so important?

Can you write wrapper stored procedures that return a particular recordset you are interested in?

-- Robert

|||

Thanks for both the answers so far. In response to Robert's point about #5 - it's useful rather than requirement.

I worked recently on converting an ASP based reporting system into RS. Many of the existing procs returns multiple recordsets so we struggled to reuse the code. Agreed it could be done with a wrapper anyway. This certainly wouldn't stop me wanting to upgrade!

Any comments on the other points?

Thanks again

Simon

|||Robert,

I think support for multiple resultsets would be great.

At the moment we may have a report that shows the same basic data in more than one way, eg two tables and a chart. If a single resultset can't provide the data we need to execute more than one query from within the report. I appreciate that they can run in parallel, but if they are basically hitting the same underlying data it would be better for us to have one stored procedure that returned several resultsets.

This is especially true if the query can't be done in one statement and requires the production of temporary tables/variables. If we have to have separate queries we may have to recreate the temporary data in each query, whereas if we have one procedure with multiple resultsets it gets created just once and the second resultset can build on the first, the third on the second etc.

Regards,
Andrew