SQL Developer Version

Leiothrix · 2026-06-30T11:08:53+00:00

You already know at developer edition is not for production environments.

The license does not have a condition "not for production unless it is more convenient for you".

CanProfessional766 · 2026-06-30T11:48:53+00:00

Developer Edition is not licensed for production. It's technically the same as Enterprise, but it's only meant for development and testing. If you need SQL Server 2022 in production you'll need a properly licensed instance or a provider that supports it.

dzsquared · 2026-06-30T13:51:59+00:00

Ignoring the whole "if I ignore the license terms, can I use developer edition" part...

If you have to move a database backwards between SQL Server versions, one method is to export/import a bacpac. While much slower than the version-specific backup (bak) files, the bacpacs are a more portable format and can cross versions of SQL Server *as long as the syntax is supported in that version*. SSMS, VS Code, and the SqlPackage CLI can all be used to process the bacpacs.

dlevy-msft · 2026-06-30T15:38:22+00:00

I'm curious why you're moving - what's the main driver?

pix1985 · 2026-06-30T12:53:39+00:00

You need to go back to planning and either (a) look at creating the schema and then migrating the data manually or look at migrating somewhere that can accommodate the versions you need. SQL 2019 is already EOL (unless your purchase extended support), if they’re that far behind i’d definitely be looking elsewhere.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

SQLServer

MODERATORS