runtype | Utilities for run-time type validation and multiple dispatch | Validation library

I would like to make the token parameter required ONLY when the runType parameter is set to download. I believe something like this can be done with dynamicparam, but I'm stuggling to find out how it works. As you can see, I have a basic Write-Error to catch the missing value, but perhaps can anyone give an example/how-to for use of something smart with dynamicparam?

I'm new to databricks so hope my question is not too off. I'm trying to run the following sql pushdown query in databricks notebook to get data from an on-premise sql server using following python code:

Here is a demo code snippet(https://godbolt.org/z/31Tq3r):

I am trying to create a a Linked Server in SQL (SQL 2016) to an access database (2013). I do not want to do anything in access - just simply query a table from SQL Studio Management. I have tried to create an ODBC connection - but I only have the option of 32bit - not 64. But if I create a 32bit (Microsoft Access Driver (*.mdb) and then create a linked server using Microsoft OLE DB Provider for ODBC Driver - Data source I am using the System DSN name I get this message:

The linked server has been created but failed a connection test. Do you want to keep the linked server?

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Program Location:

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry) at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(String cmd, Boolean retry) at Microsoft.SqlServer.Management.Smo.LinkedServer.TestConnection() at Microsoft.SqlServer.Management.SqlManagerUI.LinkedServerProperties.DoPreProcessExecution(RunType runType, ExecutionMode& executionResult)

I do have a few other linked servers - but to Oracle DB's. Am I missing something?

I am trying to extend class with overloaded method so I can instantiate it and pass different number of argument but keep common type of Foo and Bar. How can I make my code runnable?

I have the following ComboBox:

I am one of those developers that struggle with thinking in terms of sets. At least I know it. :-)

I have been asked to look into the matter of transactional emails being sent out to users. I am not the original programmer of the functionality, and I think the original programmers have left the company as well. Sigh...

Currently, some of the emails are being sent directly out of SQL, but not with Database Mail. So, I am in the process of looking into using Database Mail (sp_send_dbmail). I'll probably do a complete overhaul of how things work, hopefully using Database Mail, but in the meantime, I am wondering whether there is a simpler (temporary way) of improving performance by tinkering with the current SQL code.

In a stored procedure, a cursor is used to call another stored procedure, which makes an API call to a Controller class, which with a few more calls to other methods eventually sends the email. These C# methods are not implemented asynchronously. I'm busy changing those methods to async too. Not surprisingly, the SQL server is half-dead when these emails are being sent out.

So I'm wondering:

1. Whether there is an alternative set-based way instead of using a cursor in this case?
2. Like I said, I'm going to change the C# methods to async in any case (since other parts of the system use it) but off the cuff, would it make a noticeable change in performance? My fairly ignorant opinion would be that the main trouble lies more with the cursor.

Here is the stored procedure with the cursor, sp_Interface_PayslipEmails:

Anybody can able to explain me what is the difference between those two versions of declaring status property? I know that in some why the second version not loose type safety, but how does it work?

I'm developing a mobile app using nativescript + angular and I'm testing it using Appium. When I run appium end to end tests the the following command it loads a previous build of my application.