October 2, 2002 at 4:40 pm
When I tried replicating a table which has more than 255 columns. SQL Server came back with:
Error 20068: The article cannot be created because it has more than 255 columns.
What is the work around. Please help!
October 2, 2002 at 7:02 pm
Split the table in to two or more, replicate separately, create a view so you can work with it as one (if you must!).
Andy
October 2, 2002 at 8:13 pm
The software application (C++) that logs data to the database was written by another group. Splitting the table will definitely impact their code. SQL Server doc. shows that a table can have up to 1024 columns. Is this a bug?
October 3, 2002 at 5:12 am
Not one that they plan to fix I think. Merge replication has some other limitations, limiting the table size to around 6k characters.
If you rename your current table, split it into as many 255 col chunks as needed, then create a view, you should be able to present something to the app that looks like one table while you replicate them separately.
Andy
October 3, 2002 at 9:48 am
What are the limitations a view has that a table doesn't? I know that it does perform a join between tables so you can treat as one. Can I really treat a view as a true table without worries? How is it exposed to external applications using ODBC?
October 3, 2002 at 1:12 pm
I've used them in Access via a DSN quite a bit, only issue I've seen there is that Access doesnt look at the underlying tables and so doesnt know what the primary key is - you have to configure it. Easy enough to throw together a sample of 2-3 tables, make a view, see what you think.
Andy
October 4, 2002 at 9:42 am
Is there an perfomance issue with respect to read and write to the view from an external app? It seems that every time you write to the view, SQL Server has to turn around and make sure the tables are updated. Is the additional overhead significant? Thanks.
October 4, 2002 at 11:57 am
Havent tested. Has to be some overhead, though I suspect its not a lot.
Andy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply