I prefer "implicit transaction", they are more safe than "begin tran" in case you use "GO" in the script.

SET IMPLICIT_TRANSACTIONS ON
;with a
as
(
SELECT * FROM dbo.account WHERE account_code='4c'
)update...

Inside dynamic sql I prefer to use the /**/ comment to avoid bug in concatenation.

Well Done.

GO

CREATE procedure spt

as

SELECT C.CustomerID

FROM

(

SELECT

sh.CustomerID,

OrderDate = MAX(sh.OrderDate)

FROM dbo.SalesHeader AS sh

GROUP BY sh.CustomerID

) AS C

INNER JOIN C AS c2

ON C.CustomerID = c2.CustomerID;

GO

This is a demonstration that the error is at execution time...

Here it stats https://docs.microsoft.com/it-it/sql/t-sql/statements/alter-database-transact-sql?view=sql-server-ver15, too.

It's impossibile because of division by 0.000 (with 3 decimal).

I got it wrong, I thought you want the name of the month %B.

You also can create synonym without an existing object.

In your example you mismatched the synonym StagingSongs with SongStaging

CREATE SYNONYM SongStaging FOR #songs
GO
CREATE PROCEDURE dbo.LoadSongs
AS
INSERT Songs
(
songid,
title,
releasedate,
genre
)
SELECT songid,
title,
releasedate,
genre
FROM dbo.StagingSongs
WHERE...

The second dot is a "virtual AS".

Absolutely NO, but if you like to think so OK.

This clearly shows that if the expression before the dot is data type numeric,

then the expression after the dot is taken as a column name.

The dot is part of constant...

That's true! It's the decimal separator.

The explanation is that constant numbers are evaluated as one token! It doesn't matter if there is not a space at the end of the constant

These queries are equivalent:

This reply was modified 6 years ago by Carlo Romagnano.