Potential Issues with Deploying to SQL Server 2016 Using sqlcmd from Linux in GitHub Pipeline

James, Ashwin (BC Pension) 0 Reputation points
2025-03-08T00:47:35.3733333+00:00

We are deploying to SQL Server 2016, where our developers use sqlcmd on Windows machines for development. However, our GitHub pipeline is using a Linux runner with sqlcmd on Linux for deployment. Could this setup cause any compatibility or operational issues during deployment?

SQL Server Transact-SQL
SQL Server Transact-SQL
SQL Server: A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.Transact-SQL: A Microsoft extension to the ANSI SQL language that includes procedural programming, local variables, and various support functions.
148 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 119.4K Reputation points MVP
    2025-03-08T07:59:55.44+00:00

    The only issue I can think of are character-set issues. If you stick to UTF-8 consistently, you should be fine.

    0 comments No comments

  2. LiHongMSFT-4306 31,081 Reputation points
    2025-03-10T02:27:11.3466667+00:00

    Hi @James, Ashwin (BC Pension)

    Regarding sqlcmd for Windows (ODBC): The default installation may be an older ODBC-based tool (such as Microsoft Command Line Utilities 15), which has a different parameter support range than the Linux version. For example: The Linux version of sqlcmd (Go) adds a strict encryption mode which may not be supported in older versions of Windows.

    Best regards,

    Cosmog


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.