SQL Server 2008

  1. There is no route to service {0} and broker instance {1}, but dynamic routing is present in the database. Either the Service ...
  2. There is no route to service {0}, but dynamic routing is present in the database. Either the Service Broker Configuration ...
  3. There is no sufficient information about mapping SSIS types to data types of the selected .NET data provider. As a result, ...
  4. There is no user interface to install SQL Server patches in this release. To apply this patch, run this installation from ...
  5. There is no user table matching the input name '%1!s!' in the current database or you do not have permission to access the ...
  6. There is not enough data to generate the requested sample. The sample was scaled down to {0} rows. {1} The target state is ...
  7. There is not enough disk space on the volume '[2]' to continue the install with recovery enabled. 3 KB are required, but ...
  8. There must be at least one column of Fixed, Changing, or Historical type on the input of a Slowly Changing Dimension transform. ...
  9. There must be at least one column type of Key on the input of a Slowly Changing Dimension transformation. Set at least one ...
  10. There should be access to at least one Integration Services Proxy account under Integration Services subsystem in-order to ...
  11. There was a failure applying your new e-mail information. The previously configured settings will be used for content delivery. ...
  12. There was a failure setting your SMTP server configuration. Please make sure you specified a valid SMTP server and try again. ...
  13. There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system ...
  14. There was a problem resequencing a sequence table to contain the necessary merged actions. Database table: "{0}"; database ...
  15. There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters ...
  16. There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The ...
  17. There was an error creating a temporary file that is needed to complete this installation.{ Folder: 3]. System error code: ...
  18. There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and ...
  19. There was an error getting the cluster group name. Error: {0}. Ensure that the name you provided is correct, and try again. ...
  20. There was an error refreshing the UI after applying your changes. Review the other tasks to determine if failures were encountered ...
  21. There was an error refreshing the UI. The item status displayed in the left navigation panel or the currently active input ...
  22. There was an error refreshing the UI. The item status displayed in the left navigation panel or the currently active input ...
  23. There was an error trying enlist an ODBC connection in a transaction. The SQLSetConnectAttr failed to set the SQL_ATTR_ENLIST_IN_DTC ...
  24. There was an error while switching panels. The most likely cause is an error retrieving WMI properties. The exception details ...
  25. There was an exception migrating ForEachPropertyMapping node "{0}" when migrating the package from version {1} to version ...
  26. There was an exception while creating EnumeratedValue variable and variable mapping on ForEach Loop container "{0}" (ID = ...
  27. There was not enough memory to read the PowerShell script for a job step. You can free memory by closing inactive applications, ...
  28. There were errors generated during the calculation of the CACHE statements. Query processing will continue without calculating ...
  29. There were no cluster disks available in the cluster. At least one disk is required to create a SQL Server failover cluster ...
  30. There were no cluster disks specified. To continue, specify at least one disk to create a SQL Server failover cluster instance. ...
  31. There were no input columns with a valid join to a reference table column. Make sure that there is at least one join defined ...
  32. There were no valid input columns with JoinType column property set to Fuzzy. Performance on Exact joins may be improved ...
  33. These are the total sessions/connections associated with the login, and having active requests irrespective of databases. ...
  34. These services will be configured automatically where possible to use a low privilege account. On some older Windows versions ...
  35. This account is currently associated with profile(s): {0}. You must remove this account from associated profiles, or delete ...
  36. This action marks each subscription that supports automatic reinitialization to be reinitialized from a snapshot the next ...
  37. This action marks each subscription that supports automatic reinitialization to be reinitialized the next time its Distribution ...
  38. This action marks each subscription to be reinitialized from a snapshot the next time its Merge Agent runs. Subscriptions ...
  39. This action marks each subscription to be reinitialized the next time its Distribution Agent runs. You must run the Snapshot ...
  40. This action marks subscription '{0}' to be reinitialized from a snapshot the next time its Distribution Agent runs. You must ...
  41. This action marks subscription '{0}' to be reinitialized from a snapshot the next time its Distribution or Merge Agent runs. ...
  42. This action will remove the selected subscription information, but not the previously replicated data, from database '{0}'. ...
  43. This article cannot use the '%1!s!' feature because the publication compatibility level is less than 90. Use sp_changemergepublication ...
  44. This article has now settings to disable uploads and compensate_for_errors=true. However, local and anonymous subscribers ...
  45. This attribute is specified as the granularity attribute for the '{0}' measure group. You can set its aggregation usage setting ...
  46. This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH ...
  47. This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate ...
  48. This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path ...
  49. This backup set contains records that were logged before the designated point in time. The database is being left in the ...
  50. This backup set will not be restored because all data has already been restored to a point beyond the time covered by this ...
  51. This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before ...
  52. This buffer has been orphaned. The buffer manager has shut down, leaving an outstanding buffer and no cleanup will occur ...
  53. This buffer represents the end of the rowset and its row count cannot be altered. An attempt was made to call AddRow or RemoveRow ...
  54. This business intelligence enhancement requires the dimension to have a data source. Generate a data source view for the ...
  55. This cell contains the text string . You can press Ctrl+0 inside the cell to replace it with a NULL value. Do you want to ...
  56. This chart area cannot be deleted at this time. The series hosted in it are incompatible with series in other chart areas. ...
  57. This chart area cannot be selected because it has another series of incompatible Chart Type. Please select another Chart ...
  58. This chart area cannot be selected because it has another series of incompatible chart type. Select another chart area or ...
  59. This chart contains groupings that are not supported at design time. When you save the report, these groupings will automatically ...
  60. This column contains an Oracle data type that, when converted to a SQL Server data type, may result in a loss of data or ...
  61. This column must be published because it does not have the IDENTITY property set, it does not allow null, and it has no default ...
  62. This column must be published because it is a primary key column. Primary key columns are required in transactional publications. ...
  63. This column must be published because it is a primary key column. When a table with a primary key column is published in ...
  64. This column was created by the Business Intelligence Wizard. An attribute in the Time dimension has been created that is ...
  65. This command requires a database encryption scan on database '%1!s!'. However, the database has changes from previous encryption ...
  66. This command will connect to the hosting provider and download database configuration information. If successful, existing ...
  67. This command will connect to the hosting provider and download database configuration information. If the operation is successful, ...
  68. This component has no available input columns and cannot be configured correctly. To fix this problem, connect an output ...
  69. This component has no available input columns and it cannot be configured correctly. To correct this problem, connect an ...
  70. This component has no available input columns. Do you want to continue editing the available properties of this component? ...
  71. This component only supports data mining PREDICTION JOIN queries executed against the target model based on the data in the ...
  72. This computer is a Windows domain controller. SQL Server failover clusters cannot be installed where one of the cluster nodes ...
  73. This computer must have at least Windows 2000 SP4 and the user must have administrator privileges in order to install ProductShortName]. ...
  74. This cube will contain the source cube on which the mining model is based and the new dimension you specify in this wizard ...
  75. This cube's template contains one or more Multidimensional Expressions (MDX) expressions that may no longer be valid if the ...