WHERE t_stamp >= (CAST(DATEDIFF(SECOND, '19691231 20:00:00', GETDATE()) AS bigint) * 1000) - (1000 * 60 * 30)

ARPRINCE,

Have you looked at the query plans for the two queries?  The LEFT JOIN method is doing a full table scan per join.  That could be a (big) performance issue,...

SELECT 
    ID,
    MAX(CASE WHEN Referrence = 'OrderNo' THEN Value END) AS OrderNo,
    MAX(CASE WHEN Referrence = 'OrderDate'...

Here's the "standard" cross-tab method:

SELECT 
    ID,
    MAX(CASE WHEN Referrence LIKE 'ON%' THEN Referrence END) AS OrderNo,
    MAX(CASE...

The use of the prefixed "TBL_" is a design error so bad it has a name; it's called the tibble.

This is not a design error.  It does not violate...

I use

;WITH

just to help prevent possible errors.  Sure, I could be technically correct and blame someone else when there was a problem with the code, but I prefer to avoid...

I would not prefix a view with tbl.  In any case I rarely use views in an OLTP environment.  I do make extensive use of them in...

I would not prefix a view with tbl.  In any case I rarely use views in an OLTP environment.  I do make extensive use of them in my OLAP...

I believe that SQL renames temp tables rather than dropping them, esp. for stored procs.  That way, when the proc runs again, it doesn't have to fully recreate...

I believe that SQL renames temp tables rather than dropping them, esp. for stored procs.  That way, when the proc runs again, it doesn't have to fully recreate the table...

>> The professorID is likely both the natural ID for the professor and the identity of the row. <<

The professor_id is probably a tax identification number of some kind....

Once again, unusable data.  We need CREATE TABLE and INSERT statement(s), not a picture/"splat" of data on a screen.

So go ahead and do it.  Not sure specifically how a tally table is going to help here.  Besides, a tight loop should likely perform well enough on a string...

I think this code follows all the restrictions for natively compiled procs:

declare @byte tinyint;
declare @bad_chars char(33);
declare @new_string varchar(255);
declare @string varchar(255);
declare @string_len tinyint;
declare @string_replacement_char char(1);

set @bad_chars = '['...

I agree that you should only store attributes as numeric types if you plan on doing math on them, but if you are using only surrogate keys as you...