Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ssharma
Starting Member
4 Posts |
 Posted - 2008-07-03 : 06:38:55
|
| Hi AllWe have our custom app running against the sql server 2000 and everything was fine. After the customer upgraded to sql server 2005 data cannot saved thru the app anymore. The converted data looks fine in the tables, but we get the above message in the logs. Any help would be greatly appreciated. |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-07-03 : 08:02:33
|
| Do you have bit fields in the table? If so, are they nullable and can they be set to be non-nullable? |
 |
|
|
ssharma
Starting Member
4 Posts |
Posted - 2008-07-03 : 08:15:27
|
| yes. They will have a value of either 0 or 1 |
|
|
|
ssharma
Starting Member
4 Posts |
Posted - 2008-07-03 : 08:31:30
|
| is there some setting in sql server 2005 which would allow all bit fields to be given a default value if none is found ? |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-07-03 : 08:57:28
|
| You have to set the default on the field itself. |
|
|
|
ssharma
Starting Member
4 Posts |
Posted - 2008-07-03 : 09:02:04
|
| but why does the insert sql break in sql server 2005 and not in sql server 2000. The data exported from Sql Server 2000 looks good when opened in sql server 2005 |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-07-03 : 09:13:21
|
| It is something to do with the drivers your application is using. Are you using the JDBC drivers? If so, look for more up to date versions. |
|
|
|
|
|
|
Parameter 10 (""): Data type 0x32 is unknown