Fix missing / misleading statements, and formatting for BACKUP CERTIFICATE#1976
Fix missing / misleading statements, and formatting for BACKUP CERTIFICATE#1976Jak-MS merged 1 commit intoMicrosoftDocs:livefrom
Conversation
1. Updated "Arguments" section to conform to most other pages:
1. Added "certname" argument.
2. Added argument name to each option.
3. Added "WITH PRIVATE KEY" argument as it mirrors `CREATE CERTIFICATE`.
4. Corrected default path description (tested in SQL Server 2017 CU14 and 2019 CTP 2.4).
5. Added LocalDB info to path description (tested in SQL Server Express LocalDB 2012 SP4).
2. Updated "Remarks" section:
1. Passwords are to protect private keys, not certificates.
2. Added info about private key file format.
3. Clarified that restoring a certificate does not require the private key.
4. Added info about restoring a private key to an existing certificate via `ALTER CERTIFICATE`.
3. Added links to CERTENCODED, CERTPRIVATEKEY, CERT_ID, and CERTPROPERTY functions in "See Also" section.
These updates are related to updates proposed for `CREATE CERTIFICATE` and `ALTER CERTIFICATE` via MicrosoftDocs#1972 , and to the following post: https://sqlquantumleap.com/2019/04/22/can-a-certificates-private-key-be-imported-restored-from-a-binary-literal-hex-bytes/
srutzky
changed the title
|
Test script showing that the following items are the same between
can be found at: https://pastebin.com/45gZKpuE What that test script does not directly show is the actual default location. That was determined to not be the DATA folder (as previously documented) simply due to me using custom folders for both user data files and user log files. When saving and restoring the private key and not specifying a path, the file was written to, and read from, the default user data directory (registry value is: |
srutzky
changed the title
|
Reviewed. Thanks again @srutzky! |
|
You're welcome 😺 |
5 participants
Updated "Arguments" section to conform to most other pages:
CREATE CERTIFICATE.Updated "Remarks" section:
ALTER CERTIFICATE.Added links to CERTENCODED, CERTPRIVATEKEY, CERT_ID, and CERTPROPERTY functions in "See Also" section.
These updates are related to updates proposed for
CREATE CERTIFICATEandALTER CERTIFICATEvia #1972 , and to the following post: https://sqlquantumleap.com/2019/04/22/can-a-certificates-private-key-be-imported-restored-from-a-binary-literal-hex-bytes/