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(102.4, 45%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello, sorry if my question here is not clear on the concept...but is there a way via SQL Server script command to create a Linked Server which also specifies which Certificate to use that has been installed?
(Also to note if makes a difference the SQL Server instance here in reference is within SQL Server Clustered setup.)
Thanks in advance.
Additional SQL Server features and topics not covered by specific categories
I am not sure that I understand this. As far as I know, the client cannot select which certificate to use to for the communication with SQL Server. The instance has one single certificate that is used for communication. Whether the client is another SQL Server instance, SSMS or an application doesn't matter. There are no choices. Or am I missing something?
I agree with Erland, it seem we cannot specify which Certificate to use when create linked server. I also search this online but not luck, I could not find any helpful information.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Thanks for your replies both Erland and Cathy... sorry believe I'm a bit confused as well with the situation our end user is trying to accomplish.
End user is trying create a SQL Server "Linked Server" within their SQL Server clustered environment trying to connect into DB2.
End user here was provided a certificate from DB2 end but we seem to be confused how to get their SQL Server (Clustered environment) Linked Server to connect into DB2 end.
Sorry if this is not the best place to ask this question as it might be related more towards Windows Server? (just thought since involves creating SQL Server Linked Server I'd start here)
We did try importing the the Certificate via the Windows Server mmc console File -> Add/Remove Snap-ins... -> Certificates but we seem confused which options, locations, certificate file type (.cer, .pem, etc...) and any other steps related to the Issued certificate they received.
Any step by steps can point us related with our SQL Server Linked Server connection to DB2 certificate situation here perhaps?
Thanks in advance.
DB2? That's an interesting piece of information. If you only say "linked server" we are likely to assume that this is a linked server to another SQL Server instance, since this is the most common scenario.
Now, I don't know anything about DB2, but it may very well be the same thing as with SQL Server when you want an encrypted connection and you don't want to trust the server certificate so that you don't expose yourself to a man-in-the-middle attack.
If there is a way to configure the certificate when you set up the linked server? Maybe. That is, this depends on the OLE DB provider. The normal procedure is that the certificate is located in the folder Trusted Certificates in the certificate store of the computer. But it could be that the OLE DB provider has a connection-string option to specify a file location of the provider. Such an option was recently introduced for the MSOLEDBSQL19 provider. If such an option is available, you would define in the @provstr argument to sp_addlinkedserver.