October 30, 2013 at 9:03 am
All,
we are going to migrate 41 Cognos report to SSRS. This project is in initial stage now.
As part of this migration, I have done the below analysis on COGNOS side for all the reports.
1) No of SQL Call/Procedure Call
2) No of Expressions
3) No of Filters
4) Chart Type
5) Input Parameters
6) Execution Time
7) Header / Font Size / Colors / Note
is there any anlysis needs to be done before starting the project?
what are all the constraints will occur during this migration?
is there any functionality/logic which need more attention in SSRS?
is there any functionality/logic which is easy in COGNOS but not in SSRS?
where I have to focus on SSRS side for completing the report without any issue?
Note: I am going to develop SSRS report first time in real time.
Inputs are welcome!
karthik
October 31, 2013 at 6:16 am
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlreportingservices is a very useful Website for SSRS questions.
WROX - Professional Microsoft SQL Cerver 2008 Reporting Services book is a very useful reference and how to book.
October 31, 2013 at 6:26 am
Cognos handles parameters way better than SSRS.
In Cognos you have prompt pages, while in SSRS you have almost no control over how parameters are prompted to the end users.
SSRS is - in my opinion - sometimes a bit easier on the layout.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 3, 2013 at 11:40 pm
Thanks.
any other inputs?
karthik
November 5, 2013 at 7:40 am
Consider packaging your SQL queries in stored procedures, and not imbed the query in the report. (There are about as many people who would fight to the death to support this viewpoint as there are who would fight to the death supporting imbedding SQL in the report.)
If you do package the SQL in a stored procedure, you can test the SQL completely independently of the report. I have often found with complex reports that have imbedded SQL, it can be difficult to troubleshoot if the problem is in the SQL or the report definition.
You can get the SQL that is used for the report out of Cognos.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
November 6, 2013 at 12:10 pm
You also might want to check the schedules in Cognos.
As someone above stated, ensure you know where the data is coming from.
Are there any security settings you need to be concerned with?
Hopefully you can do in parallel environments to validate the data on the new report.
Good Luck:)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply