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 |
|
12brich
Starting Member
5 Posts |
 Posted - 2002-10-09 : 01:13:00
|
| 1)During publisher's creation, I got the following:SQL Server could not create article 'MASTER_DIST' (name of my table) based on object 'MASTER_DIST'.Do you want to continue saving other changes to the publication?Error 21395: This column can not be included in a transactional publication because the column ID is greater than 255.The column was not added correctly to the article.2) SQL Server 2000 with SP1.3) At first I had 1 table with 270 columns and I got error 20068. I broke the table into 2 tables (240 and 31 with the right index of course so I can create a view later) and got a 21395. My problem I believe resides in the syscolumns table where the COLID values remain the same even after I deleted the columns in the first table. The COLID column appeared to be out of sequence. Going from say 1-110, it skipped 111-142 and continued again from 143-270. Can I use Enterprise Manager to put everything back to sequential order like 1-240? Would this corrupt the database? Thanks in advance.Please help! |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-10-09 : 09:13:16
|
| DO NOT MODIFY OR UPDATE SYSTEM TABLES, EVER!http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=12672How did you split up the tables into 2? Did you copy the original table and then drop the columns? It might work if you create the second table with only the columns it needs, then import the data into it. You may need to do this with both tables, come to think of it. It's worth trying first. |
 |
|
|
|
|
|
Replication Error 21395 Column ID >255