Recently I noticed some abysmal performance from a select query against the HISTORY table and was finally able to track it down to an SLX Trigger.... There's an SlxLoggingTrigger.dll against the history table that generates a query like this

(@P1 nchar(26))SELECT HISTORYID,TYPE,ACCOUNTID,ACCOUNTNAME,CONTACTNAME,DESCRIPTION,COMPLETEDDATE,RESULT,COMPLETEDUSER FROM HISTORY WITH (NOLOCK) where HISTORYID = @P1

Which is really bad because HISTORYID is a char(12) .... So this query has to do an implciit conversion from nchar to char....

Is this a bug that's been fixed? Is there a hotfix? or is it safe to just disable these triggers? If so how do I go about doing that?

You can disable them using UPDATE SLXTRIGGERS SET ENABLED = 'F' WHERE PATH='SlxLoggingTrigger.dll' - you can also do the same for SpeedSearch if you're not using that (be sure also to truncate INDEXUPDATES).