Feedback
Did this article resolve your question/issue?

   

Article

Incorrect timestamp scale and precision error using the SQL Server Wire Protocol driver

Information

 
TitleIncorrect timestamp scale and precision error using the SQL Server Wire Protocol driver
URL NameIncorrect-timestamp-scale-and-precision-error-using-the-SQL-Server-Wire-Protocol-driver
Article Number000185174
EnvironmentProduct: Connect64 for ODBC SQL Server Wire Protocol driver.
Version: 7.10.05.232
OS: Windows Server 2012
Database: SQL Server 2012
Application: Informatica PowerCenter
Question/Problem Description
Incorrect timestamp scale and precision error using the SQL Server Wire Protocol driver
Steps to Reproduce
Clarifying Information
Error Message[DataDirect][ODBC SQL Server Wire Protocol driver]Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 999 and scale of 9. Error in parameter 1.
Defect Number
Enhancement Number
Cause
WorkArounds2=2 was being set in a different ODBC DSN than the one being used in the application.
Resolution
Setting WorkArounds2=2 in the ODBC DSN being used in the application resolved the error.
Workaround
Notes
References to other documentation:
Connect/Connect64 for ODBC Reference : "WorkAround Options"
https://www.progress.com/documentation/datadirect-connectors
Last Modified Date5/19/2016 11:17 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.