How to Fix Inconsistent Metadata Errors

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by James Travis » How to Fix Inconsistent Metadata Errors

21 posts, Page 1 of 3

1 2 3 »»»

How to Fix Inconsistent Metadata Errors

Rate Topic

Display Mode

Topic Options

Author

Message

Antares686

Posted Sunday, February 24, 2002 12:00 AM

SSCrazy Eights

Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357, Visits: 684

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/jtravis/changingcolumn.asp

Post #2745

darren.green

Posted Monday, February 25, 2002 11:48 AM

Valued Member

Group: General Forum Members
Last Login: Friday, May 05, 2006 1:47 PM
Points: 69, Visits: 1

Is this not covered by this fix-

FIX: Error Message 7355 "..Inconsistent metadata for a column" Occurs When You Use a Linked Server (Q306401)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306401

Darren Green
SQLDTS.com | SQLIS.com | Konesans Ltd

Post #28712

Antares686

Posted Monday, February 25, 2002 7:58 PM

SSCrazy Eights

Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357, Visits: 684

Actually no, the server I tested from was (RC, SP1, SP2) on 2000 and (RC, SP1, SP2, SP3) with SQL 7. The problem actually steams form the column order stored in the syscolumns table and not the string lenght compared to the index which was directly related to SQL 2000 and not 7.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Post #28713

Argyle

Posted Thursday, June 06, 2002 9:08 AM

Grasshopper

Group: General Forum Members
Last Login: Wednesday, December 17, 2003 12:00 AM
Points: 16, Visits: 1

This is so unbelievably on target. I had this exact same problem and MS had no fix for it. THX!!!

Post #28714

Antares686

Posted Thursday, June 06, 2002 2:25 PM

SSCrazy Eights

Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357, Visits: 684

Thank you, and as for an update, when I was doing SP4 beta it looked like the had casually fixed it there with no mention which is not unusual. However, I have not had a chance to verify with the final release code but will in the next week or so.

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Post #28715

rithomas

Posted Tuesday, September 10, 2002 2:49 PM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, September 10, 2002 12:00 AM
Points: 1, Visits: 1

If you're worried about changing system columns, a quick workaround to query a linked database would be to query against views instead of tables.

Post #28716

thotakura

Posted Tuesday, October 08, 2002 9:09 PM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, June 16, 2010 1:23 PM
Points: 1, Visits: 3

I ran the script given by James Travis to fix the column
order . It did fix the column order, but the data in the
table got messed up as the colid and colorder columns are updated in
the syscolumns table.

Can anybody explain the reason why the data gets messed up
as the colid and colorder are updated.

Any help is appreciated and can email to sridhar_t @hotmail.com

Thanks

Sridhar

Post #28717

Antares686

Posted Wednesday, October 09, 2002 3:35 AM

SSCrazy Eights

Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357, Visits: 684

I am not sure why you had this occur. I tested on several machines to insure that I was messing with the proper fields and had no issues with it in any situation I could come up with. What is visually happening to your data and can you post your table structure as I am curious specifically where this becomes an issue to try and improve it. Also, I hope you made a backup of your data beforehand as I would hate to think you lost anything but I did state I make no guarantees as there is always the unknown factor to think about. If you did you may want to restore and try updating the server to SP4 and see if this fixes (please do on a test server to test), when doing the beta it seemed it has a hushed fix of this problem which probably showed other related situations as well. Also was the version an English version server?

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

Post #28718

fastorro

Posted Tuesday, February 11, 2003 3:17 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 23, 2005 12:40 AM
Points: 174, Visits: 1

NOOOOOOOOOOOOOOOOOOOO!!!

my data base has been corrupt due to this solution, This solution DOES NOT WORK with SQL server 7 SP3

Post #28719

Antares686

Posted Tuesday, February 11, 2003 4:35 AM

SSCrazy Eights

Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357, Visits: 684

I do hope you made a backup.

I did check I still have not had issues so I am wondering what specifically is under the hood that causes this. Can you post your DDL so I can have a look under SQL at what it is doing?

As seems to not cause further issues in SP4 I did not test any SP4 machines. I will have the code pulled so no one else can potentially even try this.

Post #28720

« Prev Topic | Next Topic »

21 posts, Page 1 of 3

1 2 3 »»»

Permissions