Account does not exist. 帐户不存在。 Azure Data Studio needs to contact Azure Key Vault to access a column master key for Always Encrypted, but no linked Azure account is available. Please add a linked Azure account and retry the query. Azure Data Studio 需要连接 Azure Key Vault 才能访问 Always Encrypted 的列主密钥,但没有可用的链接 Azure 帐户。请添加链接的 Azure 帐户,然后重试查询。 The configured Azure account for {0} does not have sufficient permissions for Azure Key Vault to access a column master key for Always Encrypted. 为 {0} 配置的 Azure 帐户没有足够的权限让 Azure Key Vault 访问 Always Encrypted 的列主密钥。 ({0} KB) ({0} KB) Downloaded {0} 已下载 {0} Downloading {0} 正在下载 {0} Downloading {0} 正在下载 {0} Failed to start {0} 未能启动 {0} Installed {0} 安装于 {0} Installing {0} 正在安装 {0} Installing {0} to {1} 正在将 {0} 安装到 {1} Starting {0} 正在启动 {0} {0} Started {0} 已启动 Notebooks 笔记本 Only .ipynb Notebooks are supported 仅支持 .ipynb 笔记本 Unsupported platform 平台不受支持 $(sync~spin) {0}... $(sync~spin) {0}... Cancel 取消 Cancel operation? 是否取消操作? Search Server Names 搜索服务器名称 Error notifying of node change: {0} 通知节点更改时出错: {0} Root Session for node {0} does not exist 节点 {0} 的会话不存在 View Known Issues 查看已知问题 {0} component exited unexpectedly. Please restart Azure Data Studio. {0} 个组件意外退出。请重启 Azure Data Studio。 % of Cluster data capacity used 已使用的群集数据容量百分比 Application name 应用程序名称 Authentication type 身份验证类型 Azure Active Directory - Universal with MFA support Azure Active Directory - 支持 MFA 的通用目录 Azure Data Explorer (Kusto) Azure 数据资源管理器(Kusto) Cluster 群集 Connect retry count 连接重试次数 Connect retry interval 连接重试间隔 Connect timeout 连接超时 Connection Resiliency 连接复原力 Context 上下文 Custom name of the connection 连接的自定义名称 Database 数据库 Database Name 数据库名称 Delay between attempts to restore connection 两次尝试恢复连接之间的延迟 Failover partner 故障转移伙伴 Indicates the password to be used when connecting to the data source 指示连接到数据源时使用的密码 Indicates the user ID to be used when connecting to the data source 指示连接到数据源时使用的用户 ID Initialization 初始化 KUSTO configuration KUSTO 配置 Kusto cluster name Kusto 群集名称 Name 名称 Name 名称 Name (optional) 名称(可选) New Notebook 新建笔记本 No Authentication 无身份验证 Number of attempts to restore connection 尝试还原连接的次数 Open Notebook 打开笔记本 Password 密码 Security 安全性 Should BIT columns be displayed as numbers (1 or 0)? If false, BIT columns will be displayed as 'true' or 'false' 是否应将 BIT 列显示为数字(1 或 0)? 若否,则 BIT 列将显示为 "true" 或 "false" Should column definitions be aligned? 列定义是否应对齐? Should data types be formatted as UPPERCASE, lowercase, or none (not formatted) 数据类型应格式化为大写、小写还是无(不格式化) Should keywords be formatted as UPPERCASE, lowercase, or none (not formatted) 关键字应格式化为大写、小写还是无(不格式化) Size (MB) 大小(MB) Size (MB) 大小(MB) Source Specifies the method of authenticating with Kusto Server 指定使用 Kusto Server 进行身份验证的方法 Status 状态 The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error 在终止尝试并生成错误之前等待连接到服务器的时长(秒) The name of the application 应用程序的名称 The name of the initial catalog or database in the data source 数据源中的初始目录或数据库的名称。 The name of the workstation connecting to Kusto Server 连接到 Kusto Server 的工作站的名称 The name or network address of the instance of Kusto Server that acts as a failover partner 充当故障转移伙伴的 Kusto Server 实例的名称或网络地址 Total Machines in the cluster 群集中的总计算机数 Type 类型 User Authentication 用户身份验证 User name 用户名 Workstation Id 工作站 ID [Optional] Log debug output to the console (View -> Output) and then select appropriate output channel from the dropdown [可选] 将调试输出记录到控制台(“查看”->“输出”),然后从下拉列表中选择相应的输出通道 [Optional] Log level for backend services. Azure Data Studio generates a file name every time it starts and if the file already exists the logs entries are appended to that file. For cleanup of old log files see logRetentionMinutes and logFilesRemovalLimit settings. The default tracingLevel does not log much. Changing verbosity could lead to extensive logging and disk space requirements for the logs. Error includes Critical, Warning includes Error, Information includes Warning and Verbose includes Information [可选] 后端服务的日志级别。Azure Data Studio 在每次启动时都会生成文件名;如果文件已存在,日志条目将追加到该文件。有关旧日志文件的清理,请参阅 logRetentionMinutes 和 logFilesRemovalLimit 设置。默认 tracingLevel 记录的内容很少。更改详细级别可能提升日志的记录和磁盘空间要求。“错误”包含“严重”,“警告”包含“错误”,“信息”包含“警告”,“详细级别”包含“信息”