DI upgrade 11.7.3 to 12.2.2.3 results SQLBindParameter Error

dataservices sap-erp-bw
1

All,

We have recently upgraded from DI 11.7.3 to DS 12.2.2.3.

We have regenerated the ABAP code and posted in SAP. We now moved all the ABAP code from DEV to TEST. While testing I see the following error only on couple of tables in SD Rapid Mart… :hb:

ODBC data source error message for operation : <[Microsoft][ODBC SQL Server Driver]Optional feature not implemented>.

The rest all the code looks good and working fine… I looked at the forums for this error…but couldnt find anything specifically…

Did anyone come across the same…If so please help me out… !!!

Thank you for your time !!

Regards,
rrayanna

rrayanna (BOB member since 2010-07-12)

2

Hi Raghu,

Can you check below options?

  1. If the Job server has permission to access the SQL server tables.

  2. BODS services running on Local account or any Specific user?

Thanks
Kumar

itsvsk :india: (BOB member since 2011-05-04)

3

Is your Target DB a SQL Server ? If so in your Taget tables do you have DATE Columns? If you have one then change it to DATETIME

ganeshxp :us: (BOB member since 2008-07-17)

4

@itsvsk …Thank you for your prompt response…Below is the reply for your Q’s…

  1. If the Job server has permission to access the SQL server tables.
    Yes, it has permission to access the SQL server tables…

  2. BODS services running on Local account or any Specific user?
    They are running on Specific User, not the local account…

@Ganesh… Thank you, your solution worked…:smiley:
Changing the date columns to DATETIME worked…

Thanks a Bunch !!!

Regards,
rrayanna.

rrayanna (BOB member since 2010-07-12)

5

Did you understood why that fix worked?

Hope you do.

But for information, it is because upto SQL Server 2005 we don’t have DATE Datatype in SQL Server

ganeshxp :us: (BOB member since 2008-07-17)

6

Got that… Thank you, Ganesh…

rrayanna (BOB member since 2010-07-12)

7

Thank you!!

Edefius (BOB member since 2009-01-04)

8

Changing datatype from date to datetime, not really the solution I was thinking of. BUT, it worked and I am very happy about that.

Thanks!

Bikern (BOB member since 2011-01-10)

9

where did you change the datatype ? in database or in DS ?
I think you might not be using the correct driver of database type in DataStore

what is the Database type and version of the database that you are using in the datastore ? SQL server 2005 or 2008 ?
if it’s SQL Server 2008, then use the database type in Datastore as SQL Server and version as 2008 (you may have to create a new configuration in case of upgrade)
Install SQL Server 2008 Client on the Job server machine

if you need to store DATE then I don’t think you should be changing the datatype to DATETIME

manoj_d (BOB member since 2009-01-02)

10

Hi manoj_d,

So you mean that I should use datatype “date” none the less of the issue.

I am using Sql Management Studio 2008r2. But instead of using Sql Server 2008 as database in datastore I am currently using an ODBC-connection. Maybe not the best solution but at the moment how it works.

I have actually not seen any problems yet with using “datetime” as datatype. But I will definitely keep an eye on it.

Thx,

Bikern (BOB member since 2011-01-10)