Add Server GroupCancelOKServer Group DescriptionServer Group NameAre you sure you want to deleteAre you sure you want to deleteAzure SQL Servers cannot be used as Central Management ServersCentral Management Server Group already has a Registered Server with the name {0}{0} already has a Server Group with the name {1}NoYesAdd Central Management Server...No resources foundUnexpected error occurred while loading saved servers {0}Loading ...You cannot add a shared registered server with the same name as the Configuration ServerEditionCompatibility LevelOwnerPricing TierTypeVersionMSSQL configurationDeclares the application workload type when connecting to a serverApplication intentThe name of the applicationApplication nameWhen true, enables usage of the Asynchronous functionality in the .Net Framework Data ProviderAsynchronous processingAttach DB filenameThe name of the primary file, including the full path name, of an attachable databaseAttached DB file nameAzure Active Directory - Universal with MFA supportWindows AuthenticationSQL LoginSpecifies the method of authenticating with SQL ServerAuthentication typeDefault column encryption setting for all the commands on the connectionColumn encryptionNumber of attempts to restore connectionConnect retry countDelay between attempts to restore connectionConnect retry intervalThe length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an errorConnect timeoutCustom name of the connectionName (optional)When true, indicates the connection should be from the SQL server context. Available only when running in the SQL Server processContext connectionThe SQL Server language record nameCurrent languageWhen true, SQL Server uses SSL encryption for all data sent between the client and server if the server has a certificate installedEncryptThe name or network address of the instance of SQL Server that acts as a failover partnerFailover partnerAdvancedConnection ResiliencyContextInitializationPoolingReplicationSecuritySourceThe minimum amount of time (in seconds) for this connection to live in the pool before being destroyedLoad balance timeoutThe maximum number of connections allowed in the poolMax pool sizeThe minimum number of connections allowed in the poolMin pool sizeMulti subnet failoverWhen true, multiple result sets can be returned and read from one connectionMultiple active result setsSize in bytes of the network packets used to communicate with an instance of SQL ServerPacket sizeIndicates the password to be used when connecting to the data sourcePasswordWhen false, security-sensitive information, such as the password, is not returned as part of the connectionPersist security infoWhen true, the connection object is drawn from the appropriate pool, or if necessary, is created and added to the appropriate poolPoolingPortUsed by SQL Server in ReplicationReplicationDescription of the SQL Server instanceServer DescriptionName of the SQL Server instanceServerWhen true (and encrypt=true), SQL Server uses SSL encryption for all data sent between the client and server without validating the server certificateTrust server certificateIndicates which server type system then provider will expose through the DataReaderType system versionIndicates the user ID to be used when connecting to the data sourceUser nameThe name of the workstation connecting to SQL ServerWorkstation IdMicrosoft SQL ServerSupport for managing SQL Server Central Management ServersSQL Server Central Management ServersShould 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)should commas be placed at the beginning of each statement in a list e.g. ', mycolumn2' instead of at the end e.g. 'mycolumn1,'Should references to objects in a select statements be split into separate lines? E.g. for 'SELECT C1, C2 FROM T1' both C1 and C2 will be on separate lines[Optional] Log debug output to the console (View -> Output) and then select appropriate output channel from the dropdownMaximum number of old files to remove upon startup that have expired mssql.logRetentionMinutes. Files that do not get cleaned up due to this limitation get cleaned up next time Azure Data Studio starts up.Number of minutes to retain log files for backend services. Default is 1 week.Microsoft SQL ServerShould BIT columns be displayed as numbers (1 or 0)? If false, BIT columns will be displayed as 'true' or 'false'New Server Registration...New Server Group...DeleteDeleteDeleteCentral Management ServersRefreshRefresh Server GroupAdd Central Management ServerCentral Management Servers[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[Optional] Do not show unsupported platform warningsCompatibility LevelLast Database BackupLast Log BackupOwnerRecovery ModelComputer NameOS VersionEditionVersion