Glad to hear it worked out - and yeah, rebuilding master requires recreating the logins and any other configuration settings.

I agree that not calculating the time differently for different rows seems weird. I'd hope that this would be updated when there is a significant insert time, such as...

When you said "If SQL Server 6.5 and 7 worked that way - then it was incorrect.", the only thing that was incorrect there was you thinking so.  You...

Gosh... I agree that it's been quite a while but it seems to me that SQL Server 6.5 and 7 worked just fine in this area and I've not...

Since an INSERT is a single transaction - SQL cannot use a datetime other than when that transaction started.  It doesn't matter how long the process actually takes - it must...

Thanks so much!  That's really helpful, I will try to rebuild those system DBs this weekend.

Also check @@servername - I am assuming you renamed the server to the same...

Review this document (https://docs.microsoft.com/en-us/sql/relational-databases/databases/rebuild-system-databases?view=sql-server-ver15)

Try using the process to rebuild the msdb database.  Before you do that, make sure you have scripted out every job so you can recreate them after...

The ascii function returns the ascii value of the character.  Capital A is ascii 65, but choose works with int values starting at 1, so we subtract 64 to get...

Are you processing the same files each day/week/month?  Or is every single file completely different from previous files processed?

If this is a process that repeats with a new file submission,...

Brian gave you a solution using either a case expression - or checking each parameter and condition.  Either will work - but may not work as well if there is...

I think the problem is going to be in the details that you have left out - but I do have some comments.

There is no reason to drop the database...

To fix the issue with not being able to edit scripts - you need to repair 'Microsoft Visual Studio Tools for Applications YYYY'.  This happens almost every time you apply...

Guarding against NULLs with WHERE NOT IN should be an ingrained habit.  There certainly are alternatives with JOIN or WHERE NOT EXISTS that may or may not be more...

Instead of converting to a stored procedure - I would recommend changing this multi-statement table valued function to an inline-table valued function.

It also looks like there could be some options...

You could use Activity Monitor to list all of the processes - but you could also use this code, which is basically the same code as used by Activity Monitor...