SQL Server 2008

  1. After a table has been filtered, you can extend that filter to a second table by creating a join. When Subscribers receive ...
  2. After adding a new merge article, you must generate a new snapshot before changes from any subscription can be merged. Although ...
  3. After execution, some buffers were left outstanding. Some transform is hanging onto buffer references and if it freed them ...
  4. After it is set to True, the Allow peer-to-peer subscriptions property cannot be reset to False. Changing this property will ...
  5. After upgrading to SQL Server 2005 or later, third-party filters will not be loaded by the MSFTESQL service. To add a third-party ...
  6. After you specify the service accounts, logins will be created for each account, if necessary, and will be granted CONNECT ...
  7. After you upgrade to SQL Server 2008, you will also need to update these assemblies to the .NET Framework 3.5 SP1 version ...
  8. Agent '%1!s!' is retrying after an error. %2!s! retries attempted. See agent job history in the Jobs folder for more details. ...
  9. Agent XPs' component is turned off as part of the security configuration for this server. A system administrator can enable ...
  10. Aggregate functions that are used with CUBE, ROLLUP, or GROUPING SET queries must provide for the merging of subaggregates. ...
  11. AGGREGATE=1= Set , Numeric Expression ]=Returns a calculated value using the appropriate aggregate function, based on the ...
  12. AggregateFunction of measure %{name/} is FirstChild/LastChild/FirstNonEmpty/LastNonEmpty/AverageOfChildren and Time dimension ...
  13. Aggregation design can take a long time if the database has not been deployed previously. You can choose to interrupt this ...
  14. Aggregation design can take a long time if the database has not been saved previously. You can choose to interrupt this process ...
  15. Aggregation function %{aggfunc/} specified for mapping account type %{accounttype/} is not supported for ByAccount semiadditive ...
  16. Aggregations should not be created below the granularity attribute. This aggregation includes the '{0}' attribute which is ...
  17. Aggregations that were manually generated in previous version of Analysis Services are not migrated in Microsoft SQL Server ...
  18. Alert Replacement flag enables replacement of alert tokens. Applies only to SQL Server 2005 Service Pack 1 and later versions. ...
  19. All articles in a publication allowing updatable subscriptions contain a uniqueidentifier column named 'MSrepl_tran_version' ...
  20. All articles in the publication have been marked for data validation (rowcount and checksum). The validation will be performed ...
  21. All articles in the publication have been marked for data validation (rowcount-only). The validation will be performed when ...
  22. All columns must be published in a merge publication from a Publisher on SQL Server version 7.0. Column filtering is not ...
  23. All columns of a CDC unique index must be defined as NOT NULL. Index '%1!s!' selected as the CDC unique index for source ...
  24. All events in the workload were not analysed. DTA assumes a default time of 8 hours. Consider providing a time bound using ...
  25. All events in the workload were not evaluated. Consider increasing time bound using (1) Limit tuning time in Tuning Options ...
  26. All events in the workload were not evaluated. DTA assumes a default time of 8 hours. Consider providing time bound using ...
  27. All events in the workload were not tuned. Consider increasing time bound using (1) Limit tuning time in Tuning Options screen ...
  28. All events in the workload were not tuned. DTA assumes a default time of 8 hours. Consider providing time bound using (1) ...
  29. All index columns must be mapped to input columns when the Lookup transformation is configured to use a Cache connection ...
  30. All merge articles must contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server adds ...
  31. All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final ...
  32. All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target ...
  33. All roles and members will be copied to the destination database. Any existing role and membership data will be replaced. ...
  34. All schedulers on Node %1!s! appear deadlocked due to a large number of worker threads waiting on %2!s!. Process Utilization ...
  35. All stored connection strings, credentials, and encrypted values in a subscription will be deleted. After you delete this ...
  36. All the available inputs on the target component are connected to outputs. Edit this component to define new inputs before ...
  37. All the events in the workload were ignored due to syntax errors.The most common reason for this error is that the database ...
  38. All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There ...
  39. All updategram/diffgrams nodes with siblings must have ids, either user specified ones or mapping schema based key field ...
  40. Allows access to all members currently in the dimension, and allows access to members that are added to the topmost level ...
  41. Allows to track creation and deletion of internal parameter tables. Those tables are used to store information about active ...
  42. Allows to track when a new subscription request falls into an already existing class of (Match) or a new class (Create). ...
  43. Allows users to choose which program features will be installed and where they will be installed. Recommended for advanced ...
  44. ALTER ASSEMBLY failed because assembly '%1!s!' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to ...
  45. ALTER ASSEMBLY failed because it is referenced by object '%1!s!'. Assemblies that are referenced by SQL objects cannot be ...
  46. ALTER ASSEMBLY failed because required property '%1!s!' in type '%2!s!' was not found with the same signature in the updated ...
  47. ALTER ASSEMBLY failed because serialization data of type '%1!s!' would change in the updated assembly. Persisted types are ...
  48. ALTER ASSEMBLY failed because serialization layout of type '%1!s!' would change as a result of a change in type '%2!s!' in ...
  49. ALTER ASSEMBLY failed because table, view or constraint '%1!s!' depends on this assembly. Use WITH UNCHECKED DATA to skip ...
  50. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  51. ALTER ASSEMBLY failed because the function '%1!s!' of type '%2!s!' no longer satisfies indexability requirements, and is ...
  52. ALTER ASSEMBLY failed because the identity of referenced assembly '%1!s!' has changed. Make sure the version, name, and public ...
  53. ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  54. ALTER ASSEMBLY failed because the MaxLen attribute of type '%1!s!' would change in the updated assembly. Persisted types ...
  55. ALTER ASSEMBLY failed because the mutator attribute of method '%1!s!' in type '%2!s!' would change in the updated assembly, ...
  56. ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. ...
  57. ALTER ASSEMBLY failed because the required field "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  58. ALTER ASSEMBLY failed because the required method "%1!s!" in type "%2!s!" was not found with the same signature in the updated ...
  59. ALTER ASSEMBLY failed because the serialization format of type '%1!s!' would change in the updated assembly. Persisted types ...
  60. ALTER ASSEMBLY failed because the user-defined aggregate "%1!s!" does not exist or is not correctly defined in the updated ...
  61. ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%1!s!". Refer to column "has_unchecked_assembly_data" ...
  62. ALTER DATABASE "%1!s!" command cannot be executed until both partner server instances are up, running, and connected. Start ...
  63. Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling ...
  64. ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT ...
  65. ALTER DATABASE failed because the READ_COMMITTED_SNAPSHOT and the ALLOW_SNAPSHOT_ISOLATION options cannot be set to ON when ...
  66. Alter partition function statement failed. Cannot repartition table '%1!s!' by altering partition function '%2!s!' because ...
  67. Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. ...
  68. ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is ...
  69. ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%1!s!' did not succeed due to the following reason: ...
  70. ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%1!s!' with ROWGUIDCOL property. ...
  71. ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%1!s!' with ROWGUIDCOL property. ...
  72. 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 ...
  73. ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column ...
  74. ALTER TABLE SWITCH statement failed because column '%1!s!' at ordinal %2!s! in table '%3!s!' has a different name than the ...
  75. ALTER TABLE SWITCH statement failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...