SQL Server 2008

  1. Upgrade Advisor detected an AFTER trigger nested inside an INSTEAD OF trigger that is defined on one or more tables. Nested ...
  2. Upgrade Advisor detected an instance of SQL Server running under a Network Service or Local Service account on a Microsoft ...
  3. Upgrade Advisor detected data or log files that are not set to autogrow. In SQL Server 2005 and later, new and enhanced features ...
  4. Upgrade Advisor detected database files on a compressed drive. SQL Server 2008 cannot create or upgrade databases on compressed ...
  5. Upgrade Advisor detected DISK INIT statements. The DISK INIT statement, used in earlier versions of SQL Server to create ...
  6. Upgrade Advisor detected IIS 5.1 on the 32-bit version of Windows XP, which requires exclusive use of port 80. Upgrade will ...
  7. Upgrade Advisor detected one or more custom data processing extensions on the report server. Upgrade can continue, but you ...
  8. Upgrade Advisor detected one or more custom delivery extensions on the report server that is being upgraded. Upgrade can ...
  9. Upgrade Advisor detected one or more IP address restrictions on the IIS web site that hosts the report server or Report Manager ...
  10. Upgrade Advisor detected one or more SOAP/HTTP endpoints. The SOAP/HTTP endpoints feature will be removed from SQL Server ...
  11. Upgrade Advisor detected Schema with the name CDC - if you want to enable CDC post upgrade for that database then the schema ...
  12. Upgrade Advisor detected statements that drop system objects. System objects in SQL Server 2005 and later, including extended ...
  13. Upgrade Advisor detected statements that reference the INFORMATION_SCHEMA.SCHEMATA view. In earlier versions of SQL Server, ...
  14. Upgrade Advisor detected statements that reference undocumented system stored procedures and extended stored procedures that ...
  15. Upgrade Advisor detected statements that update the system catalog. Direct system catalog updates are not allowed in SQL ...
  16. Upgrade Advisor detected stored procedures that use one or more of the following discontinued properties: DataTimeout, ConnectTimeout, ...
  17. Upgrade Advisor detected that the instance metadata is missing from the system databases. Notification Services will not ...
  18. Upgrade Advisor detected that the instance of Notification Services uses custom components. Recompile all custom components ...
  19. Upgrade Advisor detected that you do not have any queued updating subscriptions that use Microsoft Message Queuing (MSMQ). ...
  20. Upgrade Advisor detected that you have one or more merge publications on the Microsoft Desktop Engine (MSDE) instance you ...
  21. Upgrade Advisor detected that you might have one or more queued updating subscriptions that use Microsoft Message Queuing ...
  22. Upgrade Advisor detected that you no SQL Server Agent jobs related to replication on the MSDE instance you are upgrading. ...
  23. Upgrade Advisor detected the use of outer join operators *= and =*. These operators are not supported in 90 or later compatibility ...
  24. Upgrade Advisor detected the use of the FOR BROWSE clause in a view. The FOR BROWSE clause is allowed (and ignored) in views ...
  25. Upgrade Advisor detected the user name sys in a database. This name is reserved in SQL Server 2008. Rename the user before ...
  26. Upgrade Advisor detected two conflicting registrations for the same instance. Multiple registrations occur when the instance ...
  27. Upgrade Advisor detected UPDATETEXT statements that read and write to the same binary large objects (BLOB) by using the same ...
  28. Upgrade Advisor did not find the specified instance of Notification Services in the registry and, therefore, cannot analyze ...
  29. Upgrade Advisor either could not find the instance and application databases, or the databases are corrupt. Make sure the ...
  30. Upgrade Advisor found that you are using SQL Server Authentication for one or more local connections for agents. On upgrade ...
  31. Upgrade Advisor has detected an index on a view with the IGNORE_DUP_KEY option set to ON. In SQL Server 2005 or later, this ...
  32. Upgrade Advisor has detected duplicate table or view index names. Rename the indexes to remove duplicates before upgrading ...
  33. Upgrade Advisor has detected that the AUTO_UPDATE_STATISTICS database SET option is OFF. As a result, database statistics ...
  34. Upgrade Advisor has detected that you are using log shipping. SQL Server 2000 log shipping is incompatible with log shipping ...
  35. Upgrade Advisor has detected the 0xFFFF character in an object identifier. In SQL Server 2005 and later, objects such as ...
  36. Upgrade Advisor is unable to scan packages with invalid characters (/ \ : . =) in the package name. Rename DTS packages that ...
  37. Upgrade Advisor is unable to scan packages with password protection. To scan encrypted DTS packages, use the SSIS Package ...
  38. Upgrade Advisor may be unable to scan a package for reasons that include a corrupted file, insufficient permissions, or other ...
  39. Upgrade Advisor reports only on the most recent version of each DTS package. To report on multiple versions of a DTS package, ...
  40. Upgrade Advisor was unable to analyze Integration Services packages. For more information, see the Upgrade Advisor log file ...
  41. Upgrade determined that you have custom configured your string comparison flags for your Microsoft SQL Server Analysis Services ...
  42. Upgrade is blocked due to an incomplete report server configuration. You must either configure the report server database, ...
  43. Upgrade is blocked. The report server uses one or more custom rendering extensions. configured. Custom rendering extensions ...
  44. Upgrade of database "%1!s!" failed because index "%2!s!" on object ID %3!s! has the same name as that of another index on ...
  45. Upgrade of database "%1!s!" failed because it contains a user named "sys" which is a reserved user or schema name in this ...
  46. Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade ...
  47. URLs that do not begin with "HTTP://" or "HTTPS://" are considered unsafe and will not be displayed by most applications. ...
  48. Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future ...
  49. Usage: EXECUTE xp_sqlagent_monitor @command = 'START', @netsend = ' ', @restart = or EXECUTE xp_sqlagent_monitor @command ...
  50. usage: Sqlcmd -U login id -P password -S server -H hostname -E trusted connection -d use database name -l login timeout -t ...
  51. Use a currency conversion to define rules for converting and analyzing multinational data in the cube. Conversion rules are ...
  52. Use a financial reporting aggregation to define a weighted custom rollup of members for an attribute. The aggregation will ...
  53. Use account intelligence to assign standard accounting classifications, such as income and expense, to members of an account ...
  54. Use dimension intelligence to specify a standard business type for a dimension and its attributes. Client applications can ...
  55. Use dimension writeback to allow users to modify the dimension structure manually. Updates to a write-enabled dimension are ...
  56. Use each row from the top input to build a hash table, and each row from the bottom input to probe into the hash table, outputting ...
  57. Use Extract Column to specify which columns in the data flow contain data to be extracted. Use File Path Column to specify ...
  58. Use of hint "%1!s!" on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. ...
  59. Use of level0type with value 'TYPE' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty ...
  60. Use of level0type with value 'USER' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty ...
  61. Use of NOLOCK or READUNCOMMITTED hints in the FROM clause of an UPDATE or DELETE statement on the target table of the statement ...
  62. Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma ...
  63. Use one of the following methods to increase storage space: (1) If you are using the graphical user interface, enter the ...
  64. Use ordering to specify how the members of an attribute are ordered. Members can be ordered by the name or key of the attribute, ...
  65. Use semiadditive behavior to define the aggregation method for individual measures or members of an account type attribute. ...
  66. Use the Report Viewer to view reports running on a Reporting Services report server configured for SharePoint integration. ...
  67. Use the Reporting Services Configuration Manager tool to define or modify settings for the Report Server and Report Manager. ...
  68. Use the two digit year cutoff option to specify an integer from 1753 to 9999 that represents the cutoff year for interpreting ...
  69. Use the value defined on this page for this parameter but do not show the parameter or value to the user when the report ...
  70. Use this page to assign a user or group to a system role. You can also use this page to create or modify a system role definition. ...
  71. Use this page to change the roles that are assigned to {0}. This page contains system role definitions that apply to the ...
  72. Use this page to create a Report Builder model. Click the OK button to generate a model. Generating a model may take several ...
  73. Use this page to determine which tasks {1} can perform on {0}. You can assign {1} to more than one role if you want to expand ...
  74. Use this page to grant Reporting Services accounts access to SharePoint databases. This step is required for Reporting Services ...
  75. Use this page to secure individual model items independently for this model. By default model items inherit security from ...