Surprised this is the first time I have seen this question because I have always had this problem in SQL Server even from earlier releases. It was never fixed...

Just change the lines that read:

declare @DBName varchar (20) = PARSENAME (@TableName, 3)

to

declare @DBName varchar (20)

set @DBName = PARSENAME (@TableName, 3)

SQLServer 2005 just requires 2 rows instead of 1...

But surprisingly, not triggers.