Re: Urgent: Deciphering binary code executed against the database

(anojjona@[EMAIL PROTECTED]
) writes:
> Now another thing, for those who are interested...the idea posted
> before that one could use the same logic to reverse the damage
> apparently won't work.  That's because it uses the convert() command
> to convert the data to varchar.  That does two things:  It allows the
> script to work on text fields (somehow varchar fails when used in
> dynamic SQL within an exec statement); 

You cannot do string concatenation with the text and ntext data types,
so that is probably why they do the convert-varchar thing.

> By the way, does anyone know if the 30 character thing is standard, or
> if it's configurable per installation?
 
In SQL Server when you say varchar/binary/etc and do not specify a length,
the length defaults to 1. Except in convert where it defaults to 30. That 
is not configurable.

-- 
Erland Sommarskog, SQL Server MVP, esquel@[EMAIL PROTECTED]
 Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx