Link to home
Create AccountLog in
Avatar of forcedexposure
forcedexposure

asked on

how do we upgrade our Ruby on Rails custom app so that it work with a newer version of SQL server?

We've got a database-driven Ruby on Rails application that quit running after we upgraded our database from MS SQL 2012 to MS SQL 2017. What's the fastest way to get this application back up and running?


We are seeing the following in the application log file:


railties (4.1.5) lib/rails/rack/logger.rb:20:in `block in call'

  activesupport (4.1.5) lib/active_support/tagged_logging.rb:68:in `block in tagged'

  activesupport (4.1.5) lib/active_support/tagged_logging.rb:26:in `tagged'

  activesupport (4.1.5) lib/active_support/tagged_logging.rb:68:in `tagged'

  railties (4.1.5) lib/rails/rack/logger.rb:20:in `call'

  actionpack (4.1.5) lib/action_dispatch/middleware/request_id.rb:21:in `I, [2023-04-04T08:21:27.081934 #1041]  INFO -- : Started HEAD "/" for 127.0.0.1 at 2023-04-04 08:21:27 -0400

F, [2023-04-04T08:21:28.447249 #1041] FATAL -- : 

NotImplementedError (Currently, only 2005, 2008, 2010, 2011, and 2012 are supported. We got back Microsoft SQL Server 2017 (RTM-CU27) (KB5006944) - 14.0.3421.10 (X64) 

   Oct 14 2021 00:47:52 

   Copyright (C) 2017 Microsoft Corporation

ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account