Purchase your Section 508 Compliance Support guide now!

Purchase your Section 508 Compliance Support guide now!

Free Cognos Sdk ebook guide and code samples

If you would like to receive a Free Cognos Sdk ebook guide and code samples then email us at businessintelligencecentre@gmail.com and mention "Free Cognos Sdk ebook guide and code samples" in the message body.

Sent wirelessly from my BlackBerry device on the Bell network.

Envoyé sans fil par mon terminal mobile BlackBerry sur le réseau de Bell.

Tools

Tools

Cognos 8 BI Dispatcher Diagnostic

http://cognos8diagnostic.blogspot.com/search/label/IBM%20Cognos%208%20BI%20Dispatcher%20Diagnostic

View the Cognos 8 BI Dispatcher Diagnostic tool and others at http://cognos8diagnostic.blogspot.com.

IBM Cognos 8 BI – Query Across Dimensional Data Sources

In some cases, a comparison between two dimensional data sources may be required where it is not feasible to contain all the data in one data source.
For example, a company may capture a rolling twelve month period at the month level in an IBM Cognos 8 PowerCube, which is built at the end of each month. Due to the volume of data captured, the size of the PowerCube can be well over one gigabyte in size and require a longer build time. The same company may also capture the current month's data at the day level and build this cube once a day. The company may want to compare their current month's performance each day with that of the previous month's performance to see if they are on track.
Using the following technique, the company can compare the current month's data, found in the Current Month PowerCube, with the previous month's data found in the Rolling Twelve Month PowerCube.

Create a Package with Multiple Cubes
To compare the data between the two PowerCubes in a report, both PowerCubes must be contained in the same IBM Framework Manager package and published to IBM Cognos 8.
  1. To create this package, ensure data sources are created for each PowerCube and then import them into Framework Manager as shown below.

    Project Viewer in Framework Manager showing two PowerCubes after import

  2. Create a package.

    Project Viewer in Framework Manager showing a newly created package

  3. Ensure the package contains both PowerCubes.

    Framework Manage package definition showing two PowerCubes selected

  4. Publish the package to IBM Cognos 8.

Create a Union Query
The following steps will illustrate how to relate the data from the two PowerCubes using a Union object.
  1. Open IBM Cognos Report Studio and select the package just published.
  2. Select Blank for the new report.
  3. Using the Query Explorer, click on Queries.

    Report Studio - Query Explorer

  4. From the Insertable Objects pane, add three queries to the middle pane.

    Report Studio - query work area

    Two of these queries will be used as base queries, one for each PowerCube. Each query will contain the same number of items with the same names and in the same order so that they can be unioned in the third query.
  5. Rename the queries as shown below.

    Report Studio - query work area with renamed queries

  6. Double-click the Current Month query and then add the following items from the Current Month cube to the query.
    • Month level from the Time dimension
    • Product line from the Products dimension
    • Order method type from the Order method dimension
    • Quantity from Measures
    • The results appear as shown below.


    Report Studio - Data Items pane in query work area

    A data item will be added to this query to identify items from this query as representing the current month's data.
  7. Under Insertable Objects, click the Toolbox tab and then drag a Data Item to the query.
  8. In the Expression Definition pane, type 'Current Month'.

    Report Studio - Data Item Expression dialog

  9. Click OK, and then rename the data item to Month Flag.
  10. Using the Query Explorer, navigate to the Previous Month query.

    In this query, the Month data item will be a calculation that uses a dimensional function to retrieve the last month in the cube. The last month in the rolling 12 month cube contains the previous month's data.
  11. From the Toolbox, drag a Data Item to the query, and then in the Expression Definition pane, type closingPeriod(.
  12. Under Available Components, expand the Rolling 12 Month cube, add the Month level from the Time dimension to the expression, and then type ).
    The expression appears as shown below.
    closingPeriod([Sales and Marketing - Rolling 12 Months].[Time].[Time].[Month])
  13. Click OK, and then rename the data item to Month.
  14. Add the following items from the Rolling 12 Month cube to the query.
    • Product line from the Products dimension
    • Order method type from the Order method dimension
    • Quantity from Measures
  15. Under Insertable Objects, click the Toolbox tab and then drag a Data Item to the query.
  16. In the Expression Definition pane, type 'Previous Month'.

    Report Studio - Data Item Expression dialog

  17. Click OK, and then rename the data item to Month Flag.
  18. From the Query Explorer, click on Queries, and then add a Union item to the right of the Combined Cubes query.

    Report Studio - query work area with Union object added

  19. Drag the Current Month query to the top dotted box and the Previous Month query to the bottom dotted box of the Union item.

    Report Studio - query work area with queries added to a Union item

  20. Double-click the Combined Cubes query, and then add all the items from Union1 to the query.

    Report Studio - query work area with query items added from a union

Now if the tabular data for this query is viewed, there will be rows for the current month and the previous month as indicated by the Month Flag item.

Cognos Viewer showing the tabular data for the union query
Data is retrieved from both cubes, the current month, in this case July 2007, and the previous month, June 2007.

Create Calculations to Separate Current and Previous Month Values
Since the result set of the Combined Cubes query is a union from which current month and previous month values are to be compared, the quantity values need to be separated based on the Month Flag values. To do this, two calculations will be created, one for the current month values and one for the previous month values.
  1. In the Combined Cubes query, from the Toolbox, add a Data Item to the query.
  2. In the Expression Definition pane, create the following expression.

    case when [Union1].[Month Flag] = 'Current Month' 
    then [Union1].[Quantity] end

    This expression checks the value of the Month Flag. If it is 'Current Month' then retrieve the Quantity value.
  3. Click OK, name the data item Current Month, and then set the Regular Aggregate property to Total.

    Report Studio showing property settings for a new data item

  4. Create a second Data Item called Previous Month with the following expression and set the Regular Aggregate property to Total.

    case when [Union1].[Month Flag] = 'Previous Month'
    then [Union1].[Quantity] else 0 end

    This expression checks the value of the Month Flag. If it is 'Previous Month', then retrieve the Quantity value, otherwise make the value zero. The zeros are added so that null values are not returned. This is required for a future Boolean variable calculation which will compare the Current Month and Previous Month values. The Combined Cubes query now contains the following items.

    Report Studio showing the Data Items pane for the Combined Cubes query


Create the Report and Add Conditional Formatting
Now that the two cubes have been unioned together and values have been created to compare current month data to previous month data, the report layout can be created. The report in this example will be a crosstab.
  1. Using the Page Explorer, navigate to Page1, and then from the Toolbox, add a Crosstab object to the report layout.
  2. Select the crosstab and then in the Properties pane, change the Query property to use the Combined Cubes query.
  3. Under Insertable Objects, click the Data Items tab, and then drag items from the Combined Cubes query to the crosstab as shown below.

    Report Studio showing a crosstab

  4. Using the Condition Explorer, click Variables, and then add a new Boolean Variable object to the Variables pane.
  5. In the Expression Definition of the new Boolean Variable, create the following expression.

    [Combined Cubes].[Current Month] > [Combined Cubes].[Previous Month]

  6. Click OK, and then rename the new variable to var_Month_Comparison.

    Report Studio showing Variables pane and properties

  7. Using the Page Explorer, navigate back to Page1.
  8. Select the fact cells for the Current Month column.
  9. In the Properties pane, beside the Style Variable property, click the ellipsis.
  10. Under Variable, select var_Month_Comparison from the drop down list, and then click OK.
  11. Using the Condition Explorer, under var_Month_Comparison, click Yes.
  12. In the Properties pane, change the Foreground Color property for the Current Month fact cells to Green.

    Report Studio showing conditional formatting of fact cells

  13. Using the Condition Explorer, under var_Month_Comparison, click No.
  14. In the Properties pane, change the Foreground Color property for the Current Month fact cells to Red.

    Report Studio showing conditional formatting of fact cells

  15. Run the report. The results appear as shown below.

    Cognos Viewer showing conditionally formatted report output of a union query between two PowerCubes

    Current month values that are less than those of the previous month are highlighted in red, and those that are greater than or equal are highlighted in green.
    For a consistent display of null values, a conditional style can be used to hide the zeros displayed in the Previous Month column. Remember, the zeros were used to replace null values, which allows the Boolean Variable calculation [Combined Cubes].[Current Month] > [Combined Cubes].[Previous Month] to behave as expected.
  16. In Report Studio, right-click the fact cells of the Previous Month column, point to Styles, and then click Conditional Styles.
  17. Click the New Conditional Style icon, and then click Advanced Conditional Style.

    Report Studio - Conditional Styles dialog
  18. Click the New Advanced Condition icon in the lower left corner, and then in the Expression Definition pane, create the following expression.
    [Combined Cubes].[Previous Month] = 0

  19. Click OK, and then click the Edit icon (pencil) beside the new condition.
  20. Click on the Advanced tab, and then from the Visible drop down list, select No.
  21. Click OK to all three open dialogs, and then run the report again.

    Cognos Viewer showing conditionally formatted report output of a union query between two PowerCubes with zeros hidden

    The zeros are now hidden from the Previous Month column.

Conclusion
Using the techniques in this document, authors can compare and conditionally format values from different dimensional sources.


Download
DescriptionNameSizeDownload method
Zip fileQuery_Across_Dimensional_Data_Sources.zip3,430KBHTTP

deploying IBM Cognos 8 with Teradata as a data source.



This document provides a set of tips and techniques when deploying IBM Cognos 8 with Teradata as a data source.
The tips and techniques explained below are intended as a "help" tool; therefore, they should be treated as a recommendation or suggestion only. Every customer site is different; therefore, some of these tips and techniques may or may not apply.
The tips and techniques described below are an accumulation of experiences from the field at different customer sites.
This document should also be considered as "work in progress". New tips and techniques will be added as time goes by, and some of the existing tips and techniques listed below could be amended at any time without prior notice.
Document prerequisites
This document assumes the reader has a basic knowledge of Teradata, SQL, databases and a strong knowledge of IBM Cognos 8. This document also assumes the reader has a proficient knowledge of IBM Cognos 8 implementation and modeling proven practices.
It is strongly recommended that the reader be very familiar with the items listed in the References section below.
Scope of document
This document has been written for the following versions:
  • IBM Cognos 8.2 BI, IBM Cognos 8.3 BI
  • Teradata EDW V2R6.2
IBM Cognos integrates with Teradata at different levels. This document is broken down into the different levels of integration and the corresponding tips and techniques.
This document is based on a Teradata Star/Snowflake physical tables schema.
References
  • IBM Cognos Product Documentation
    • Data source connectivity
    • Framework Manager
  • Teradata documentation
    • Teradata Product Documentation
    • Teradata Deployment Best Practices
  • IBM Cognos Proven Practices Documentation (other IBM developerWorks documents found under the Modeling section)
    • IBM Cognos 8 Framework Manager - Flexible Model Solutions
    • IBM Cognos 8 Framework Manager - Durable Models
    • Modeling with Prompts and Parameter Maps

Teradata Deployment
Profile data and identify Primary Index (PI) candidates
A typical mistake in designing a Teradata Primary Index is to simply combine a number of columns to evenly distribute data across Teradata AMPs. While data distribution is one of many design criteria, the primary focus should be on the business questions that will be posed by the business. A primary index is a unique feature of Teradata’s database – it offers the benefit of an index without the traditional overhead associated with an index.
There are two types of Primary Indexes – Unique Primary Index (UPI) and Non-unique Primary Index (NUPI). If there is a column in a table that constitutes a common access path (i.e., queries leverage that column most commonly to retrieve data from the table) then it can be considered a candidate for Primary Index. If it is unique then it would be a candidate for UPI; else it would be a candidate for NUPI.
Any query that utilizes the Primary Index column will encounter faster response times.
In order to define a quality primary index, data profiling (sometimes referred to as data analysis) is required. The following query can be used to choose a PI for certain tables based on data access and also to provide reasonable data distribution across the different AMPs:
select hashamp(hashbucket(hashrow())), 
count(*)
from group by 1
Leverage Teradata Database Statistics
Regardless
of schema (3NF or Star), the Teradata query optimizer relies on
statistics to help it determine the best way to access data. Statistics
also help the optimizer ascertain how many rows exist in tables being
queried and predict how many rows will qualify for given conditions.
When
trying to improve performance of a specific report, there is a simple
method for determining which statistics are worth collecting.
  1. First, connect to the data source using Teradata SQL Assistant.

  2. Execute a statement to turn on diagnostic helpstats for the remainder of the session ("diagnostic helpstats on for session").

  3. Next, copy the report's native Teradata SQL from within IBM Cognos Report Studio.

  4. Paste the SQL into Teradata SQL Assistant's Query frame.

  5. Press the F6 key to perform an Explain.

"High Confidence" results indicate columns that are good candidates for collecting statistics.
Leverage partitions and Primary Indexes in filters and prompts.
When
authoring reports, be sure to leverage columns that have indexes
wherever possible. If the database designer has created a Primary
Partition Index on a table, queries should incorporate the partitioning
column. When a join is executed that incorporates an index that is
selective, any column in the dimension table can be used. The optimizer
will deduce key value selection based on the functional dependency of
the column within the row.
When defining prompts in Report Studio, you can take advantage of two separate
properties: "Use Value" and "Display Value". For example,
designate Sales Org Code as the "Use Value" and Sales Org Description as the "Display Value".
Partition elimination can be achieved by passing a literal value or a join.
Leverage Teradata Soft Referential Integrity (Soft RI)
Relationships
between tables provide valuable input to the Teradata database
optimizer. These relationships are identified through the creation of
constraints between tables. The data volumes in data warehouse
databases make traditional referential integrity constraints too
costly. As a result, Teradata created Referential Constraints, which
are commonly referred to as "Soft RI", by adding the phrase "WITH NO
CHECK OPTION" to the constraint. This feature identifies which side is
the master entity (driver) and which entity is the child and enhances
the data access plan. Soft RI in conjunction with statistics may enable
the optimizer to generate a more efficient access path.
The following are some considerations for implementing Soft RI:
Ensure
that the column on which the Primary Key (maybe same as Primary Index
in many cases) is to be defined in the driving table/dimension is
unique. Non-unique columns cannot provide a Foreign Key reference to a
different table.
Ensure that both the Primary Key in the
driving table and the Foreign Key in the target table are of the same
datatype. The key columns on both the tables cannot be compressed.
The statement to create Soft RI is shown below:

ALTER TABLE  
FOREIGN KEY ()
REFERENCES WITH NO CHECK OPTION ();
After enabling Soft RI, ensure that appropriate statistics are collected on all columns in the constraint.See the section "Using Referential Integrity" in the Teradata Database Administration manual.

Teradata ModelingAvoid Outer Joins in the Physical Data ModelOuter joins may have a negative impact on query performance. Thisrecommendation applies to both 3NF and Star schemas for joins betweenvery large tables and is not specific to Teradata.Outer joins can be converted to inner joins by augmenting facttables with default values for foreign keys. This performance enhancingchange can be implemented without restructuring the physical data model.ODBC ConfigurationTeradata recommends their ODBC driver as the preferred method ofconnectivity. This ODBC driver has several options for which thefollowing is recommend.Store User credentialsIf the customer would like to use only one TD user account as aproxy user, then the user credentials should be stored at the ODBCdriver level rather than at the IBM Cognos 8 Connection level.In Windows, fill the "Username:" and "Password" fields:OBBC Driver Setup for Teradata Database dialog In UNIX, fill the options "Username=" and "Password=" in the ".odbc.ini" file. For example:
[ODBC]
InstallDir=/usr/odbc
Trace=0
TraceDll=/usr/odbc/lib/odbctrac.so
TraceFile=/usr/odbcusr/joe/trace.log
TraceAutoStop=1
[ODBC Data Sources]
financial=tdata.so
[financial]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R5.1
DBCName=123.45.67.10
DBCName2=123.45.67.11
DBCName3=123.45.67.12
Username=odbcadm
Password=password

Database=
DefaultDatabase=sales
When using this technique, it is recommended not to check the “UserID” option when creating the data source in IBM Cognos Administration.IBM Cognos Connection - New Data Source Wizard Use X ViewsThe TD ODBC driver provides several options.OBBC Driver Setup for Teradata Database dialogIt is strongly recommended to turn off the option "Use X Views".This option will extend the time of Metadata calls on objects that arenot used by the IBM Cognos application.In Windows, deselect the option from the Teradata ODBC Driver Options.Teradata ODBC Driver Options In UNIX, ensure that the option "UseXViews=" is not in the".odbc.ini" file. If the option is in the file, then make sure that isset to "No". For example:
[ODBC]
InstallDir=/usr/odbc
Trace=0
TraceDll=/usr/odbc/lib/odbctrac.so
TraceFile=/usr/odbcusr/joe/trace.log
TraceAutoStop=1
[ODBC Data Sources]
financial=tdata.so
[financial]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R5.1
DBCName=123.45.67.10
DBCName2=123.45.67.11
DBCName3=123.45.67.12
Username=odbcadm
Password=password
Database=
DefaultDatabase=sales
UseXViews=No
No HELP DATABASEThe "No HELP DATABASE" option can also be turned on. This is veryvaluable when a multiple logical database query is sent to Teradata.Teradata will do all of the processing versus IBM Cognos 8 forcing thejoin in the middle tier.In Windows, check the option "No HELP DATABASE".Teradata ODBC Driver Options In UNIX, ensure that the option "DontUseHelpDatabase=" is set to "Yes" in the ".odbc.ini" file. For example:
[ODBC]
InstallDir=/usr/odbc
Trace=0
TraceDll=/usr/odbc/lib/odbctrac.so
TraceFile=/usr/odbcusr/joe/trace.log
TraceAutoStop=1
[ODBC Data Sources]
financial=tdata.so
[financial]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R5.1
DBCName=123.45.67.10
DBCName2=123.45.67.11
DBCName3=123.45.67.12
Username=odbcadm
Password=password
Database=
DefaultDatabase=sales
DontUseHelpDatabase=Yes
ODBC Advanced optionsThe TD ODBC also provides advanced options.Teradata ODBC Driver Options In the advanced options, the "Maximum Response Buffer Size" can beadjusted. The default value is 8192. The maximum allowed value is1048575. There is no specific value that is recommended. Every customersite will require a different value. If the value is too high, it willimpact metadata calls. There is no side effect for using a low value.This option should be fully tested prior to deploying the option in Production.In Windows, enter the value in the "Maximum Response Buffer Size:" option. Teradata ODBC Driver Options In UNIX, use the option "MaxRespSize=" with the desired value. For example:
[ODBC]
InstallDir=/usr/odbc
Trace=0
TraceDll=/usr/odbc/lib/odbctrac.so
TraceFile=/usr/odbcusr/joe/trace.log
TraceAutoStop=1
[ODBC Data Sources]
financial=tdata.so
[financial]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R5.1
DBCName=123.45.67.10
DBCName2=123.45.67.11
DBCName3=123.45.67.12
Username=odbcadm
Password=password
Database=
DefaultDatabase=sales
MaxRespSize=65477
If after changing this option, FM generates an error message whenimporting objects into the model, then the "Maximum Response BufferSize" needs to be reduced. Also test running the reports over and over.Test running one report several times before moving to the next report.Custom Catalog ModeIt has been noted that a small performance gain is achieved whenturning on the "Enable Custom Catalog Mode for 2.x Applications".This option should be fully tested prior to deploying the option in Production.In Windows, turn the option "Enable Custom Catalog Mode for 2.x application" on.Teradata ODBC Driver Options In UNIX, turn on the option “USE2XAPPCUSTOMCATALOGMODE=”. For example:
[ODBC]
InstallDir=/usr/odbc
Trace=0
TraceDll=/usr/odbc/lib/odbctrac.so
TraceFile=/usr/odbcusr/joe/trace.log
TraceAutoStop=1
[ODBC Data Sources]
financial=tdata.so
[financial]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R5.1
DBCName=123.45.67.10
DBCName2=123.45.67.11
DBCName3=123.45.67.12
Username=odbcadm
Password=password
Database=
DefaultDatabase=sales
USE2XAPPCUSTOMCATALOGMODE=Yes

IBM Cognos ConnectionWhen creating an IBM Cognos 8 data source connection, use the "Teradata (ODBC)" and not the "ODBC" option.IBM Cognos Connection - New Data Source Wizard

IBM Cognos ModelingIBM Cognos 8 metadata modeling for Teradata is probably the most important task in the IBM Cognos 8 implementation.It is very important to receive some form of education on modelingin Framework Manager for a successful implementation and to takeadvantage of some of the IBM Cognos Modeling Proven Practices documentslocated on the IBM developerWorks website. Teradata best practices recommend connecting directly to theTeradata Business Views Layer (also known as the Semantic Views Layer)and not the Teradata Physical Tables. IBM Cognos 8 will be able toconnect to either level; however, it is recommended to follow theTeradata best practices.The Teradata Business Views should prevent READ Locks on the table:
Create/Replace view {view name} as Locking Row for Access Select * From {table name}
Local CacheIBM Cognos Framework Manager offers the ability to re-use a localcache of information rather than going to Teradata every single time.It is recommended to turn this option on unless going against theTeradata Active Data Warehouse. To do so, under the Project menu,select Edit Governors and then select Allow usage of local cache.Framework Manager - Governors dialog SQL Join SyntaxSQL Join Syntax can have an impact on performance. It has been notedthat better performance gains can be achieved by using Explicit Joinsvs. Implicit Joins.To ensure the desired SQL Join Syntax is used, turn on the option in the project Governors dialog.Framework Manager - Governors dialog WITH ClauseA small performance gain has been noticed when turning off the "Use WITH clause when generating SQL" option.Framework Manager - Governors dialog Join on Like Data TypesQuery performance can be improved by leveraging like data types(i.e. INT32 to INT32) when joining foreign keys in a fact table toprimary keys in a dimension table. By making data types consistentwithin the DDL, there is less overhead associated with conversion ofdata at query run time.Create Durable ModelsTo minimize the impact of changes to an underlying data source, IBMCognos recommends using a layered approach to model design within IBMCognos Framework Manager. For information on how to implement this,please refer to the IBM Cognos Proven Practice document titled "IBMCognos 8 Framework Manager - Durable Models".Avoid Additional Metadata CallsIt is strongly recommended to minimize metadata calls to Teradata.To achieve this, keep the database/physical layer as clean as possible.Changes to this layer that can cause additional metadata calls includealtering the simple select statements on the SQL tab of a data sourcequery subject definition, and adding calculations or filters. Thosetypes of activities can take place at a higher level of modeling, suchas in a Business View of the metadata comprised of model query subjectsrather than data source query subjects. To find out if a database/physical query subject is making metadata calls or not, look at the "Response" of a Query Test.Example of a Query Test that is making Metadata Calls:Framework Manager - Query Subject Definition showing the Query Information tab Example of a Query Test that is NOT making Metadata Calls:Framework Manager - Test Results dialog showing the Query Information tab To avoid metadata callbacks to the underlying data source, onerecommendation is to create a set of dedicated query subjects toprovide the cached metadata. To do so, one would create a FrameworkManager namespace in which all imported tables and views remainunmodified. These unmodified data source query subjects can then bereferenced by other query subjects, calculations, and filters withinthe model.

Working in Report StudioWhen creating highly formatted reports using Report Studio, there are several advanced options that should be considered.ProcessingProcessing should be set as "Database only" as much as possible.Avoid "Limited Local" whenever possible. If "Limited Local" needs to beset, then re-visit the Framework Manager model to see if there is a wayto pass the processing to Teradata.Report Studio - Query Explorer and Properties Query Joins, Unions, Intersections and ExceptsIBM Cognos 8 provides the ability for the report developer tocombine their analysis across multiple Queries. This is very powerful;however, when the majority (if not all) of the reports require a largenumber of queries to be joined at the report level, it is recommendedto re-visit the database schema within Teradata to better leverage theprocessing power of the Teradata database.Execution MethodIBM Cognos 8 provides the ability to run multiple report queriesconcurrently or sequentially. By default, IBM Cognos 8 will run thequeries sequentially. The report developer can change the executionmethod to concurrent if desired.NOTE: Turning the option to Concurrent does NOT mean that the reportwill run faster. There are several reasons for which a report willprovide better performance when running sequentially. This feature mustbe fully tested before deploying the report to production.

Testing and TroubleshootingIt is recommended to have access to non-IBM Cognos tools whentesting and/or troubleshooting. For example, if a Query Subject isgiving errors, the SQL Statement can be copied and pasted in one ofthese tools to validate the SQL Statement.Some Tools that are available are:
  • On Windows, Teradata SQL Assistant
  • On UNIX, Adhoc.c sample application
Both tools will connect to Teradata via ODBC, which will also validate the SQL Statement against the ODBC driver as well.

SummaryIBM Cognos and Teradata provide a very powerful BI/EDW solution totheir customers. The tips and techniques listed above are a combinationof observations at different customer sites. It is strongly recommendedto fully test each tip or technique listed above to ensure maximumperformance at your specific site.

Impromptu web services

http://download.boulder.ibm.com/ibmdl/pub/software/data/cognos/documentation/docs/en/cws/1.1/rdm_cws.pdf



Have you tried to get at some legacy cognos impromptu reports within your business intelligence solution? Are you trying to access the specific oracle or db2 database tables? Install the cognos web services to get started.

Sent wirelessly from my BlackBerry device on the Bell network.

Envoyé sans fil par mon terminal mobile BlackBerry sur le réseau de Bell.

Cognos 8 Diagnostic: Cognos 8 Diagnostic tools are coming soon...Be s...

Cognos 8 Diagnostic: Cognos 8 Diagnostic tools are coming soon...

Be s...
: "Cognos 8 Diagnostic tools are coming soon... Be sure to visit: http://bicentre.blogspot.com/ http://bicentresdkguide.blogspot.com/ http:..."

An IBM message from John Doe

IBM

Dear Bi Centre,

IBM is sending this e-mail message to you at my request. I thought you would find the content referenced on the IBM web page below of interest:

IBM - Setting the CAM Passport from an ASP Page.

Note: The links within this e-mail message will expire in 90 days. Links to password-protected or dynamic content may not operate.

IBM is committed to protecting your privacy. You may view IBM's privacy policy at:

http://www.ibm.com/privacy/ca/en