This will be more complex than just what you've shown, if this is trying to strip prefixes/suffixes off a name, as it appears to be.

For example, the letters "JR" and...

Yeah, I can't think of a really clean way to do it now either, other than brute force:

SELECT table_name.*, derived2.row_num

FROM table_name

INNER JOIN (

SELECT colb,ROW_NUMBER() OVER(ORDER BY...

If you typically query by datetime, cluster the table by datetime first. No need to use kludges just to keep load_id as the lead key column.

A User table, a Group table and a GroupUser -- or UserGroup -- table.

User ( User_Id, ...other_user_columns... )

Group ( Group_Id, ...other_group_columns... )

GroupUser ( Group_Id, User_Id, ...other_columns_related_only_to_the_COMBINATION_of_Group_and_User only]...

Typically the ROW_NUMBER() method will outperform other methods. It also guarantees only a single result row, which means that duplicate values will be ignored (I believe you can use...

Or maybe this?:

SELECT

t.ProductID

,t.Order_Day

,t.Order_Quantity

FROM (

SELECT

ProductID

,Order_Day

,Order_Quantity

,ROW_NUMBER() OVER(PARTITION BY ProductID ORDER BY...

Yes, but you could have a start-up proc that recreates the table. Or just test for its existence and create it if it's not there.

For a particular table, you can add a trigger to the table to capture the relevant details from any UPDATE statements.

One of the tasks will acquire the lock first, and then the other one will have to wait. SQL's locking mechanism is what it allows it to "sequence" these...

Worst case, create the table in tempdb. Btw, yes, you can create a permanent (non-temporary) table in tempdb.

You need a separate table, clustered on the matching value, if you want best performance, or even good performance in the main table that is being compared has lots of...

Lol, kind of as an exercise I did do a recursive function for this task. As you said, I'm not sure about how it will perform, and I have...

Try sp_helptext, as in:

EXEC master.sys.sp_helptext 'sys.server_principals'

The best-practice recommendation is to grant only the specific permissions needed, in this case, I think that would be:

GRANT SELECT ON SCHEMA::dbo TO [<user_name>];

GRANT CONTROL ON SCHEMA::rpt TO [<user_name>];

Yep. Just add the schema to the table and add the other column to the WHERE:

...

FROM dbo.Orders

WHERE STATUS IN (1, 2, 3) AND Type IN (3, 4)