If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

FM sql datasource restriction

Started by sdf, 05 Oct 2018 09:56:45 AM

Previous topic - Next topic

sdf

Hi,

First up, I would like to know if it is usual or just normal to see the masterdb or tempdb when I select an SQL datasource in Framework manager.

If it is, is there a way to hide them or restrict them?
If not, what could have we set to make masterdb and tempdb available/visible?
Lastly, would there be any impact when we hide them?



Thanks!

bdbits

By default, you see all databases on the instance you are connected to. You can restrict the list, but then you will never see them anywhere including SSMS (SQL Server Management Studio).

Why do you want to hide them? It is not really necessary, and could cause admin some headaches dealing with it.

sdf

Something I noticed,
When DQM is enabled/selected, I am able to see the masterdb.
When DQM is not selected, I am able to see only the database for that connection.
I'm sensing this has something to do with JDBC being used for DQM.

Security reason and I want to let the users to only see the database they need for FM.

cheers!

cognostechie

Quote from: bdbits on 05 Oct 2018 11:22:53 AM
By default, you see all databases on the instance you are connected to. You can restrict the list, but then you will never see them anywhere including SSMS (SQL Server Management Studio).

Not really, and SSMS cannot be restricted from within Cognos.

When you create a datasource in Cognos, you have the option to specify the database name along with the instance name and the server name. It will then show only that particular database and all schemas within that database as far as SQL Server is concerned.

cognostechie

Quote from: sdf on 05 Oct 2018 12:25:53 PM
Something I noticed,
When DQM is enabled/selected, I am able to see the masterdb.
When DQM is not selected, I am able to see only the database for that connection.
I'm sensing this has something to do with JDBC being used for DQM.

Security reason and I want to let the users to only see the database they need for FM.

cheers!

I don't have 10.2 available right now but I remember that it does allow specifying the database name. If that is not specified then it will show all databases within an instance of SQL Server. When a data source is created then there are two screens, one for CQM which does not involve JDBC and another for DQM which has another tab named 'JDBC' . It's possible that in that tab, the box for database name is not filled up.

sdf

First of, sorry for I have posted this on the wrong section. I actually am pertaining to a CA11 environment.

QuoteI don't have 10.2 available right now but I remember that it does allow specifying the database name. If that is not specified then it will show all databases within an instance of SQL Server. When a data source is created then there are two screens, one for CQM which does not involve JDBC and another for DQM which has another tab named 'JDBC' . It's possible that in that tab, the box for database name is not filled up.

I will be checking this behavior in Cognos 10. Regarding the database name for JDBC, I made sure that it is defined.
I was hoping that this is a usual behavior, but it seems not.