November 23, 2007 at 4:15 am
Hello!
I'm trying to restore a database from a backup, but I always get this warning message:
Restore was succesfully done, but I want to repair those tables described in warnings.
So I started to search what this issue could be, but I can't find the solution.
But I noticed that I have old and unwanted Subscriptions here:
I tried to remove them, but I can't remove them in the Enterprise Manager, because I don't have valid Publications there. I also can't drop them with T-SQL stored procedure sp_dropsubscription, which is described in MS Article 324401 http://support.microsoft.com/kb/324401
When I disable Publishing and distribution in Enterprise manager, I get the message that all publications on this MSSQL Server will be dropped, but this doesn't happen.
When I tried to make a new Publication, I always get this error:
I realized that this column is in the database named 'distribution' in the table MSpublications. So I don't have a clue what's wrong with it.
I'm really confused and I don't have no idea how can I repair that.
Could anyone help me?
November 27, 2007 at 10:20 pm
These are warnings. The maximum row size is 8160, but you can actually create a row that has a potential maximum size that's larger. You cannot insert more than 8160 bytes in the row, however.
Also, please post in the appropriate version forum.
November 27, 2007 at 11:45 pm
Steve Jones - Editor (11/27/2007)
These are warnings. The maximum row size is 8160, but you can actually create a row that has a potential maximum size that's larger. You cannot insert more than 8160 bytes in the row, however.Also, please post in the appropriate version forum.
Hello, Steve!
Thank you for moving my post to the appropriate forum! I overlooked that mistake 🙁
Well, I know that those are just warnings. I want to reduce the row size, but I can't find tables described in the warning description. Do you know in which database they could be and how can I find them?
Thank you for your help in advance!
November 28, 2007 at 7:40 am
You can check sysccolumns for the one that appeared.
For the others, you could write query that would add up all the lengths in syscolumns, grouped by table, with a sum < 8100 and that would find them.
Sorry, the errors aren't necessarily that descriptive. I might report this in the BOL o the web for this error.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply