May 10, 2018 at 12:33 pm
Hi,
company want to migrate 3-rd party database application (let's name it "financial_db 3-rd party ") from SQL 2012 to SQL 2017 and possibly to Azure.
officially "financial_db 3-rd party " supported by SQL 2012 I think they simply did not bother to test it on 2012+
"financial_db 3-rd party " can be used with different RDBMS as
Oracle, Informix, Sybase, MySQL, Microsoft SQL Server versions up to 2012, PostgreSQL, SQLite
Without setting testing application server connected to DB restored on SQL 2017 and trying to open all application windows and running application batches I need to identify if database will work with 2017
Since application can use different RDBMS as back end I will safely exclude server objects like triggers ,calls to shell
If Restore database on SQL 2017 what is best ways to scan syscomments for code not supported by SQL 2017 ?
Thank you
Alex
May 10, 2018 at 2:10 pm
this is quite old, but you can try that , hope it helps , if you decide to go ahead from 2012 to 2017 be ready, you might be declined support from 3rd party.
May 10, 2018 at 3:03 pm
goher2000 - Thursday, May 10, 2018 2:10 PMthis is quite old, but you can try that , hope it helps , if you decide to go ahead from 2012 to 2017 be ready, you might be declined support from 3rd party.
Thank you!
I found similar article
http://jasonbrimhall.info/2016/11/07/finding-deprecated-uses-in-sql-server/
started filtering out in "where"
like
AND [feature] NOT LIKE '%Returning results from trigger%'
because event file filling out quickly on repeatable events
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply