OCS Database Servers

[eferreyra]

Hi, we currently have our OCS server instance (7.0) using a SQL Server 2000 database back-end for the calling list stuff.
And maybe other components of the platform uses it, historic reports, statistics, i dont know...

We are close to not have any more support of SQL Server 2000, having to migrate to 2005 or 2008 (or other?)

Its is possible for OCS to change the back-end to SQL Server 2005 or 2008 (or other) ?

How hard is it ?

Thanks!
Pachu

[René]

Hi Pachu,

It's definitely possible. I would suggest you upgrade to version MS SQL Server 2005 because the version 2008 is still in testing phase so it isn't supported for production use either by Microsoft or Genesys.

Of course, you can migrate to Oracle but it's more related to your IT department strategy, available resources, compatibility of existing non-Genesys tools etc. than to Genesys itself.

Migration to MSSQL 2005 - It's necessary to do some compatibility test before going to production but it should be sufficient to upgrade Genesys DBServers to version 7.5 only. Maybe it will be good to open a ticket and ask Genesys what they "think" about support of OCS 7.0 with DBServer 7.5. Just for sure

René

[eferreyra]

Thanks renee!

We dont have the skills for migrate by ourselves the Genesys DBServer yet, but i need to know this alternative so when the time comes we open a ticket for the full implementation of DBServer 7.5 and SQL 2005.

Cheers.
Pachu

[bcyk]

Genesys Outbound Contact Solution comes with a list of databases, depending on site specific implementation. Common databases are configuration db, LOG db, ODS db, Dart Mart db and OCS db.

Couple migration tasks to migrate MS SQL 2000 to MS SQL 2000 (yes! changing hardware servers only) were performed. A point should be reminded was migration of usernames and access rights. Below MS SQL command might be required.

use my_db;
go
sp_change_users_login AUTO_FIX, 'my_user'
go

--------------------------------
Migration from MS SQL 2000 to MS SQL 2005 was never performed in production environment. Development testing was tried.

Most Genesys components requiring DB access works fine for MS SQL 2005; problem begins when running Reporting modules; Data Sourcer and ETL sevice. Error message could be found in relevant debug log in which it suggested using sp_dbcmptlevel in MS SQL 2005 server.

sp_dbcmptlevel [ [ @dbname = ] name ] [ , [ @new_cmptlevel = ] version ]

version:
60 = SQL Server 6.0
65 = SQL Server 6.5
70 = SQL Server 7.0
80 = SQL Server 2000
90 = SQL Server 2005

You need Database administrator support to change below settings

EXEC sp_dbcmptlevel 'gctiCONF', '80';
GO
EXEC sp_dbcmptlevel 'gctiLOG', '80';
GO
EXEC sp_dbcmptlevel 'gctiODS', '80';
GO
EXEC sp_dbcmptlevel 'gctiDM', '80';
GO
EXEC sp_dbcmptlevel 'gctiOCS', '80';
GO
## and, all other databases as well!
## use below command to list database size, owner,..., compatibility level
sp_helpdb

This approach can be the minimum effect without upgrading any Genesys component. Please consult your local Genesys Support and have confirmation before any migration to production environment!


It is interesting to know as well what are impacts when upgrading to Geneyss 7.5. For instance, is it possible to migrate and keep current report databases (ODS and DM).

It's wondered Geneys DB server 7.5 is NOT the only components for MS SQL 2005! ETL Service is a set of Java programs that do not access Genesys DB server; they access database tables directly. It may imply that Genesys 7.5 Reporting solution/module are mandatory required. Again, confirmation from your local Genesys Support is recommended.


regards