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 |
|
parrot_person
Starting Member
1 Post |
 Posted - 2005-02-15 : 09:55:19
|
| I am importing tables from Sybase 11 to SQL Server 2000. I am having a problem in that all identity columns ending in 0 on Sybase BECOME 0 when transferred to SQL Server. It's quite obvious what the primary keys need to be changed to (when you see a series like 1 2 3 4 5 6 7 8 9 0 11 12 13 14 15 16 17 18 19 0), but this problem afflicts the foreign keys as well, and it is impossible to tell what records *should* be referenced.I have tried importing the data into a flat file, same problem. I had fixed a date issue previously by importing that column in as varchar initially, but transforming the identity columns to varchar when importing doesn't fix this problem. I have tried Googling about this issue and find no information. Ditto asking coworkers if they've ever encountered this before. I have never used Sybase before but have frequently used SQL Server. If I knew Sybase better, perhaps I'd try going on on that side and transforming the data... when I look at the data in Sybase, using SQL Advantage, there appear to be no problems with the data in the identity columns.Anyone have any clue what is going on?? |
|
|
|
|
|
Sybase -> SQL Server identity column issue