This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(281.6, 85%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGL%3C/text%3E%3C/svg%3E)
Import-module sqlserver -MinimumVersion 22.2.0
$ConfigInfo = Import-CSV 'C:\ConfigStuffToImportOnSQLServer.txt'
Write-SqlTableData -ServerInstance myinstance -DatabaseName 'master' -SchemaName 'dbo' -TableName 'GoodStuff' -Force -ConnectionTimeout 0 -Timeout 0 -InputData $ConfigInfo -TrustServerCertificate
This command mostly works but out of 200 SQL Servers it fails on 10 of them:
Write-SqlTableData : A parameter cannot be found that matches parameter name 'TrustServerCertificate'.
Additionally Invoke-SqlCmd runs fine against the same instances that fail the above command while using TrustServerCertificate.
The Bug (or I think it is one) is with the version 22.2.0 sqlserver module and Write-SqlTableData.
![](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(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
A bug, perhaps, but if your code works 95% of the time I don't think it's more than an incorrect error message.
If it always fails on the same set of servers, I think you should check that the certificates on those machines haven't expired, have an incorrect host name, or some other problem.
I don't have a SQL server to do any more than offer what I've just said, though. One of the SQL SMEs might offer better advice. :-)
The issue is obviously with Write-SqlTableData, not the SQL Server version. I would check that you really have version 22 on the machines where this fails. I see on https://learn.microsoft.com/en-us/powershell/module/sqlserver/write-sqltabledata?view=sqlserver-ps that -TrustServerCerticate is new in V22.
The Bug (or I think it is one) is with the version 22.2.0 sqlserver module and Write-SqlTableData.
For this bug issue, you can post it in the feedback site.
I was instructed to log it as an issue on the modules GitHub page which I did. Today it ran in the customers environment without throwing an error. Nothing changed, unless they changed something which I am researching. If it no longer persists or I get info from what changed on the SQL Servers in question, I will share back here. Thanks.
out of 200 SQL Servers it fails on 10 of them:
Have all 200 SQL Server the same version or do the 10 have a different one?
Sorry, you provided so less informations, it's difficult to guess.
Thanks for the reply. I posted this on sqlserver module GitHub and will be reviewed for a bug. The 200 instances range from SQL 2005 to SQL 2022. The errors happen on 2016, 2017 and 2019. They also are successful on those versions too. Its either an unknown setting on those instances thats causing the issue or a bug in Write-SqlTableData