We are pleased to announce a FREE online training in Cognos Query Studio.Query studio is a Cognos tool that can whip up adhoc reports and analysis for users by users.
Introduction to Query Studio
Examine Query Studio and its interface
Add and save data to ad hoc reports
View data by using appropriate charts
Create list, grouped list, and crosstab reports
Filter and sort your reports
Create detail and summary calculations
Move columns and reorder columns
New features in Cognos8.4 Query Studio
Best Practices and optimization of queries
Please mark your calendars for August 21st 2009 between 10:00-11:00 AM. Please email support@softpath.net to confirm your seat and receive a copy of the training documentation.
Thursday, July 23, 2009
Wednesday, July 15, 2009
Pointers while Integrating/migrating- M&A scenario
Here are some general pointers to be kept in mind, while planning migrations, upgrades, conversions and the likes. Most of these recommendations can be made only after a thorough understanding of client systems architecture, maturity of their BI systems and their future plans. Anyways here is an appetizer.
1. Assess your architecture
2. Huge performance gains can be achieved by having dedicated servers for reporting services, batch report services, Agent and monitoring services and presentation services respectively.
3. Gateways
ISAPI is most recommended gateway. Also improve performance by adding multiple gateways.
Especially, if you have multiple locations for your servers
4. Perform Capacity Planning Exercise. Most BI tools offer pre built exercises.
5. If switching Security namespaces, you will encounter a lot of accessibility issues and will not be able to export personal content
6. If you have external vendors/clients accessing your BI portal the firewalls can cause accessibility issues. You will have to configure your firewalls and gateways to support multiple dispatchers.
7. Consider virtualization of your servers to cut costs
8. If in the near future, you plan on merging data sources multiple companies, you might have to plan back up of existing Models, packages and data source connections. Also, perform a step by step deployment into new environments or domains.
Some Challenges you might come across are:
1. Accessing cross company portals. Are you going to have 2 portals? Are you going to add users in two domains?
2. If development and support teams are in Domain A and have to support users in domain B. Developers and support Team, ticket management has to work across domains with additional privileges. This might not seem like huge liability but it can be time consuming to get it up and running
3. There will be a need for more licenses and appropriate capabilities
4. You will have to assess he hardware requirements and configuration
However, this is a very good time and opportunity to introduce new BI technologies and practices.
- You could start a BICC ( BI Competency Center)
- Upgrade to newer versions of the tools
1. Assess your architecture
2. Huge performance gains can be achieved by having dedicated servers for reporting services, batch report services, Agent and monitoring services and presentation services respectively.
3. Gateways
ISAPI is most recommended gateway. Also improve performance by adding multiple gateways.
Especially, if you have multiple locations for your servers
4. Perform Capacity Planning Exercise. Most BI tools offer pre built exercises.
5. If switching Security namespaces, you will encounter a lot of accessibility issues and will not be able to export personal content
6. If you have external vendors/clients accessing your BI portal the firewalls can cause accessibility issues. You will have to configure your firewalls and gateways to support multiple dispatchers.
7. Consider virtualization of your servers to cut costs
8. If in the near future, you plan on merging data sources multiple companies, you might have to plan back up of existing Models, packages and data source connections. Also, perform a step by step deployment into new environments or domains.
Some Challenges you might come across are:
1. Accessing cross company portals. Are you going to have 2 portals? Are you going to add users in two domains?
2. If development and support teams are in Domain A and have to support users in domain B. Developers and support Team, ticket management has to work across domains with additional privileges. This might not seem like huge liability but it can be time consuming to get it up and running
3. There will be a need for more licenses and appropriate capabilities
4. You will have to assess he hardware requirements and configuration
However, this is a very good time and opportunity to introduce new BI technologies and practices.
- You could start a BICC ( BI Competency Center)
- Upgrade to newer versions of the tools
Subscribe to:
Posts (Atom)
