SQL Server 2008

  1. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate custom tasks in SQL Server 2000 ...
  2. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate Data Driven Query tasks in SQL ...
  3. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate Dynamic Properties tasks in SQL ...
  4. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate Execute Packages tasks that load ...
  5. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate Parallel Data Pump tasks in SQL ...
  6. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate the Analysis Services task in SQL ...
  7. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate the Data Mining Prediction Query ...
  8. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate transaction settings in SQL Server ...
  9. The SQL Server 2008 Data Mining Add-ins for Office 2007 cannot connect to an instance of SQL Server Analysis Services version ...
  10. The SQL Server 2008 Data Mining Add-ins for Office 2007 help you uncover hidden patterns and relationships in your data and ...
  11. The SQL Server 2008 Setup wizard has encountered an internal error as it was not able to find a way to determine what changes ...
  12. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. Since the ...
  13. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. To continue, ...
  14. The SQL Server Analysis Services feature failed when it was initially installed. The feature must be removed before the current ...
  15. The SQL Server and Analysis Services features of the selected clustered SQL Server 2005 instance have been installed into ...
  16. The SQL Server Compact connection cannot be acquired. {0} Click Yes if you want to save the current settings. Click No if ...
  17. The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current ...
  18. The SQL Server Execute Package Utility requires Integration Services to be installed by one of these editions of SQL Server ...
  19. The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL ...
  20. The SQL Server failed to initialize VIA support library %1!s!]. This normally indicates the VIA support library does not ...
  21. The SQL Server failover cluster instance '{0}' was not correctly detected. The instance was discovered on the local node ...
  22. The SQL Server failover cluster instance name '{0}' already exists as a clustered resource. Specify a different failover ...
  23. The SQL Server failover cluster instance name '{0}' already exists as a server on the network. Specify a different failover ...
  24. The SQL Server failover cluster services is not online, or the cluster cannot be accessed from one of its nodes. To continue, ...
  25. The SQL Server feature '{0}' is not in a supported state for repair, as it was installed in preparation to be clustered. ...
  26. The SQL Server feature '{0}' is not in a supported state for repair, as it was never successfully configured. Only features ...
  27. The SQL Server features on this computer are shown below. To remove a feature, select the checkbox next to the feature name. ...
  28. The SQL Server instance '{0}' already has an Instance ID '{1}' that is different than the specified Instance ID '{2}'. Specifying ...
  29. The SQL Server instance '{0}' which was already upgraded on machine '{1}' has an Instance ID '{2}' that is different than ...
  30. The SQL Server instance hosting the service {0} and broker instance {1} was not found. Ensure the tool is connected to this ...
  31. The SQL Server instance hosting the service {0} was not found. Ensure the tool is connected to this server to allow investigation ...
  32. The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when ...
  33. The SQL Server Integration Services service requires Integration Services to be installed by one of these editions of SQL ...
  34. The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. ...
  35. The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. ...
  36. The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) %1!s! for the SQL Server ...
  37. The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) %1!s! for the SQL Server ...
  38. The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. ...
  39. The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will ...
  40. The SQL Server patch package expects the installed SQL Server product to be at product version {0}, architecture {1}. Disqualified ...
  41. The SQL Server patch package is part of a general distribution release (GDR). This package cannot be applied since this SQL ...
  42. The SQL Server performance counter '%s' (instance '%s') of object '%s' is now above the threshold of %s (the current value ...
  43. The SQL Server performance counter '%s' (instance '%s') of object '%s' is now below the threshold of %s (the current value ...
  44. The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity ...
  45. The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation ...
  46. The SQL Server removal of SQL Server failover cluster '{0}' encountered an error deleting cluster resource '{1}'. The exception ...
  47. The SQL Server repair operation has set registry keys to default values, as follows: '{0}', field: '{1}'. Previous value: ...
  48. The SQL Server Reporting Services feature failed when it was initially installed. The feature must be removed before the ...
  49. The SQL Server resource group must be owned by the current cluster node. Setup requires access to shared cluster resources. ...
  50. The SQL Server Sertup user interface cannot be shown because it is already running. Wait for the other Setup operation to ...
  51. The SQL Server Service account does not have permission to register the supplied URL on the endpoint '%1!s!'. Use sp_reserve_http_namespace ...
  52. The SQL Server service account login or password is not valid. Use SQL Server Configuration Manager to update the service ...
  53. The SQL server specified by these connection properties does not support managed objects. Please choose a different server. ...
  54. The SQL Server SSIS Package Utilities require Integration Services to be installed by one of these editions of SQL Server ...
  55. The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a ...
  56. The SQL statement cannot be executed because filegroup '%1!s!' is offline. Use the sys.database_files or sys.master_files ...
  57. The SQL statement has been manually edited and the displayed values may not reflect the metadata of the destination table ...
  58. The SQL, AS and/or RS features of the instance chosen to upgrade have been installed into separate folders. This is not a ...
  59. The SQLBrowser is closing Analysis Services discovery support. There are no SQL Server Analysis Services instances or the ...
  60. The SQLBrowser is closing SQL Server and connectivity discovery support. There are no SQL Server instances or the discovery ...
  61. The SQLBrowser processing of requests against a particular IP address has encounted a critical error. Processing of requests ...
  62. The SQLMerge ActiveX control failed with error code 1!x! when attempting to access the registry key '%2'. Ensure that the ...
  63. The SQLServerAgent mail session is not running; check the mail profile and/or the SQLServerAgent service startup account ...
  64. The SSIS Data Flow Task could not be created. Verify that DTSPipeline.dll is available and registered. The wizard cannot ...
  65. The SSIS logging infrastructure failed with error code 1!8.8X!. This error indicates that this logging error is not attributable ...
  66. The SSIS logging provider "%1!s!" failed with error code 2!8.8X! (%3!s!). This indicates a logging error attributable to ...
  67. The SSIS managed helper object failed during creation with error 1!8.8X! "%2!s!". This occurs whenever CoCreateInstance CLSID_DTSManagedHelper ...
  68. The SSIS Package Upgrade Wizard upgrades packages created using the SQL Server 2005 tools and object models to SQL Server ...
  69. The SSIS Runtime has failed to start the distributed transaction due to error 1!8.8X! "%2!s!". The DTC transaction failed ...
  70. The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue ...
  71. The SSMA Tester Wizard is analyzing the Oracle database to find objects referred to in this test case. This may take few ...
  72. The start index %1!d! is not valid for function "%2!s!". The start index value must be an integer greater than 0. Start index ...
  73. The start index was not valid for function SUBSTRING. The start index value must be an integer greater than zero. The start ...
  74. The start width of the range. Measured as a percentage of the size of the gauge (height for horizontal gauges, width for ...
  75. The StartMode property indicates the start mode of the Win32 base service. \"Boot\" specifies a device driver started by ...