I think what Jeffery was getting at was "who is the SQL Server Agent Service set to run as?".  I have a feeling it is NT Authority/System which doesn't have...

To answer your questions I would say "it depends".  For you, I would say do it all application side and just push the row across to SQL with a simple...

The logs are stored on disk along with the SQL instance in a folder called "Logs".  You will be looking for the file "ERRORLOG" (no file extension) and you can...

To me that sounds like it should be a good test set.  I would also try forcing the failover by having the VM go offline (reboot the VM and see...

Have you checked the SQL log?  That will likely tell you what is wrong.

Now, if memory serves, the MSVCP100.dll is the Microsoft Visual C redistributable, so if that got updated...

First question is easy.  SELECT <columns> FROM <table> WHERE <date column> = CAST('09.01.2021' AS DATE)

Second question is a bit more tricky as it depends.  This would likely be handled in...

Quick google brought me to Microsoft's website on that view and to quote them:

Returns counts of different types of index operations and the time each type of operation was last...

Possible? yes.  Would I do it? no.

The reason I wouldn't do it is you are going to have a whole bunch of tables that are named by the date.  Each...

I would reach out to the vendor of the BODS tool myself.  I expect that the tool has a timeout (possibly the default) for keeping the connection open to SQL. ...

I can't see any reason why it wouldn't work as long as @CurrentToken is defined.  I've run stored procedures inside an SSRS report.  I think it needs to return a...

I agree with Jeff here - find the problem queries and you will find the performance problems.  fix the problem queries and you will likely fix the performance problems.

The exception...

CTE's are not the only way to do it.  Nested selects would be another option, or you could do the calculation outside of SQL at the application layer, or you...

So, I think the problem you are having is that you are doing the update based on a VARIABLE not a COLUMN VALUE.  Change:

 UPDATE [dbo].[DTable] SET...

One thing to be cautious of that I didn't think of until today (just now) - AFTER getting the "final" string, you may want to check for a WHERE clause...

My goal was not to "stump" the interviewee, but to see if they had knowledge of SQL Joins and if they could do basic problem solving based on the words...