AnsweredAssumed Answered

Deprecated features of MS SQL 2008 used in NIKU SPs

Question asked by clarity2689 on Apr 3, 2013
Latest reply on Apr 3, 2013 by clarity2689
HI All

We have recently upgrade from 12.0.6 to v13.1 . We did a fresh installation on MS SQL 2008 server and moved the MS SQL2 005 dump on th new instance.
Before the upgrade We had a question raised by the DBA team that some of the Extended Procedures that exist in the Database MS SQL server 2005 ,obsolete features of these SP will be removed in future versions of MS SQL as per the below link from Microsoft.

http://msdn.microsoft.com/en-in/library/ms175200(v=sql.105).aspx


Now when the DBA team analysied the Niku DB after completion of the Clarity Upgrade. Team found that even after the Upgrade the deprecated features of SQL 2008 persists in the DB. This clearly indicates that these deprecated features are not handled by Clarity Upgrade Script and should be handled manually, if at all.

We just want to confirm whether these objects are used as part of internal architecture of the Clarity tool, we’re not sure of changing these objects. We are not sure if the deprecated features will function incorrectly but ideally these features should not be used as per MSSQL 2008 documentation.

We just need a confirmation if these objects need to be changed or removed for v13.1 to work properly. And also want to know if this is really an issue to be taken care of.

Some of the SP using teh Deprecated features.
clb_validate_file_perms_sp sysobjects
CMN_CREATE_SEQ_TABLES_SP syscolumns
CMN_CUSTOM_OBJECT_DEL_SP sysobjects
cmn_dblocks_sp sysdatabases
CMN_DROP_COLUMN_SP syscolumns
CMN_DROP_DEFAULT_CONSTRAINT_SP syscolumns
CMN_DROP_INDEX_SP sysindexes
CMN_ENABLE_DISABLE_SP sysobjects
CMN_ID_CREATE_CURRVAL_SP sysobjects
CMN_ID_SP syscolumns
CMN_MIGRATE_MSSQL_INDEXES_SP syscolumns
CMN_RENAME_COLUMN_SP syscolumns


Thanks
Pavithra

Outcomes