SQL Dialect Translation Notes Between Two Databases
Translate a query and list the differences to test.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Translate this query from one SQL dialect to another. Source database and version: [SOURCE_DATABASE]. Target database and version: [TARGET_DATABASE]. Query: [QUERY]. Produce the translated query and a table of every change with the reason, ordered by risk with silent differences first: integer division (an integer in one system, a decimal in another), case-insensitive comparison, handling of empty strings and NULL, then date and time functions, string functions, quoting of identifiers, limit and top syntax, boolean types, auto-increment, case sensitivity and collation. Mark each translation to verify [VERIFY]. Give five test queries that expose these differences, each with an expected result for both systems that I should confirm by running them, plus comparisons of row counts, totals and a sample of rows on the same data. Add a date and time zone checklist, a note on identifiers and reserved words, features with no direct equivalent and a workaround, and for a bigger migration a spreadsheet inventory (query, owner, features used, status, tested by). Be honest about what you cannot be sure of without running the query.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.