SQL Server 2008 R2
- All articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' ...
- All articles in the publication have been marked for data validation (rowcount and checksum). The validation will be performed ...
- All articles in the publication have been marked for data validation (rowcount-only). The validation will be performed when ...
- All columns must be published in a merge publication from a Publisher on SQL Server version 7.0. Column filtering is not ...
- All columns of a CDC unique index must be defined as NOT NULL. Index '%1!s!' selected as the CDC unique index for source ...
- All events in the workload were not analysed. DTA assumes a default time of 8 hours. Consider providing a time bound using ...
- All events in the workload were not evaluated. Consider increasing time bound using (1) Limit tuning time in Tuning Options ...
- All events in the workload were not evaluated. DTA assumes a default time of 8 hours. Consider providing time bound using ...
- All events in the workload were not tuned. Consider increasing time bound using (1) Limit tuning time in Tuning Options screen ...
- All events in the workload were not tuned. DTA assumes a default time of 8 hours. Consider providing time bound using (1) ...
- All index columns must be mapped to input columns when the Lookup transformation is configured to use a Cache connection ...
- All merge articles must contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server adds ...
- All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final ...
- All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
- All related columns between table '{0}' and table '{1}' must be specified within the same row. Relate columns within the ...
- All roles and members will be copied to the destination database. Any existing role and membership data will be replaced. ...
- All schedulers on Node %1!s! appear deadlocked due to a large number of worker threads waiting on %2!s!. Process Utilization ...
- All stored connection strings, credentials, and encrypted values in a subscription will be deleted. After you delete this ...
- All the available inputs on the target component are connected to outputs. Edit this component to define new inputs before ...
- All the events in the workload were ignored due to syntax errors.The most common reason for this error is that the database ...
- All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There ...
- All updategram/diffgrams nodes with siblings must have ids, either user specified ones or mapping schema based key field ...
- Allows access to all members currently in the dimension, and allows access to members that are added to the topmost level ...
- Allows to track creation and deletion of internal parameter tables. Those tables are used to store information about active ...
- Allows to track when a new subscription request falls into an already existing class of (Match) or a new class (Create). ...
- ALTER ASSEMBLY failed because assembly '%1!s!' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to ...
- ALTER ASSEMBLY failed because it is referenced by object '%1!s!'. Assemblies that are referenced by SQL objects cannot be ...
- ALTER ASSEMBLY failed because required property '%1!s!' in type '%2!s!' was not found with the same signature in the updated ...
- ALTER ASSEMBLY failed because serialization data of type '%1!s!' would change in the updated assembly. Persisted types are ...
- ALTER ASSEMBLY failed because serialization layout of type '%1!s!' would change as a result of a change in type '%2!s!' in ...
- ALTER ASSEMBLY failed because table, view or constraint '%1!s!' depends on this assembly. Use WITH UNCHECKED DATA to skip ...
- ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
- ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
- ALTER ASSEMBLY failed because the identity of referenced assembly '%1!s!' has changed. Make sure the version, name, and public ...
- ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
- ALTER ASSEMBLY failed because the MaxLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
- ALTER ASSEMBLY failed because the mutator attribute of method '%1!s!' in type '%2!s!' would change in the updated assembly, ...
- ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. ...
- ALTER ASSEMBLY failed because the required field "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
- ALTER ASSEMBLY failed because the required method "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
- ALTER ASSEMBLY failed because the serialization format of type '%1!s!' would change in the updated assembly. Persisted types ...
- ALTER ASSEMBLY failed because the user-defined aggregate "%1!s!" does not exist or is not correctly defined in the updated ...
- ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%1!s!". Refer to column "has_unchecked_assembly_data" ...
- ALTER DATABASE "%1!s!" command cannot be executed until both partner server instances are up, running, and connected. Start ...
- Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling ...
- Alter partition function statement failed. Cannot repartition table '%1!s!' by altering partition function '%2!s!' because ...
- Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. ...
- ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is ...
- ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%1!s!' did not succeed due to the following reason: ...
- ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%1!s!' with ROWGUIDCOL property. ...
- ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%1!s!' with ROWGUIDCOL property. ...
- ALTER TABLE DROP COLUMN failed because '%1!s!' is the only data column in table '%2!s!'. A table must have at least one data ...
- ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' at ordinal %2!s! in table '%3!s!' has a different name than the ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' and '%3!s!'. ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same collation in tables '%2!s!' and '%3!s!'. ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same column set property in tables '%2!s!' and ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same FILESTREAM storage attribute in tables ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same nullability attribute in tables '%2!s!' ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same persistent attribute in tables '%2!s!' ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ROWGUIDCOL property in tables '%2!s!' and ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same sparse storage attribute in tables '%2!s!' ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same XML Schema Collection in tables '%2!s!' ...
- ALTER TABLE SWITCH statement failed because column '%1!s!' has data type %2!s! in source table '%3!s!' which is different ...
- ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does ...
- ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not ...
- ALTER TABLE SWITCH statement failed. %1!s! '%2!s!' is in filegroup '%3!s!' and partition %4!s! of %5!s! '%6!s!' is in filegroup ...
- ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' and check constraint '%3!s!' in target ...
- ALTER TABLE SWITCH statement failed. Check constraint '%1!s!' in source table '%2!s!' is NOCHECK constraint but the matching ...
- ALTER TABLE SWITCH statement failed. Check constraints of source table '%1!s!' allow values that are not allowed by range ...
- ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table '%1!s!' allows values that are ...
- ALTER TABLE SWITCH statement failed. Column '%1!s!' in table '%2!s!' is computed column but the same column in '%3!s!' is ...
- ALTER TABLE SWITCH statement failed. Computed column '%1!s!' defined as '%2!s!' in table '%3!s!' is different from the same ...
- ALTER TABLE SWITCH statement failed. Foreign key constraint '%1!s!' is disabled in source table '%2!s!' and the corresponding ...