Not really.

Only stuff not available from BOL.

Ask Jeff about this.

It will be the same SPID, because it's gonna be connected to the server via the same connection.

And dynamic SQL called from there will have the same @@SPID despite all...

And you don't need loop for this.

Replace whole WHILE thing with this:

SELECT @Message = ISNULL(@Message + ',', '') + Z.REP+':'+ Z.INFO

FROM (

SELECT LEFT(SLPRSNID,2) AS REP,INFO

FROM @Stage

WHERE SLPRSNID =@MinRep

) Z

ORDER BY...

SELECT @Message = ISNULL(@Message + ',', '') + @Concat

Does it deserve anything cooler?

If there are no leading spaces then there is no need for LTRIM. RTRIM is useless by definition. As well as ISNULL.

You doin't need LEFT because LIKE will take 1st...

You can easily make a UDF with 3 parameters from it and use it in your scripts instead of standard DATEADD:

SET @DatePart = 'yyyy' SET @AddedParts = 2 SET @AddedDate...

Antares686, this tells about presentation mainly, again.

I tell you, read math references. Read about precision behind the scene.

After you've discovered the truth i'd probably thankful to MS for implicitly...

It's probably the time for you to refresh memory about normalisation rules, especially the 1st one.

But if you'll remove leading spaces from "Comment" when you save it you could use...

Antares686, please take any reference book on math and read about precision in math operations.

Then you'll realise that result of calculations from FLOAT ALWAYS more precise than result...

Is it your case?

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=367848

The difference comes from the fact that hardcoded values let optimiser estimate number of index entries to participate in the range and, because the number is quite small, use non-clustered...

From BOL:

Recompiling Execution Plans

Certain changes in a database can cause an execution plan to be either inefficient or invalid, given the new state of the database. SQL Server detects the...

Very valuable suggestion.

The only problem is that statement

Insert into [newtable] select * from [oldtable]

will lock [oldtable] for the entire insertion period.

If you apply (NOLOCK) or do it in groups you...

Check out BOL for sp_spaceused.