Any news about that? Anyone found a solution?
We are having the same issue
I supposed it should work, since with other ORMs that works pretty fine

I manage to make it work but i'm not proud of myself, i just hope we have a solution soon

@AntonioBusillo
By the way, the 6 rows are not other actions related to the triggers?

@RMTTyszka would you mind sharing your workaround?

I'm facing the same problem. We mostly managed it by using a struct without the primary key defined, this stops gorm adding the OUTPUT clause. Of course this also stops gorm retrieving the inserted ID, so we have to perform a SELECT after the INSERT when we need the ID.

Has anyone better ideas?

Hi, I have the same issue :(
The workaround that I tested with my team is using a replace function to remove the OUTPUT, we know this is not the best approach but works

    sql := s.db.GetDb().ToSQL(func(tx *gorm.DB) *gorm.DB {
        return tx.Create(data)
    })
   // from the insert sql generated, delete the OUTPUT 
    sql = strings.Replace(sql, ^OUTPUT INSERTED\."(\w )", "", 1)
    tx := s.db.GetDb().Exec(sql)

See also here.
I proposed a workaround. Note that the issue is more related to the sql-server driver and not directly to gorm.