Hi,
I want to move COGNOS_CONTENT_STORE and COGNOS_AUDIT to another SQL Server (new instance not default one). I want to do the steps as:
1. Backup the databases.
2. Restore databases on new SQL Server.
3. Delete Content Store in IBM Cognos Configuration
4. Recreate new resource as Database to connect to COGNOS_CONTENT_STORE on new server with proper credentials (same for COGNOS_AUDIT) .
Is this the right way to do it, or I need to check something else? What type of authentication should I use to connect to databases, SQL Server or Windows?
Thanks.
One addition (implied but worth stating): make sure you stop all Cognos processes first.
It's similar to the process I've used in the past. As part of this, I'd recommend taking an export from Cognos Configuration (clear text dump of all config information) in case you need to rebuild the configuration information.
You might be able to get by with just changing the connection information on the connections in Cognos Configuration, rather than deleting the connection reference.
If you want to ensure you are seeing the correct database, you can "take offline" the databases on the old SQL Server.
I've seen better results using a SQL Server account for connections in Cognos Configuration.
Thanks for your specifications. I will stop the service before and take the databases OFF on the old server. For the moment we are using Windows authentication to connect to SQL Server but I will change for an SQL user. I will make a full configuration Export or even better a full backup of the Cognos Application Server. I am not able to change the connection in Cognos Configuration, so I'm afraid that I need to delete it an re-create it.
Full configuration export or full backup:
The full configuration export is for you to read in case you need it (it's plain text). Full backup is a great idea but won't help if you only have to retype info in Cognos Configuration.
Thanks for your explanation. For full backup I wanted to say that I'll make a machine (physical server) backup (all OS and application) so in case of something goes wrong I can restore my server image.
If you've already set up your content store for windows access then I suggest you leave it that way. Then everything runs under the Cognos service account and you don't have all of these additional SQL logons floating around.