3 ms·
IME if you didn’t use the DB -specific features, migration is painful, but not that much so. If you did use the DB specific features, you’re screwed regardles
by setr 5y ago
IME if you didn’t use the DB
-specific features, migration is painful, but not that much so.
If you did use the DB specific features, you’re screwed regardless of an ORM.
NB: I work for a DB migration firm, specializing in legacy->modern — where our usual customer has thousands of SP’s that have to be migrated and an ORM would have saved you maybe 5% of the effort; so my experience is biased towards that level of difficulty.
- sumtechguy 5y agoTSQL and PSQL ideas of a stored procedure are not really the same. If your SQL is mostly bound columns or some sort of ORM only then you can get lucky and just play the data type matching game. But most of the ones I have ever had to port was playing the 'rewrite these 300 stored procs again' game. They usually ended up in some sort of stored procedure for one of a few reasons 'they only knew how to do that', performance, that is what the senior guy wants.