It's possible within tsql to set up linked servers to submit queries to different db's.  However to switch between the linked servers you must use the word "go".  I'm pretty sure...

What query are you executing on the different servers?  When you get the list of servers do you only get a list of IP addresses or is there usename and...

tl;dr stands for "too long; didn't read" so your worries were well founded!  But seriously, what you posted worked and I'm very glad to have helped.  Readability is always a...

This is outside my area but my 2 pennies: Witness Client and Witness Server are used to keep the cluster in sync.  The error appears to have triggered a retry...

The specific issue of: Must declare the scalar variable "@output".  This is because when you specify the output variable(s) in the execute statement the target variable needs to be on the...

• This reply was modified 6 years, 2 months ago by Steve Collins.

Hey alright, now the code is tl;dr but it seems like you're on your way!

#3, you're correct.  The proc output variable(s) can be of any type.  However, the RETURN type...

One reason the first proc is not functional is because the temporary table is out of scope.  Where does #ssrsresults get created?  If a temp table only has 1 '#'...

Yep

declare...

This is done.  I couldn't find any satisfactory solution to placeholder replacement so the string formatting still happens in C#.  All of the text files and templates have been moved...

I think I see what you are saying about how many times the function could execute and the fact that I don't have a FROM clause.  Are you saying...

If you run it a million times.  In this case here the OP has no 'from' clause so it only executes once.  I actually did read your article a while...

If you're looking for something simple a scalar function could work.  The calculation requires no rows or columns.  If you know the function is accessed by query(s) in a proc...

Set operators work best when the tables are identical.  In this case there are different collations between tables.  Since "we're talking about thousands of columns across 100s of tables" it...

The procedure could be named whatever you wish.  "spFindExistingOrCreateNewProject" seems ok but a maybe little long...

If the goal is to tighten/shorten the code then here are a few suggestions:

1. Where...

Currently there are 2 procs:

Proc 1 ("spNewProject") does 3 things: 1) returns all project records if all inputs are nulls, 2) if necessary creates new project and returns new record,...