199 questions
The only issue I can think of are character-set issues. If you stick to UTF-8 consistently, you should be fine.
Potential Issues with Deploying to SQL Server 2016 Using sqlcmd from Linux in GitHub Pipeline
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 50%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJA%3C/text%3E%3C/svg%3E)
James, Ashwin (BC Pension)
0
Reputation points
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 SQL Server Transact-SQL
2 answers
Sort by: Most helpful
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator2025-03-08T07:59:55.44+00:00 -
LiHongMSFT-4306 31,566 Reputation points2025-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".