EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB248854: “Server Definition manipulations error: (Database error <>: Execute Query failed…Incorrect syntax near ‘@ERRNO’.)” after moving a metadata from older SQL Server versions to newer ones directly


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical note documents an issue that occurs after moving a metadata from older SQL Server versions to newer ones directly

SYMPTOM:
After moving a metadata from an older SQL Server version to another newer one, such as from SQL Server 2008 to SQL Server 2014, the following error message appears after configuring the Intelligence Server to this new metadata:
 

ka04W000001Iqw8QAC_0EM440000002C5I.jpeg


Server Definition manipulations error: (Database error <>: Execute Query failed. 
Error type: Odbc error. Odbc operation attempted: SQLExecDirect.
[42000:102: on SQLHANDLE] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '@ERRNO'.)

 
CAUSE:
This issue occurs when users manually move the metadata from one SQL Server version to another. This method is not supported by Strategy because each version of SQL Server (and each different database) has its own syntax and structure requirements. When Strategy creates the metadata tables, the tables are created using the specific syntax for that database and its version. In SQL Server 2008 and below, one of the triggers uses @ERRNO syntax to ensure metadata integrity. This is no longer valid in SQL Server 2012 and above, hence the error message described occurs. The only way for this syntax to be put into SQL Server 2012 and up is for a direct database migration.
 
ACTION:
The proper way to move the metadata is to duplicate the project(s) through Project Duplication into an empty metadata shell created in the appropriate version. When creating the empty metadata shell, Strategy generates the metadata tables with the proper syntax, structure and preset system values for that database platform and version.
For information on Project Duplication, refer to KB12330 .
For steps on migrating projects from one database to another, refer to KB44209 .


Comment

0 comments

Details

Knowledge Article

Published:

May 24, 2017

Last Updated:

May 24, 2017