SQL Server 2012

  1. Upgrade Advisor analyzes any SQL Server 2008 R2, SQL Server 2008 or SQL Server 2005 components that are installed and identifies ...
  2. Upgrade Advisor analyzes your existing SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2 instances to provide assistance ...
  3. Upgrade Advisor cannot locate the SQL Server 2005 or SQL Server 2008 Integration Services files that it requires to analyze ...
  4. Upgrade Advisor cannot locate the SQL Server Integration Services files that it requires. Please ensure that Integration ...
  5. Upgrade Advisor could not connect to the database server specified in the registry. The database server must be running to ...
  6. Upgrade Advisor could not detect SQL Server components on the server. Please check if current user has the privilege to access ...
  7. Upgrade Advisor detected a database mirroring configuration. The database mirroring feature is deprecated and will be removed ...
  8. Upgrade Advisor detected a database with the database ID 32767. In SQL Server 2005 or later, this database ID is reserved. ...
  9. Upgrade Advisor detected a filegroup that is either set to read-only or is not in a writeable state. All filegroups must ...
  10. Upgrade Advisor detected a trigger that uses the SET XACT_ABORT OFF statement. In 80 compatibility mode, SET XACT_ABORT OFF ...
  11. Upgrade Advisor detected a view that uses the WITH CHECK OPTION and a TOP clause in the SELECT statement of the view or in ...
  12. Upgrade Advisor detected an AFTER trigger nested inside an INSTEAD OF trigger that is defined on one or more tables. Nested ...
  13. Upgrade Advisor detected an instance of SQL Server running under a Network Service or Local Service account on a Microsoft ...
  14. Upgrade Advisor detected data or log files that are not set to autogrow. In SQL Server 2005 and later, new and enhanced features ...
  15. Upgrade Advisor detected database files on a compressed drive. SQL Server 2012 cannot create or upgrade databases on compressed ...
  16. Upgrade Advisor detected DISK INIT statements. The DISK INIT statement, used in earlier versions of SQL Server to create ...
  17. Upgrade Advisor detected IIS 5.1 on the 32-bit version of Windows XP, which requires exclusive use of port 80. Upgrade will ...
  18. Upgrade Advisor detected one or more custom data processing extensions on the report server. Upgrade can continue, but you ...
  19. Upgrade Advisor detected one or more custom delivery extensions on the report server. Upgrade can continue, but you must ...
  20. Upgrade Advisor detected one or more IP address restrictions on the IIS web site that hosts the report server or Report Manager ...
  21. Upgrade Advisor detected one or more SOAP/HTTP endpoints. The SOAP/HTTP endpoints feature will be removed from SQL Server ...
  22. Upgrade Advisor detected Schema with the name CDC - if you want to enable CDC post upgrade for that database then the schema ...
  23. Upgrade Advisor detected statements that drop system objects. System objects in SQL Server 2005 and later, including extended ...
  24. Upgrade Advisor detected statements that reference the INFORMATION_SCHEMA.SCHEMATA view. In earlier versions of SQL Server, ...
  25. Upgrade Advisor detected statements that reference undocumented system stored procedures and extended stored procedures that ...
  26. Upgrade Advisor detected statements that update the system catalog. Direct system catalog updates are not allowed in SQL ...
  27. Upgrade Advisor detected statements that uses fn_get_audit_file. Queries using 'select from fn_get_audit_file' will break ...
  28. Upgrade Advisor detected stored procedures that use one or more of the following discontinued properties: DataTimeout, ConnectTimeout, ...
  29. Upgrade Advisor detected that the instance metadata is missing from the system databases. Notification Services will not ...
  30. Upgrade Advisor detected that the instance of Notification Services uses custom components. Recompile all custom components ...
  31. Upgrade Advisor detected that you do not have any queued updating subscriptions that use Microsoft Message Queuing (MSMQ). ...
  32. Upgrade Advisor detected that you have one or more merge publications on the Microsoft Desktop Engine (MSDE) instance you ...
  33. Upgrade Advisor detected that you might have one or more queued updating subscriptions that use Microsoft Message Queuing ...
  34. Upgrade Advisor detected that you no SQL Server Agent jobs related to replication on the MSDE instance you are upgrading. ...
  35. Upgrade Advisor detected the use of outer join operators *= and =*. These operators are not supported in 90 or later compatibility ...
  36. Upgrade Advisor detected the use of the FOR BROWSE clause in a view. The FOR BROWSE clause is allowed (and ignored) in views ...
  37. Upgrade Advisor detected the user name sys in a database. This name is reserved in SQL Server 2008. Rename the user before ...
  38. Upgrade Advisor detected two conflicting registrations for the same instance. Multiple registrations occur when the instance ...
  39. Upgrade Advisor detected UPDATETEXT statements that read and write to the same binary large objects (BLOB) by using the same ...
  40. Upgrade Advisor did not find the specified instance of Notification Services in the registry and, therefore, cannot analyze ...
  41. Upgrade Advisor either could not find the instance and application databases, or the databases are corrupt. Make sure the ...
  42. Upgrade Advisor found that you are using SQL Server Authentication for one or more local connections for agents. On upgrade ...
  43. 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 ...
  44. Upgrade Advisor has detected duplicate table or view index names. Rename the indexes to remove duplicates before upgrading ...
  45. Upgrade Advisor has detected that the AUTO_UPDATE_STATISTICS database SET option is OFF. As a result, database statistics ...
  46. Upgrade Advisor has detected that you are using log shipping. SQL Server 2000 log shipping is incompatible with log shipping ...
  47. Upgrade Advisor has detected the 0xFFFF character in an object identifier. In SQL Server 2005 and later, objects such as ...
  48. Upgrade Advisor may be unable to scan a package for reasons that include a corrupted file, insufficient permissions, or other ...
  49. Upgrade Advisor was unable to analyze Integration Services packages. For more information, see the Upgrade Advisor log file ...
  50. Upgrade from SQL Server "Denali" CTP0 to SQL Server 2012 is not supported. Uninstall SQL Server "Denali" CTP0 before installing ...
  51. Upgrade is blocked due to an incomplete report server configuration. You must either configure the report server database, ...
  52. Upgrade is blocked. The report server uses one or more custom rendering extensions. Custom rendering extensions must be updated ...
  53. 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 ...
  54. Upgrade of database "%1!s!" failed because it contains a user named "sys" which is a reserved user or schema name in this ...
  55. Upgrade of FILESTREAM container ID %1!s! in the database ID %2!s! failed because of container size recalculation error. Examine ...
  56. Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade ...
  57. Upper-Sorbian-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  58. URLs that do not begin with "HTTP://" or "HTTPS://" are considered unsafe and will not be displayed by most applications. ...
  59. Usage collection is not configured correctly. Check whether the following timer jobs have been enabled: Microsoft SharePoint ...
  60. usage DqsInstaller.exe {0} | {1} | {2} | {3} | {4} {6} {5} {0,-25} - Install Data Quality Services in the provided instance. ...
  61. Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future ...
  62. Usage: dreplay preprocess -m controller -i input_trace_file -d controller_working_dir -c config_file -f status_interval -? ...
  63. Usage: dreplay replay -m controller -d controller_working_dir -o -s target_server -w clients -c config_file -f status_interval ...
  64. Usage: dreplay status -m controller -f status_interval Options: -m Computer name of controller -f Frequency(in seconds) at ...
  65. Usage: DReplay.exe {preprocess|replay|status|cancel} options -?]} Verbs: preprocess Apply filters and prepare trace data ...
  66. Usage: EXECUTE xp_sqlagent_monitor @command = 'START', @netsend = ' ', @restart = or EXECUTE xp_sqlagent_monitor @command ...
  67. usage: Sqlcmd -U login id -P password -S server -H hostname -E trusted connection -N Encrypt Connection][-C Trust Server ...
  68. usage: Sqlcmd -U login id -P password -S server -H hostname -E trusted connection -N Encrypt Connection][-C Trust Server ...
  69. Usage: ssms.exe -S server_name[\instance_name -d database -U user -P password -E -nosplash file_name[, file_name]* -? -S ...
  70. Use a currency conversion to define rules for converting and analyzing multinational data in the cube. Conversion rules are ...
  71. Use a financial reporting aggregation to define a weighted custom rollup of members for an attribute. The aggregation will ...
  72. Use account intelligence to assign standard accounting classifications, such as income and expense, to members of an account ...
  73. Use control flow tasks to support data flow, prepare data, implement scripts and perform workflow and business intelligence ...
  74. Use dimension intelligence to specify a standard business type for a dimension and its attributes. Client applications can ...
  75. Use dimension writeback to allow users to modify the dimension structure manually. Updates to a write-enabled dimension are ...