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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-06 : 08:58:36
|
| Ehsan writes "Dears, When I resotre a back up database from SQL 7.0, on 2000,the domains of sonme fields change, automatically and it causes exception in my application. for ex. "can not onvert int to varchar....". Please tell me this is the 2K version bug, or it is for another reason? And may be I had fault in DB design...?!?Thanx,Ehsan F.Technical managerSystem Group Co." |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-05-06 : 13:59:05
|
| I know this one too well. In 7.0 there was an implicit conversion allowed between char and int values. No more! We had to change our statements to convert them manually.ie. Select * from aTable where aCharacterfield > 19would work in 7.0. But fails in 2000. It had to be rewritten asSelect * form aTable where Cast(aCharacterfield as integer)>19You MIGHT be able to change the LEVEL of COMPATABILITY settings for the database under the OPTIONS tab of Enterprise Manager and get the Server to cooperate. I didn't try this, since I was trying to enforce strict 8.0 version compliance in our application. I understand there were several changes bewteen 7.0 and 2000 that affected things in this way. This is the only one that showed up in our application.Hope it helps. |
 |
|
|
|
|
|
About Field Domain