By default, SQL Server 2005 or later Express, Evaluation, and Developer editions allow local client connections only. Enterprise, Standard, and Workgroup editions also listen for remote client connections over TCP/IP. Use the options below to change the protocols on which SQL Server listens for incoming client connections. TCP/IP is preferred over named pipes because it requires fewer ports to be opened across the firewall.
Bulk load: DataFileType was incorrectly specified as widechar. DataFileType will be assumed to be char because the data file ...
Bulk-logging has been turned on for database %1!s!. To ensure that all data has been secured, run backup log operations again. ...
Business rules cannot be applied because more than {0} members are affected. Choose Version > Validate Version to validate ...
Business rules cannot be published or refreshed while validation is running for the entity's model. Wait until validation ...
By default, SQL Server 2005 or later Express, Evaluation, and Developer editions allow local client connections only. Enterprise, ...
By impersonating the proxy account of the job (usually the SQL Server Agent service account of the server instance where ...
By removing a measure group, one or more dimension tables are no longer related to any measure group tables. You can use ...
By specifying this parameter and accepting the SQL Server license terms, you acknowledge that you have read and understood ...
Bypassing recovery for database '%1!s!' because it is marked as a mirror database, which cannot be recovered. This is an ...