by Shruti Sinha, Project Manager
With SQL Server 2008 finally a real option for organizations, IT departments need to address bottom line tactical operational issues before deployment. Questions they need to address are – will my legacy applications still work as expected or do I need to reinvest and redeploy everything.
The table below answers some of these questions.
| Usage Scenario | Support Statement |
| Applications built for RS 2005, 2005 SP2 | Will work |
| Applications built for RS 2000 | RS 2000 SOAP APIs are not supported |
| RS 2005 RDL, RS 2000 RDL | URL access will work Can publish Cannot edit |
| RS Database hosted in SQL 2005 | Will work |
| RS Database hosted in SQL 2000 | Not supported |
| VS 2005 ReportViewer Control | Supported |
| SharePoint integration | Supported |
| SharePoint v2 WebParts | Supported |
Similarly when upgrading to SSRS 2008 here are some things to remember
• RS 2008 server WILL support running legacy RDL
– RS 2005 RDL
– RS 2000 RDL
• RS 2008 designer has PARTIAL support for legacy RDL
– Converts legacy RDL to 2008 RDL
– If you don’t convert, you cannot open the RDL in the 2008 designer
– CANNOT save to legacy RDL formats
• Published reports upgrade on the fly
• RS 2008 RDL will NOT work with SQL 2005
• SQL 2005 Report Engine is deprecated
– Snapshots created in 2000 or 2005 WORK in SQL 2008
– They will not work in a version after 2008
No comments:
Post a Comment