SQL Server 2012

  1. Switch to diagram view of the model. Use the this view to perform metadata driven operations such as managing relationships ...
  2. Switching to the visual designer will discard your manual changes to the query. Do you want to use the visual designer anyway? ...
  3. Symbol folder path '{2}' does not exist. Valid existing symbol path is needed to register performance counters for service ...
  4. Symbol folder path '{2}' is not valid. Valid symbol path is needed to register performance counters for service '{0}' instance ...
  5. Synchronization failed. Synchronization from the server with ConnStringEncryptionEnabled=%d{BLSet/} and current server is ...
  6. Synchronization failed. Synchronization from the server with EnableBinaryXML=%d{BLSet/} and current server is running with ...
  7. Synchronization failed. Synchronization from the server with EnableCompression=%d{BLSet/} and current server is running with ...
  8. Synchronization of a secondary database, '%1!s!', was interrupted, leaving the database in an inconsistent state. The database ...
  9. Synchronization of a secondary database, '%1!s!', was interrupted, leaving the database in an inconsistent state. The database ...
  10. Synchronization of the mirror database, '%1!s!', was interrupted, leaving the database in an inconsistent state. The ALTER ...
  11. Synchronization Synchronization is useful to get a local object copy from database to memory and vice versa. It also helps ...
  12. SynchronizationAgent object property can only be retrieved when subscription is push type. Use PullSubscription object and ...
  13. Synchronize command Location subtree used for restoring of remote partition incomplete: it must contain non-empty DataSourceId, ...
  14. Synchronize command Location subtree used for updating of DS connection strings incomplete: it must contain non-empty DataSourceId, ...
  15. Synchronize command Location subtree used to specify folder location mapping must contain at least one non-empty Folder element. ...
  16. Synchronize failed as source server is set to work in Multidimensional mode and target server is set to work in Tabular mode. ...
  17. Synchronize failed as source server is set to work in Tabular mode and target server is set to work in Multidimensional mode. ...
  18. Synchronizes Report Server files (.rdl, .rsds, .smdl, .rsd, .rsc, .rdlx) from a SharePoint document library to the report ...
  19. Synchronizing dependencies (operation '{0}') for the catalog object "{2}" of extraction point "{1}", failed with the following ...
  20. Synchronizing dependencies for the catalog object "{1}" of extraction point "{0}", failed with the following message: "{2}". ...
  21. System administrator accounts cannot be specified when adding a brick to a matrix. Remove the command prompt parameter {0}, ...
  22. System Packages This tab allows selection of Oracle system packages that will be loaded during connection to the Oracle database. ...
  23. System process ID %1!s! tried to terminate the distributed transaction with Unit of Work ID %2!s!. This message occurs when ...
  24. System Schemas This tab allows selection of Oracle system schemas that will be loaded during connection to the Oracle database. ...
  25. System table '%1!s!' (object ID %2!s!, index ID %3!s!) is in filegroup %4!s!. All system tables must be in filegroup %5!s!. ...
  26. System table pre-checks: Object ID %1!s! has chain linkage mismatch. %2!s!->next = %3!s!, but %4!s!->prev = %5!s!. Check ...
  27. System table pre-checks: Object ID %1!s! has cross-object chain linkage. Page %2!s! points to %3!s! in alloc unit ID %4!s! ...
  28. System table pre-checks: Object ID %1!s!. Could not read and latch page %2!s! with latch type %3!s!. Check statement terminated ...
  29. System table pre-checks: Object ID %1!s!. Loop in data chain detected at %2!s!. Check statement terminated due to unrepairable ...
  30. System table pre-checks: Object ID %1!s!. Page %2!s! has unexpected page type %3!s!. Check statement terminated due to unrepairable ...
  31. Systematically create and register a data-tier application from an existing user database on a UCP enrolled instance of SQL ...
  32. Table "%1!s!" does not have any records for configuration. This occurs when configuring from a SQL Server table that has ...
  33. Table %1!s! contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter ...
  34. Table %1!s! has a partition key already. Explicitly specifying a new partition key is not allowed. Please use "Alter table". ...
  35. Table '%1!s!' can not be replicated because it contains imprecise Primary Key column, please recreate table without 'persisted' ...
  36. Table '%1!s!' cannot have table '%2!s!' as a parent in a logical record relationship because it already has a different parent ...
  37. Table '%1!s!' does not have a clustered primary key as required by the %2!s! index. Make sure that the primary key column ...
  38. Table '%1!s!' foreign key 'originating_server_id' does not have a matching value in the referenced view 'dbo.sysoriginatingservers_view'. ...
  39. Table '%1!s!' in database '%2!s!' is subscribing to transactional queued publication and published for merge for uploading ...
  40. Table '%1!s!' into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process ...
  41. Table '%1!s!' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for ...
  42. Table '%1!s!' may be out of synchronization. Rowcounts (actual: %2!s!, expected: %3!s!). Rowcount method %4!s! used (0 = ...
  43. Table '%1!s!' might be out of synchronization. Rowcounts (actual: %2!s!, expected %3!s!). Checksum values (actual: %4!s!, ...
  44. Table '%1!s!' needs to have a clustered primary key with less than %2!s! columns in it in order to create a primary XML index ...
  45. Table '%1!s!' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically. ...
  46. Table '%1!s!' will not be available during reorganizing index '%2!s!'. This is because the index reorganization operation ...
  47. Table '%1!s!'. Scan count %2!s!, logical reads %3!s!, physical reads %4!s!, read-ahead reads %5!s!, lob logical reads %6!s!, ...
  48. Table '%{table/}' cannot be queried in DirectQuery mode because it is based on multiple DSVs. Tables that get data from multiple ...
  49. Table '%{table/}' does not have a partition with DirectQueryUsage property set to DirectQueryOnly or InMemoryWithDirectQuery. ...
  50. Table '%{table/}' includes multiple partitions with DirectQueryUsage property set to DirectQueryOnly or InMemoryWithDirectQuery. ...
  51. Table '%{table/}' is not based on the same Data Source as other tables in the model. When querying in DirectQuery Mode all ...
  52. Table '{0}' is no longer filtered, and an unfiltered table does not create partitions of its published data at Subscribers. ...
  53. table cannot be used as a nested table because it does not have a many-to-one relationship with the case table. You need ...
  54. Table error: %1!s! page %2!s! (object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc unit ID %6!s! (type %7!s!)) is ...
  55. Table error: A FILESTREAM directory ID %1!s! exists for a column of object ID %2!s!, index ID %3!s!, partition ID %4!s!, ...
  56. Table error: A FILESTREAM directory ID %1!s! exists for a partition, but the corresponding partition does not exist in the ...
  57. Table error: alloc unit ID %1!s!, page %2!s! contains an incorrect page ID in its page header. The PageId in the page header ...
  58. Table error: Allocation page %1!s! has invalid %2!s! page header values. Type is %3!s!. Check type, alloc unit ID and page ...
  59. Table error: Cannot find the FILESTREAM file "%1!s!" for column ID %2!s! (column directory ID %3!s! container ID %4!s!) in ...
  60. Table error: Could not check object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) due to ...
  61. Table error: Cross object linkage. Page %1!s!->next in object ID %2!s!, index ID %3!s!, partition ID %4!s!, AU ID %5!s! (type ...
  62. Table error: Cross object linkage: Page %1!s!, slot %2!s!, in object ID %3!s!, index ID %4!s!, partition ID %5!s!, alloc ...
  63. Table error: Cross object linkage: Parent page %1!s!, slot %2!s! in object %3!s!, index %4!s!, partition %5!s!, AU %6!s! ...
  64. Table error: Extent %1!s! in object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) is beyond ...
  65. Table error: IAM chain linkage error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!). ...
  66. Table error: IAM page %1!s! for object ID %2!s!, index ID %3!s!, partition ID %4!s!, alloc unit ID %5!s! (type %6!s!) is ...
  67. Table error: Multiple IAM pages for object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) ...
  68. Table error: Object ID %1!s! has inconsistent metadata. This error cannot be repaired and prevents further processing of ...
  69. Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s! processing encountered file name "%4!s!" twice in the column ...
  70. Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s! processing encountered file name "%4!s!" twice in the column ...
  71. Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) B-tree level mismatch, ...
  72. Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) B-tree level mismatch, ...
  73. Table error: Object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!) contains an anti-matter ...
  74. Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!, row %7!s!. ...
  75. Table error: object ID %1!s!, index ID %2!s!, partition ID %3!s!, alloc unit ID %4!s! (type %5!s!), page %6!s!, row %7!s!. ...