ZAP has multiple rules for detecting SQL injection vulnerabilities - search for "SQL" in the "alert" field on
https://www.zaproxy.org/docs/alerts/If any of the rules find a potential vulnerability then they will report it.
In this case it appears that it was the Oracle specific rule that found a potential problem, but that could be a False Positive.
If the MS SQL specific rule finds a potential problem then it will report the attack it uses.
They are independent rules, so there is no simple way to convert one attack to another.
Just run all of the rules, or use the Technology Flags to disable tests against dbs that you know are not in use.
Cheers,
Simon