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 |
|
clarkbaker1964
Constraint Violating Yak Guru
428 Posts |
 Posted - 2005-08-12 : 13:20:55
|
Hey...I have a problem with data in a varchar fieldWhen an application tries to read the records from my tableon of the fields has corrupt data.I have run DBCC to repair the table but theunicode (oxB) (ascii characer (11) - vertical tab)still exists in the fieldI am concerned I may have more fields on other rows with this condition.Help appreciated. You can do anything at www.zombo.com |
|
|
clarkbaker1964
Constraint Violating Yak Guru
428 Posts |
Posted - 2005-08-12 : 13:35:27
|
| select 'select ' + c.name + ' from sf_contact where ' + c.name + ' like char(11)', * from sysobjects o inner join syscolumns c on o.id = c.id where o.name = 'sf_contact' and c.xtype =167Thank you for letting me post it felt good hopes this help othersYou can do anything at www.zombo.com |
 |
|
|
ryanston
Microsoft SQL Server Product Team
89 Posts |
Posted - 2005-08-12 : 14:13:03
|
| This is actually a condition that DBCC CHECKDB would not detect. For the most part, we are unaware of the contents of user data. There's not anyway for us to verify the semantics of your data, so we restrict ourselves to verifying the structural consistency of the database and its contents.On a similar note, though, we have added a new set of column-level checks in SQL Server 2005 CHECKDB that will detect "data purity" errors in structured column data for types like (SMALL)DATETIME, NUMERIC, FLOAT/REAL, etc. Thanks,----------------------Ryan StonecipherDeveloper, Microsoft SQL Server Storage Engine, DBCC(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
Corrupt field data