With proper indexing and defragmentation, 200 mil rows shouldn't be an issue. I've had tables with 2 billion+ rows that were still usable.

Also, inserting data shouldn't take any longer than...

There is definitely nothing wrong with the code...it works fine on my end without a GO in between.

This might sound silly, but are you sure you're executing this in the...

It sounds like you're looking for the Stuff() function.

What is your downtime window?

Can you just take the system down, run a full backup, copy it, and restore it on the new server? If you have the time available,...

Some good points posted already, but I just wanted to add one more

Sometimes it's a good idea to drop all indexes (except the one you're sorting on of course), delete,...

Yeah, sounds like the OS is running out of resources. I would leave 8gb for the OS on a 96gb box. Remember that SQL allocated ram is just for the...

Who makes the decision on which organizations are the same? Is there a set of rules anywhere, or are you just basing it on a similar name set? Basically, how...

Weekly data refreshes? If you do backup/restore, that also means anything being developed/tested will be wiped out....typically I only do data refreshes after a major release when there's a code...

Sorry for the wording there..was in the middle of a few things. I meant a Synonym, not an alias.

CREATE SYNONYM [dbo].[LicenseTable] FOR [LicenseDB].[dbo].[LicenseTable]

I don't know what your table names are...

Except that entire thing is defeated by:

declare @a as varchar(max)

set @a = convert(varchar(max),@obfoo)

print @a

I noticed it's throwing the error every 5 minutes or so.

Is there a job scheduled to run every 5 mins that is connecting to a linked server/etc? Log shipping/replication check...

Can you please post the table definitions, which criteria is going to potentially be passed, and some sample data? Also a quick mock-up of expected results would help us to...

Sounds like just a quick network blip. It only has to be down for a few seconds while the backup job looks for that directory to throw an error.

Have you...

Create a new database on each server just for the license key table, and then create an alias in your main database for the license table to point to the...

You could add some auditing to it, and save the output to a text file so you can read where the error occurs.

Add a few PRINT 'starting step x' lines...