Converting to BIT error

We have a checkbox field check, (value='1') and it is deployed to a column with datatype BIT in MSSQL 2005. While deploying if we uncheck the checkbox, deployments goes through. But if the checkbox is selected deployment fails.

The error log states that failed to convert '1' to BIT.

So we changed the datatype in table to Varchar(3). Now while deploying if we uncheck the checkbox, deployments goes through as usual. But if the checkbox is selected deployment fails with the following log

DBD: Column: colname, field: dctq/0/check, Index: 3, Converting '1' to BIT

The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Paramater 13: Datatype 0x32 is unknown.

When we have changed the datatype in table from BIT to varchar why DataDeploy is still converting the field in DCT to BIT?

In deployment configuration xml we have datatype set to varchar.

Any pointers will be of great help.

thanks in advance

Find more posts tagged with

Comments

Adam Stoller

Did you drop the table?

praveen t n

Did you drop the table?

Thanks Ghoti, I didn't.

Though issue is resolved! I changed the field name and tried deploying, it went through. And in log it is now showing "converting '1' to Varchar(3)".

I have a question here - is there any kind of caching which DD does (which made it unable to identify the change in the datatype of the column mapped to a particular table) .

regards

Adam Stoller

Thanks Ghoti, I didn't.

Though issue is resolved! I changed the field name and tried deploying, it went through. And in log it is now showing "converting '1' to Varchar(3)".

I have a question here - is there any kind of caching which DD does (which made it unable to identify the change in the datatype of the column mapped to a particular table) .

regards

There are [at least] two things in play here:

column to the table with the new name, and that the old column (with the old name and data-type) is probably still there in the DB.Hence the question about dropping the table. If you had changed the DD config, dropped the table, then DD would have re-created it with the new data-type for that column.

praveen t n

[QUOTE=ghoti]There are [at least] two things in play here:

Adam Stoller

The datatype was changed to Varchar(3) in the DD config as well as in table. No new column got added to the table. Even after doing this, the deployments failed stating

DBD: Column: colname, field: dctq/0/check, Index: 3, Converting '1' to BIT
The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Paramater 13: Datatype 0x32 is unknown

Deployments went through for checkbox unchecked. Hence my question, why DataDeploy is still converting the field in DCT/DDconfig to BIT as indicated by Converting '1' to BIT ?

i.e. why DD didn't picked up the change in datatype?

You didn't previously indicate clearly that you had made the change in both locations - hence my previous posts.
Why it didn't pick up the change? No idea - I tend to find dealing with DD kind of a "black art" and try to stay away from it as much as possible.