Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only
  • 1.  Can data modules use existing Data Source Connections?

    Posted 16 days ago

    We are a long-time Cognos shop with existing Data Sources (Administration Console -> Configuration -> Data Source Connections. We have an SDK that a server administrator runs that creates the Data Source Connections at setup and when the Sign on password changes/expires/disables. The Cognos development team is now looking to create some Data Modules that would be in the next release deployment package and we want to encourage the Cognos users to create Data Modules. But how to control the Sign on. Obviously, we are not giving the Cognos users the sign on credentials to the MS SQL Server. 

    Can Modules use existing Cognos Data Source connections? This would solve all problems as the Cognos users could just use an existing Data Source and our SDK would not have to be changed when passwords expire.  

    How are other people handling this. Is there something that I am missing? 



    ------------------------------
    brenda grossnickle
    BI Programmer Analyst
    FIS
    ------------------------------


  • 2.  RE: Can data modules use existing Data Source Connections?

    Posted 16 days ago

    Hi Brenda

    Assuming I understand your question - the short answer is yes data modules can connect to data servers (aka - data sources).  In order to make the data sources available to a data module - go into the Data Source connections (within Admin console) - click on the properties for the data source in question.  Click on the Connection tab, place a check on the "Allow web-based modeling" and save.

    If you do not have this "allow" option on that tab - this means that the data source you are attempting does not have a JDBC connection defined to the DB.  Add that connection and the "allow modeling" option will then show. 

    Whenever you add a "data server" to your environment - this is the same as adding a data source connection but without the OCI connection.  Data servers only use JDBC connections -- so that is why the automatically show up as a source within a data module. 

    Give that a try and hope this gets you moving in the right direction.  

    Feel free to text me if you have additional questions.



    ------------------------------
    John Cusack
    Analytica iQ
    3042818589
    ------------------------------



  • 3.  RE: Can data modules use existing Data Source Connections?

    Posted 16 days ago

    You will also need to load the schemas which you want to work with.

    Because of this, the metadata is available in a way which avoids unnecessary metadata call backs.



    ------------------------------
    IAN HENDERSON
    ------------------------------



  • 4.  RE: Can data modules use existing Data Source Connections?

    Posted 15 days ago

    I don't understand your reply. Can you explain?



    ------------------------------
    brenda grossnickle
    BI Programmer Analyst
    FIS
    ------------------------------



  • 5.  RE: Can data modules use existing Data Source Connections?

    Posted 15 days ago

    Once you make it available for web modeling, go to data servers and click on properties for the data source and under one of those tables you will see schemas...that will allow you to load the meta data for the tables you want to use in the data modules.

    Hope this helps. 



    ------------------------------
    John Cusack
    Analytica iQ
    3042818589
    ------------------------------



  • 6.  RE: Can data modules use existing Data Source Connections?

    Posted 15 days ago
    Edited by Abbas Alnamar 15 days ago
    Hello Brenda,
     
    I want to add this to IAN's note just a quick heads-up regarding working with Data Modules in IBM Cognos Analytics especially when you're loading schemas.
    When you load a schema, Cognos pulls in metadata from the data source (like tables, columns, and relationships), which can be quite resource-intensive. If the schema is large and your Cognos environment doesn't have enough memory or disk space, it can slow things down significantly or in some cases, even cause the environment to become unresponsive.
    1. Make sure the server has enough memory and disk space.
    2. Only bring in the tables and fields you really need.
    3. Consider doing schema loads during off-peak hours if possible.



    ------------------------------
    [Abbas] [Alnamar]
    [Data Management and Analytics System Administrator]
    [Emporia State University]
    [Kansas, USA]
    ------------------------------



  • 7.  RE: Can data modules use existing Data Source Connections?

    Posted 15 days ago

    "If the schema is large and your Cognos environment doesn't have enough memory or disk space, it can slow things down significantly or in some cases, even cause the environment to become unresponsive." and "3. Consider doing schema loads during off-peak hours if possible." are you talking about when creating the Data Server, creating the Data Module, and/or using a Data Module. 



    ------------------------------
    brenda grossnickle
    BI Programmer Analyst
    FIS
    ------------------------------



  • 8.  RE: Can data modules use existing Data Source Connections?

    Posted 15 days ago
    When I mentioned the potential performance impact of large schema loads, I was specifically referring to the process of creating or editing a Data Module particularly when you're loading metadata from a data server (like selecting tables, views, or schemas during setup).
     
    Creating a Data Server: This step usually doesn't cause performance issues on its own it's mostly about setting up the connection.
     
    Creating or editing a Data Module: This is where things can get heavy. When you load a large schema, Cognos pulls in a lot of metadata, which can consume memory and disk space.
     
    Using a Data Module (in reports or dashboards): This is generally lighter, unless the module itself is very large or poorly optimized.


    ------------------------------
    [Abbas] [Alnamar]
    [Data Management and Analytics System Administrator]
    [Emporia State University]
    [Kansas, USA]
    ------------------------------



  • 9.  RE: Can data modules use existing Data Source Connections?

    Posted 12 days ago
    I will need to try to set aside some time to finish my paper on loading metadata and its purpose.  
     
    The basic purpose of loading metadata is so that the query engine can consult and use the metadata rather than needing to make calls to the database to get the metadata.
     
    In FM, you import the metadata and use it as the basis of the query layer.  
     
    In a data module, the metadata is loaded into the content store and is thus available to all things which consume it.
     
    In addition, the metadata will have some enrichment, such as the taxonomy.   Also you can set data security filters on the loaded metadata so that all applications would have a common set of data security.
     
    When you set up a data source connection, one option you have available to you is called assets.  In there is a list of all the schemas of the db as defined by the connection information you provided.
     
    You have the ability to load the metadata.  If you don't, you will not be able to use that schema in a data module.  
     
    You can control which tables are loaded.  You can control the sampling size.  In some cases, sampling can cause problems.

    In the attached pictures, I have loaded 3 of the 79 tables of the GOSLDW sample database.  (the DBA has called it GV1022DW) Those tables are the only ones which are available to me if I try to import the metadata from the schema.  If I wanted more tables I would need to import more of them.  You will notice other schemas, such as GV1022HR, which are not loaded and thus not available to the modeller.
    Hope this helps.  
     
     






    ------------------------------
    IAN HENDERSON
    ------------------------------