ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    SQL Server 2019

    IT Discussion
    wrcombs sql sql server 2012
    5
    8
    857
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • WrCombsW
      WrCombs
      last edited by

      Anyone using this ? 2012 goes to end of life this year
      https://docs.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012

      just trying to see if there are any problems with 2019

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @WrCombs
        last edited by

        @WrCombs Yup, been using it for years now. Every SQL Server instance that we manage has been updated since.... 2019 or so 😉

        No issues at all. And I think we've been 100% on Linux, too. We always deploy SQL Server to Linux, even in otherwise WIndows environments because we want to treat it like production.

        WrCombsW 1 Reply Last reply Reply Quote 0
        • WrCombsW
          WrCombs @scottalanmiller
          last edited by

          @scottalanmiller said in SQL Server 2019:

          @WrCombs Yup, been using it for years now. Every SQL Server instance that we manage has been updated since.... 2019 or so 😉

          I figured that was the case, lol just wanted to double check.

          No issues at all. And I think we've been 100% on Linux, too. We always deploy SQL Server to Linux, even in otherwise WIndows environments because we want to treat it like production.

          Thanks - I'm looking to move a private client to this. anything I need to keep in mind?

          JaredBuschJ scottalanmillerS 1 3 Replies Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @WrCombs
            last edited by

            @WrCombs said in SQL Server 2019:

            @scottalanmiller said in SQL Server 2019:
            Thanks - I'm looking to move a private client to this. anything I need to keep in mind?

            SQL Server is SQL Server. Nothing has really changed with it in years other than the ability to now install it on Linux.

            scottalanmillerS 1 Reply Last reply Reply Quote 1
            • scottalanmillerS
              scottalanmiller @JaredBusch
              last edited by

              @JaredBusch said in SQL Server 2019:

              @WrCombs said in SQL Server 2019:

              @scottalanmiller said in SQL Server 2019:
              Thanks - I'm looking to move a private client to this. anything I need to keep in mind?

              SQL Server is SQL Server. Nothing has really changed with it in years other than the ability to now install it on Linux.

              Exactly, from a software perspective, it's all SQL Server. Your "users", meaning the apps that connect to SQL Server have no way to know what platform it is running on. Just like if you are running LIbreOffice... you can't tell from the app what it is running on underneath.

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @WrCombs
                last edited by

                @WrCombs said in SQL Server 2019:

                Thanks - I'm looking to move a private client to this. anything I need to keep in mind?

                Nope, super straightforward. Much easier than Windows, even.

                1 Reply Last reply Reply Quote 0
                • 1
                  1337 @WrCombs
                  last edited by 1337

                  @WrCombs said in SQL Server 2019:

                  Thanks - I'm looking to move a private client to this. anything I need to keep in mind?

                  SQL server can run a database in compatibility mode and does so by default when you migrate from something older. 2012 however supports older version than 2019 does so it's possible to run into problems.

                  There is also some breaking changes between versions as well as functionality that has been discontinued. Only advanced SQL applications are likely to run into any of these though. But it's really the job of the application developers to make sure the app is compatible with newer SQL versions.

                  I suggest a test run before upgrading production workloads. Or just have the ability to roll back until full functionality has been verified. In most cases there will not be any problems whatsoever.

                  1 Reply Last reply Reply Quote 1
                  • ITivan80I
                    ITivan80
                    last edited by

                    Yeah i know a former customer using SQL 2012 and he has since left. I have not tried SQL 2019 yet, i wish that i can work with that software.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post