Replication triggers are causing the rowcount to be greater than one and therefore causing NHibernate to throw an exception.

I've searched this forum to ascertain whether NHibernate can in fact be used against a replicated database but I found any leads to be inconclusive. The advise given on posts discussing rowcounts has been to add "SET NOCOUNT ON" in the offending triggers. However, what abount triggers that get added by sql server itself?

Has anyone experience in what it takes to configure NHibernate and / or SQL server 2005 replication to get around the rowcount problem? I really have very limited experience in replication, so I'm not sure whether its even possible to manually change the replication trigger to add the necessary NOCOUNT statement.

Thanks
Christian

Yeah, this is a pain. The procs added by SQL server for replication can be edited by hand and you can add the NOCOUNT, but you'll have to be careful if you make future modifications to replication.

As far as I know that's the only solution open to you.

Symon.

Hmm, that is a pain. I've posted to sqlservercentral.com forums to see whether anyone else knows of a better way.

Thanks
Christian