I recently started learning about Cognos and I am trying to decide if I can focus on learning one tool rather than both as they seem to have similar functionality.
What are the differences between Cognos Report Studio and Cognos Workspace Advanced?
Are there some things that can be done in one but not the other?
Why do we need both tools?
This link says that there are "objects that can be inserted only in Report Studio, such as map." Those objects can be viewed but not edited in Workspace Advanced.
Does this mean that Workspace Advanced is unfinished or that the mentioned "objects" are deprecated and should no longer be used?
Cognos Workspace Advanced is the logical upgrade path for IBM Cognos BI. It brings together Query Studio, Analysis Studio, and Report Studio Express features, all in one place.
If you are working with IBM Cognos 8.x, you can continue to use your queries from IBM Cognos BI 8.x in IBM Cognos BI v10.x and newer; however if you plan to build new reports for query and analysis, it is recommended you can work with IBM Cognos Workspace Advanced.
Related
When I launch VS Ultimate 2012, and select "New Project...", I do not have the option of Templates --> Reporting Services --> Report Server Project*
When I download SQL Server Data Tools for 2012, I can get to the Feature Selection screen, but everything is grayed out. Hitting "Next" presents the error message, "To continue, select a feature to install. If all features are already selected, these features are installed. You cannot add additional features."
*https://learn.microsoft.com/en-us/sql/reporting-services/lesson-1-creating-a-report-server-project-reporting-services
I think the ReportBuilder can run as a standalone tool, however, Reporting Projects in SSDT require some parts of the SQL Server : Reporting Services installation.
See this link under Report Server Projects --> When you install Reporting Services, the following project templates are made available in SQL Server Data Tools (SSDT):
I am completely newbie to TFS. Need some help on Migration. We have a VS TFS 2015 and the requirement is to move a certain code with history and all the work items from current VS TFS 2015 to new VS TFS 2015. How can I achieve this. Any pointers will be of great help.
Just additional info. The current VS TFS 2015 was build by us on Azure and the new one is provisioned through Azure SAAS.
We don't widely support (as of August 3, 2016) importing your data from Team Foundation Server to Visual Studio Team Services. However, we have been working on a full-fidelity data import utility that will let you do this. It's currently in Private Preview and we're testing it out with a handful of customers at the moment. We've also shared some details with our Microsoft MVPs so if you have an MVP that is helping you, they will be able to help you migrate.
Feel free to vote on this User Voice item and we'll keep everyone updated there on our progress: Import data from TFS On-Premises
Tip: When the TFS to VSTS Data Import utility does become available, you'll want to make sure your TFS server is upgraded to the latest version of TFS including the latest update. At the moment, that would be Team Foundation Server 2015 Update 3.
You can use OpsHub Visual Studio Online Migration Utility.
OpsHub Visual Studio Migration Utility : Supports migration of source
code and work items from TFS 2010, TFS 2012, TFS 2013, and TFS 2015 to
Visual Studio Team Services.
I have always used Visual Studio to create my SSRS reports but I have recently been advised to switch over to and use report builder 3.0. I am wondering, are there are any advantages to using one over the other for SSRS report development?
Any known compatibility issues when trying to edit an .rdl in Report Builder 3.0 that was created in Visual Studio 2012?
I would say that the Report Designer (Visual Studio) targets Developers that have a Visual Studio edition, whereas Report Builder targets non-developer users, familiar with Office applications that will just need to let ClickOnce install Report Builder (but developers can use it too).
Report Builder has less features, but you can still do plenty of things with it, so it can be useful when you need to do a quick fix of the report, and you would take more time to do it with Report Designer.
Having said that, the following scenario is completely valid:
Create a report in the Report Designer
Deploy the report
Do a fix with Report Builder
Save the report (= deploys the report)
Here are the official descriptions of each environments:
Report Designer
Report Designer in Business Intelligence Development Studio is a
report authoring environment that is hosted in Microsoft Visual
Studio. Use Report Designer project and solution files to organize and
maintain a master copy of report definitions, report parts, shared
data sources, shared datasets, and resource files such as images and
ESRI shapefiles for maps.
Report Builder
Report Builder is a report authoring environment for business users
who prefer to work in the Microsoft Office environment. You work with
one report at a time. You can modify a published report directly from
a report server. You can quickly build a report by adding items from
the Report Part Gallery provided by report designers from your
organization.
More info on the differences between Report Designer and Report Builder:
Designing Reports in Report Designer and Report Builder 3.0 (SSRS)
Comparing Report Authoring Environments
There are some known compatibility issues with Visual Studio's newer versions and SSRS. If you want to preview your report, you will have some issues using newer versions of SSRS, and they will error out. That being said, once you publish them, they appear to work without issue.
Hope that helps.
I'm upgrading a VS 2010 database extension project to VS 2012 SSDT extension project now that extensibility is in SSDT. I used base.PublishMessage to output messages as my extension was running. In SSDT, base.PublishMessage is not displaying in the output window. I was wondering if there are other settings I need to make. I'm not finding a lot of info out there yet and the online doc and samples are sparse.
In cognos, we design a model using framework manager and then we can use the model to build reports in Query Studio/Report Studio. However, there is another report viewing utility called cognos viewer. Why we need cognos viewer when everything can be done in query studio or report studio? Is it because cognos sdk uses cognos viewer to render the reports or any other reason for it?
The Cognos viewer is simply the page which is shown when you're viewing report output. For example :
click on a report in Cognos Connection, it runs (you see the hourglass), then when its finished, you see the output in the Cognos viewer
run the report from Report Studio, it runs (hourglass shown), then when its finished, you see hte output in the Cognos viewer