I wish to improve the performance of a stored procedure by using an 'insert into' a table with a 'unique index' along with the 'with ignore_dup_key' option instead of using a select distinct. Problem is I distributed a client side application that craps out when the stored procedure returns the informational message 3604. I can only think of one way to stop the message and that would be to remove that SQL Error message. I don't even know if that will work. Anybody got any server side workaround for the handling of this informational message?