problem with reading link information in Sql server image field

Question

problem with reading link information in Sql server image field

Glenn Laanekorb

SSC Veteran

Points: 254
More actions
December 13, 2005 at 6:16 pm

#166814

I am working on an SQL database and the database was transferred over to another database, and now some of the information that is saved as \\server\folder\ is not in human readable form.
Is it possible to get this back into some sort of readable form? the information that is saved there is the link to the file, which appears in hex format it looks like when just viewing the table.
I have tried
select convert(varchar(100),convert(binary(100),textcol)) as test
from databasetable
this converts it, though as some I suspect got corrupted, it shows up similar to *%*$)# and can't read it.
Is it possible to convert this information into readable form?

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Glenn Laanekorb SSC Veteran Points: 254 More actions · Answer 1

I have determined that it isn't actually corrupt just cannot be read in SQL Server.

How do I check the contents of the image field, to determine what the link is and resolve the problem so the information is again displayed as normal text and not gobbly gook?

Paul Randal One Orange Chip Points: 29544 More actions · Answer 2

So was the data perfectly readable in the source database? Using what mechanism?

How did you copy it?

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

Glenn Laanekorb SSC Veteran Points: 254 More actions · Answer 3

As far as I can ascertain yes it was readable before the transfer to the new SQL database, otherwise I wouldn't be here attempting to solve it. The maximiser program copied all of the data to the new database automatically as far as I know.

We are going to have a look at the customers database Monday as we have determined only a few entries in the database have different data when just viewing the database.

used the code:

select convert(varchar,convert(varbinary(100),textcol)) as test

from amgr_letters_tbl

Glenn

Paul Randal One Orange Chip Points: 29544 More actions · Answer 4

ok - so if the table schemas are exactly the same and the data is still readable in the source database then the problem occured during the copy process or the destination database is corrupt.

Have you checked that there isn't a char/widechar mismatch between the source/destination databases?

Have you run CHECKDB on the destination database?

I know nothing of the 'maximiser' program - how does it do the copy?

Thanks

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005