I found this while researching a blog article; very interesting - I always thought code was put in place to prevent this sort of thing from happening. Only seems to work on SQL Server 2005 SP1. set language british set ansi_defaults off set ansi_nulls...