Hi,
We are using sql server 2005 as content store in cognos 8.4 . I successfully backup the content store from sql 2000 to sql server 2005. In cognos 8.4 configuration -> content manager -> content db1 (type: Microsoft SQL server database(windows authentication), it connects to db. I see nothing in cognos connection. Can anyone help if you have experienced with this issue. Thank you for your help.
Is this new database being restored with the same user as used to connect to in Cognos configuration? If not, these tables might have been restored in a different çatalog hence not showing up. Did you also change the Cognos 8 security by any Chance?
The database is restored with same user account as cognos configuration. I can see the tables in sql server. When I connect to SQL Server 2005 (MS Sql server management studio) the authentication mode is windows authentication. I am not sure why it is not showing anything in the cognos connection.
Hi,
Right click on content store and test it once you changed the DB info.if its succeeded then save your configuration and restart the cognos services.
hope this will hep.
SSNCOG
If I right click and test, the connection is successfull.
The fact that you see nothing in Cognos connection can mean 2 things: 1. You don't have permission in Cognos connection. That could occur if you changed authentication.
2. The content store tables were recreated under a new schema and are hence empty.
Hi,
Could you please explain 'The content store tables were recreated under a new schema and are hence empty'?
I took a backup of content store db from cognos 8.2 server and restored it into new server which has cognos 8.4 installed. I logged in with full admin rights into Ms Sql server management(sql server 2005) with windows authentication and restored the database.
In cognos configuration -> content manager added new database -MS sql server db(windows authentication) and test was successful.
In sql server management studio, I see all the tables restored.
Thanks.
never mind ... I was to caught up with oracle too much at that time. If the DB test successfully then the schema will not be a problem. Point one from my previous post could still be valid though :
Check that the namespaces (entries under Authentication) in cognos configuration are exactly the same (especially name and ID) between 8.2 and 8.4. If these aren't the same secured content will not be visible anymore. Changing the Namespace ID means that users logging in 8.4 will no longer be recognised as the same user.