We've got a strange problem here and I'm hoping someone has some kind of idea as to what could be causing it.<BR><BR>We've got a stored procedure in Sql Server 2005.