The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @locuta: Wereldwijd nu 2,5 miljard prikken gezet. Op een wereldbevolking van bijna 8 miljard (we zitten al op 7,8…..!) is dat vermoedeli… 2 hours ago
    • RT @SidFudd: Rarely has an award been more deserved. Millions of editorial cartoonists daily devote quite a very big large amount of time o… 2 hours ago
    • RT @overlistener: 1/ Uit ervaring weet ik dat sommige mannen je als vrouw zullen seksualiseren zelfs als je bijna volledig bedekt bent. Is… 2 hours ago
    • @iRepeltje Gefeliciteerd jullie! 3 hours ago
    • RT @030Caro: Kijk. Uiteindelijk zijn die Belgen toch De Slimste. 😆 3 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,388 other followers

In SQL Server use `SET NOCOUNT ON` so tools taking the last modified record count won’t be confused by your trigger.

Posted by jpluimers on 2020/04/07

Interesting read: Time eating bug of the day… – Fabian S. Biehn – Google+.

TL;DR: in SQL Server use SET NOCOUNT ON so tools taking the last modified record count won’t be confused by your trigger.

Source: [WayBackTime eating bug of the day: I used a TADOQuery.ExecSQL (on Berlin) for an Up…

Related: [WayBack] sql server – ADODB affected rows return trigger’s affected rows – Stack Overflow


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: