-->APPLIES TO: Azure Data Factory Azure Synapse Analytics (Preview)
2017-12-8 大坑!使用SecureRandom默认的加密方式即SHA1PRNG生成的密码有误,即使使用相同的password来生成,不同runtime或时刻生成的随机密码也有可能不同,造成的错误为javax.crypto.BadPaddingException: pad block corrupted。即key不同!!! 详细解释. 2016-10-2 bitwarden never sends unencrypted data to the server. All data is kept on the client machine and decrypted during runtime using the master password as the key. For the browser extension, all vault data is stored using the chrome.storage. I want to adjust the machine keys dynamically in code during runtime, for an IIS hosted ASP.NET MVC 4 website. The machine keys, encryption and validation keys as well as algorithms to use, are stored in a database.
The integration runtime (IR) is the compute infrastructure that Azure Data Factory uses to provideRegister a self-hosted integration runtime node with the specified authentication key.NoRegisterNewNode '
<AuthenticationKey>
' '<NodeName>
'Register a self-hosted integration runtime node with the specified authentication key and node name.NoEnableRemoteAccess '<port>
' ['<thumbprint>
']Enable remote access on the current node to set up a high-availability cluster. Or enable setting credentials directly against the self-hosted IR without going through Azure Data Factory. You do the latter by using the New-AzDataFactoryV2LinkedServiceEncryptedCredential cmdlet from a remote machine in the same network.NoEnableRemoteAccessInContainer '<port>
' ['<thumbprint>
']Enable remote access to the current node when the node runs in a container.NoDisableRemoteAccessDisable remote access to the current node. Remote access is needed for multinode setup. The New-AzDataFactoryV2LinkedServiceEncryptedCredential PowerShell cmdlet still works even when remote access is disabled. This behavior is true as long as the cmdlet is executed on the same machine as the self-hosted IR node.NoKey '<AuthenticationKey>
'Overwrite or update the previous authentication key. Be careful with this action. Your previous self-hosted IR node can go offline if the key is of a new integration runtime.NoGenerateBackupFile '<filePath>
' '<password>
'Generate a backup file for the current node. The backup file includes the node key and '<password>
'Restore the node from a backup file.NoRestartRestart the self-hosted integration runtime host service.NoStartStart the self-hosted integration runtime host service.NoStopStop the self-hosted integration runtime host service.NoStartUpgradeServiceStart the self-hosted integration runtime upgrade service.NoStopUpgradeServiceStop the self-hosted integration runtime upgrade service.NoTurnOnAutoUpdateTurn on the self-hosted integration runtime auto-update.NoTurnOffAutoUpdateTurn off the self-hosted integration runtime auto-update.NoSwitchServiceAccount '<domainuser>
' ['<password>
']Set DIAHostService to run as a new account. Use the empty password ' for system accounts and virtual accounts.NoCommand flow and data flow
When you move data between on-premises and the cloud, the activity uses a self-hosted integration runtime to transfer the data between an on-premises data source and the cloud.
Here is a high-level summary of the
When you open Integration Runtime Configuration Manager, you see a status of Disconnected or Connecting. When you view Windows event logs, under Event Viewer > Application and Services Logs > Microsoft Integration Runtime, you see error messages like this one:
Encodeuricomponent
Enable remote access from an intranet
If you use PowerShell to encrypt credentials from a networked machine other than where you installed the self-hosted integration runtime, you can enable the Remote Access from Intranet option. If you run PowerShell to encrypt credentials on the machine where you installed the self-hosted integration runtime, you can't enable Remote Access from Intranet.
Rsa Public Key Encryption
Enable Remote Access from Intranet before you add another node for high availability and scalability.
When you run the self-hosted integration runtime setup version 3.3 or later, by default the self-hosted integration runtime installer disables Remote Access from Intranet on the self-hosted integration runtime machine.
When you use a firewall from a partner or others, you can manually open port 8060 or the user-configured port. If you have a firewall problem while setting up the self-hosted integration runtime, use the following command to install the self-hosted integration runtime without configuring the firewall:
If you choose not to open port 8060 on the self-hosted integration runtime machine, use mechanisms other than the Setting Credentials application to configure data-store credentials. For example, you can use the New-AzDataFactoryV2LinkedServiceEncryptCredential PowerShell cmdlet.
Next steps
For step-by-step instructions, see Tutorial: Copy on-premises data to cloud.
-->SQL Server 2014 Integration Services (SSIS)SQL Server 2014 Integration Services (SSIS)包括 SSISDB 数据库。includes the SSISDB database.查询 SSISDB 数据库中的视图可以检查 SSISDB 目录中存储的对象、设置和操作数据。You query views in the SSISDB database to inspect objects, settings, and operational data that are stored in the SSISDB catalog.本主题说明如何备份和还原该数据库。This topic provides instructions for backing up and restoring the database.
SSISDB 目录存储部署到 ** 服务器的包**Integration ServicesIntegration Services。The SSISDB catalog stores the packages that you've deployed to the Integration ServicesIntegration Services server.有关该目录的详细信息,请参阅 SSIS 目录。For more information about the catalog, see SSIS Catalog.
备份 SSIS 数据库To Back up the SSIS Database
- 打开 SQL Server Management StudioSQL Server Management Studio 并连接到 SQL ServerSQL Server实例。Open SQL Server Management StudioSQL Server Management Studio and connect to an instance of SQL ServerSQL Server.
- 使用 BACKUP MASTER KEY Transact-SQL 语句备份 SSISDB 数据库的主密钥。Back up the master key for the SSISDB database, by using the BACKUP MASTER KEY Transact-SQL statement.该密钥存储在您指定的文件中。The key is stored in a file that you specify.使用密码加密该文件中的主密钥。Use a password to encrypt the master key in the file. Arma 2 free cd key generator.有关语句的详细信息,请参阅 BACKUP MASTER KEY (Transact-SQL)。For more information about the statement, see BACKUP MASTER KEY (Transact-SQL).在下面的示例中,将主密钥导出到
c:temp directoryRCTestInstKey
文件。In the following example, the master key is exported to thec:temp directoryRCTestInstKey
file.使用LS2Setup!
密码加密主密钥。TheLS2Setup!
password is used to encrypt the master key. - 在 中使用 “备份数据库” SQL Server Management StudioSQL Server Management Studio对话框备份 SSISDB 数据库。Back up the SSISDB database by using the Backup Database dialog box in SQL Server Management StudioSQL Server Management Studio.有关详细信息,请参阅 如何备份数据库 (SQL Server Management Studio)。For more information, see How to: Back Up a Database (SQL Server Management Studio).
- 通过执行以下操作,生成 ##MS_SSISServerCleanupJobLogin## 的 CREATE LOGIN 脚本。Generate the CREATE LOGIN script for ##MS_SSISServerCleanupJobLogin##, by doing the following.有关详细信息,请参阅 CREATE LOGIN (Transact-SQL)。For more information, see CREATE LOGIN (Transact-SQL).
- 在 SQL Server Management StudioSQL Server Management Studio的对象资源管理器中,展开 “安全性” 节点,然后展开 “登录名” 节点。In Object Explorer in SQL Server Management StudioSQL Server Management Studio, expand the Security node and then expand the Logins node.
- 右键单击 ##MS_SSISServerCleanupJobLogin##,然后依次单击“编写登录脚本为”“CREATE 到”“新查询编辑器窗口”。 > **** > ****Right-click ##MS_SSISServerCleanupJobLogin##, and then click Script Login as > CREATE To > New Query Editor Window. Openssl crt key to pem.
- 如果要将 SSISDB 数据库还原到从未创建 SSISDB 目录的 SQL ServerSQL Server 实例,请执行以下操作生成 sp_ssis_startup 的 CREATE PROCEDURE 脚本。If you will be restoring the SSISDB database to an SQL ServerSQL Server instance where the SSISDB catalog was never created, generate the CREATE PROCEDURE script for sp_ssis_startup, by doing the following.有关详细信息,请参阅 CREATE PROCEDURE (Transact-SQL)。For more information, see CREATE PROCEDURE (Transact-SQL).
- 在对象资源管理器中,展开 '数据库' 节点,然后展开 '系统数据库 > ' '主 > 可编程性 > ' '存储过程' 节点。In Object Explorer, expand the Databases node and then expand the System Databases > master > Programmability > Stored Procedures node.
- 右键单击 dbo.sp_ssis_startup,然后依次单击“编写存储过程脚本为”“CREATE 到”“新查询编辑器窗口”。 > **** > ****Right click dbo.sp_ssis_startup, and then click Script Stored Procedure as > CREATE To > New Query Editor Window.
- 确认 SQL Server 代理已启动Confirm that SQL Server Agent has been started
- 如果要将 SSISDB 数据库还原到从不创建 SSISDB 目录的 SQL ServerSQL Server 实例,请执行以下操作生成 SSIS 服务器维护作业的脚本。If you will be restoring the SSISDB database to an SQL ServerSQL Server instance where the SSISDB catalog was never created, generate a script for the SSIS Server Maintenance Job by doing the following.创建 SSISDB 目录时自动在 SQL ServerSQL Server 代理中创建该脚本。The script is created in SQL ServerSQL Server Agent automatically when the SSISDB catalog is created.该作业帮助清除保留期窗口之外的操作日志并删除较旧版本的项目。The job helps clean up cleanup operation logs outside the retention window and remove older versions of projects.
- 在对象资源管理器中,展开 “SQL Server 代理” 节点,然后展开 “作业” 节点。In Object Explorer, expand the SQL Server Agent node and then expand the Jobs node.
- 右键单击 'SSIS 服务器维护作业',然后单击 '创建到 > 新查询编辑器窗口的脚本作业 > '。Right click SSIS Server Maintenance Job, and then click Script Job as > CREATE To > New Query Editor Window.
还原 SSIS 数据库To Restore the SSIS Database
- 如果要将 SSISDB 数据库还原到从不创建 SSISDB 目录的 SQL ServerSQL Server 实例,请通过运行 sp_configure 存储过程来启用公共语言运行时 (clr)。If you are restoring the SSISDB database to an SQL ServerSQL Server instance where the SSISDB catalog was never created, enable common language runtime (clr) by running the sp_configure stored procedure.有关详细信息,请参阅 sp_configure (Transact-SQL) 和 clr enabled 选项。For more information, see sp_configure (Transact-SQL) and clr enabled Option.
- 如果要将 SSISDB 数据库还原到从不创建 SSISDB 目录的 SQL ServerSQL Server 实例,请创建非对称密钥和对应非对称密钥的登录名并将 UNSAFE 权限授予该登录名。If you are restoring the SSISDB database to an SQL ServerSQL Server instance where the SSISDB catalog was never created, create the asymmetric key and the login from the asymmetric key, and grant UNSAFE permission to the login.Integration ServicesIntegration ServicesCLR 存储过程要求将 UNSAFE 权限授予该登录名,因为该登录名需要对受限制资源(如 Microsoft Win32 API)的其他访问权限。CLR stored procedures require UNSAFE permissions to be granted to the login because the login requires additional access to restricted resources, such as the Microsoft Win32 API.有关 UNSAFE 代码权限的详细信息,请参阅 Creating an Assembly。For more information about the UNSAFE code permission, see Creating an Assembly.
- 在 中使用 “还原数据库” SQL Server Management StudioSQL Server Management Studio对话框从备份中还原 SSISDB 数据库。Restore the SSISDB database from the backup by using the Restore Database dialog box in SQL Server Management StudioSQL Server Management Studio.有关详细信息,请参阅以下主题。For more information, see the following topics.
- 执行你在备份 SSIS 数据库中为 ##MS_SSISServerCleanupJobLogin##、sp_ssis_startup 和 SSIS 服务器维护作业创建的脚本。Execute the scripts that you created in the To Back up the SSIS Database for ##MS_SSISServerCleanupJobLogin##, sp_ssis_startup, and SSIS Server Maintenance Job.确认 SQL Server 代理已启动。Confirm that SQL Server Agent has been started.
- Putty generating invalid rsa keys key. 运行以下语句以将 sp_ssis_startup 过程设置为自动执行。Run the following statement to set the sp_ssis_startup prodecure for autoexecution.有关详细信息,请参阅 sp_procoption (Transact-SQL)。For more information, see sp_procoption (Transact-SQL).
- 通过在 ** 中使用“登录属性”对话框,将 SSISDB 用户 ##MS_SSISServerCleanupJobUser##(SSISDB 数据库)映射到 ##MS_SSISServerCleanupJobLogin##。**SQL Server Management StudioSQL Server Management StudioMap the SSISDB user ##MS_SSISServerCleanupJobUser## (SSISDB database) to ##MS_SSISServerCleanupJobLogin##, by using the Login Properties dialog box in SQL Server Management StudioSQL Server Management Studio.
- 使用下列方法之一还原主密钥。Restore the master key by using one of the following methods.有关加密的详细信息,请参阅 Encryption Hierarchy。For more information about encryption, see Encryption Hierarchy.
- 方法1Method 1如果已备份数据库主密钥且具有用于加密主密钥的密码,则使用此方法。Use this method if you've already performed a backup of the database master key, and you have the password used to encrypt the master key.备注确认 SQL ServerSQL Server 服务帐户有权读取备份密钥文件。Confirm that the SQL ServerSQL Server service account has permissions to read the backup key file.备注如果服务主密钥尚未加密数据库主密钥,将看到 SQL Server Management StudioSQL Server Management Studio 中显示的以下警告消息。You will see the following warning message displayed in SQL Server Management StudioSQL Server Management Studio if the database master key has not yet been encrypted by the service master key.忽略警告消息。Ignore the warning message.当前主密钥无法解密。已忽略此错误,因为指定了 FORCE 选项。The current master key cannot be decrypted. The error was ignored because the FORCE option was specified.FORCE 参数指定即使当前数据库主密钥未打开,也应继续执行还原过程。The FORCE argument specifies that the restore process should continue even if the current database master key is not open.对于 SSISDB 目录,由于在您正在其中还原数据库的实例上未打开数据库主密钥,您将看到此消息。For the SSISDB catalog, because the database master key has not been opened on the instance where you are restoring the database, you will see this message.
- 方法2Method 2如果您具有用于创建 SSISDB 的原始密码,则使用此方法。Use this method if you have the original password that was used to create SSISDB.
- 通过运行 Integration ServicesIntegration Services catalog.check_schema_version ,确定 SSISDB 目录架构与二进制文件(ISServerExec 和 SQLCLR 程序集)是否兼容。Determine whether the SSISDB catalog schema and the Integration ServicesIntegration Services binaries (ISServerExec and SQLCLR assembly) are compatible, by running catalog.check_schema_version.
- 若要确认 SSISDB 数据库已成功还原,请针对 SSISDB 目录执行操作,如运行部署到 Integration ServicesIntegration Services 服务器的包。To confirm that the SSISDB database has been restored successfully, perform operations against the SSISDB catalog such as running packages that have been deployed to the Integration ServicesIntegration Services server.有关详细信息,请参阅 使用 SQL Server Management Studio 在 SSIS 服务器上运行包。For more information, see Run a Package on the SSIS Server Using SQL Server Management Studio.
移动 SSIS 数据库To Move the SSIS Database
- 按移动用户数据库的说明操作。Follow the instructions for moving user databases.有关详细信息,请参阅 Move User Databases。For more information, see Move User Databases.确保您备份 SSISDB 数据库的主密钥并保护备份文件。Ensure that you back up the master key for the SSISDB database and protect the backup file.有关详细信息,请参阅 备份 SSIS 数据库。For more information, see To Back up the SSIS Database.确保在尚未创建 SSISDB 目录的新 SQL ServerSQL Server 实例中创建 Integration Services (SSIS) 相关对象。Ensure that the Integration Services (SSIS) relevant objects are created in the new SQL ServerSQL Server instance where the SSISDB catalog has not yet been created.