2017-01-30 (first published: 2017-01-26)
18,892 reads
2017-01-30 (first published: 2017-01-26)
18,892 reads
Have you ever wanted to run a query across every database on a server with the convenience of a stored procedure? If so, Microsoft provided a stored procedure to do so. It’s unreliable, outdated, and somewhat obfuscated, though. Let’s improve on it!
2016-04-15 (first published: 2014-12-01)
16,839 reads
2010-09-08 (first published: 2010-09-02)
2,344 reads
2008-08-06 (first published: 2008-06-16)
2,639 reads
By Daniel Janik
The circle cylinder of life Maybe you’ve noticed all the twenty somethings tight rolling...
By Chris Yates
In today’s data-driven economy, organizations are no longer asking if they should invest in...
By Rohit Garg
PostgreSQL, often referred to as Postgres, is a powerful, open-source object-relational database system that...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Good Morning All, We are facing replication latency issue. I checked for blocking, long...
Comments posted to this topic are about the item Life's Little Frustrations
I have this table in SQL Server 2022:
CREATE TABLE CustomerLarge (CustomerID INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED , CustomerName VARCHAR(20) , CustomerContactFirstName VARCHAR(40) , CustomerContactLastName VARCHAR(40) , Address VARCHAR(20) , Address2 VARCHAR(20) , City VARCHAR(20) , CountryCode CHAR(3) , Postal VARCHAR(20) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers