New Objects, Columns, and Messages in SQL Server 2019 CTP 2.3

Sure, there’s official documentation on what’s new in SQL Server 2019, but Microsoft’s notorious for slipping undocumented stuff in. Sometimes these new features become officially documented in subsequent preview builds, like CTP 2.2’s initial plumbing for Accelerated Database Recovery that went officially public in CTP 2.3, and other times they never see the light of day, like Snapshot Materialized Views.

To unearth this stuff, I use this linked server technique, joining between old & new versions of the product, and query the system tables for changes. Here’s what’s new in SQL Server 2019 CTP 2.3:

New objects in CTP 2.3:

New objects in SQL Server 2019 CTP 2.3

New columns in existing objects in master:

New columns in existing objects

New error messages:

  • 3644: Prefaulter task failed for file %ls with error %d.
  • 3868: Failed to start tempdb in Hekaton mode. Continuing tempdb startup in SQL mode.
  • 5153: OVERFLOW is not supported in Alter Database modify statement in Sql DW back door.
  • 5346: DATAFILETYPE option cannot be provided without WITH schema.
  • 5347: USE_TYPE_DEFAULT option cannot be provided without WITH schema.
  • 7439: Fail to read required information about %S_MSG pool %S_MSG.
  • 7440: Remote execution status: “%ls” .
  • 8677: Cannot create the clustered index ‘%.*ls’ on view ‘%.*ls’ because it does not aggregate results. Consider changing the view definition.
  • 8705: A DML statement encountered a missing entry in index ID %d of table ID %d, in the database ‘%.*ls’ due to an interaction with another transaction. If you continue to see this error, consider using Repeatable Read or higher isolation level.
  • 13784: Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same sensitivity classification in tables ‘%.*ls’ and ‘%.*ls’.
  • 13785: System-versioned table schema modification failed because column ‘%.*ls’ does not have the same sensitivity classification in tables ‘%.*ls’ and ‘%.*ls’.
  • 13810: Column ‘%ls’ is of type ‘%ls’ which is not supported with file format ‘%ls’.
  • 13962: The alias or identifier ‘%.*ls’ is not the last node in a shortest path pattern. Only the last node in the path can be used with LAST_NODE().
  • 13963: Node table name or alias ‘%.*s’ refers to a derived table and cannot be used by the LAST_NODE function.
  • 13964: The two aliases ‘%.*s’ and ‘%.*s’ refer to different underlying objects in a LAST_NODE equality expression.
  • 13965: The table name or alias ‘%.*s’ must use the LAST_NODE function to reference the last node in a shortest_path expression.
  • 14173: Replication-%s: agent initialization failed. %s
  • 15807: Provided statement is not supported.
  • 15808: Schema cannot be determined from data files for file format ‘%.*ls’. Please use WITH clause of OPENROWSET to define schema.
  • 15809: No files found matching the name pattern(s) ‘%ls’.
  • 15810: Error trying to retrieve schema from the data file ‘%.*ls’. Make sure the file matches the ‘%.*ls’ format.
  • 15811: No columns found in the data file ‘%ls’.
  • 15812: Number of columns in the data file ‘%ls’ exceeds the maximum of %d.
  • 15813: Error reading external file: ‘%s’.
  • 15814: Column ‘%s’ of type ‘%s’ is not compatible with external data type ‘%s’.
  • 15815: External data type ‘%s’ is currently not supported.
  • 16115: Sensitivity classifications cannot be added to a history table directly.
  • 17206: File %ls, file number %d is successfully mapped.
  • 17209: File %ls, file number %d: File size is not configured multiple of the minimum size of a large page.
  • 19515: Database partner is missing during database restart.
  • 22301: DW FIDO mode is not enabled.
  • 22302: DW FIDO transaction context not found.
  • 22303: Updates are not allowed from a FIDO Scan transaction.
  • 22304: Reading or Writing to database files is not supported in FIDO DBs.
  • 22305: A NULL or unexpected value was retured by a FIDO ODBC call.
  • 22306: Only CCI tables are allowed in Fido mode.
  • 22307: Alter statements are only allowed from a FIDO Alter transaction.
  • 22308: Fido thread failed to acquire a lock.
  • 22309: Fido Cache DB not found.
  • 22310: Failed to create Fido DB with key: [%.*ls].
  • 22311: Generic Fido out of bounds error.
  • 22312: Failed to remap rowset with Id ‘%I64d’ on a Fido DB.
  • 22313: Failed to find Fido columns in rowset with Id ‘%I64d’.
  • 22314: Fido invalid ODBC connection.
  • 22315: Invalid Fido Transaction type %d.
  • 22316: Failed to acquire CSI Cache lock.
  • 22317: Fido invalid ODBC column.
  • 22318: Fido ODBC transaction failed a commit.
  • 22319: An invalid access to a Fido DB Rowset (DbId ‘%lu’, RowsetId ‘%I64d) was performed.
  • 22320: Fido DB (DbId:’%lu’, Name: ‘%.*ls’) can only be used under a Fido session context.
  • 22321: Fido DB (DbId:’%lu’, Name: ‘%.*ls’) cannot be used. Only DbId: ‘%lu’ is allowed.
  • 27803: Message reported from (%.*s) device on device Id (%I64d), code : %d, message : %.*s .
  • 27804: Query failed on HPC device Id (%I64d), with error code %d .
  • 33554: Encountered error 0x%08lx while waiting for encryption scan completion consensus. See the errorlog for details.
  • 33555: Unable to find the user-specified certificate [Cert Hash “%hs”] in the certificate store of the local computer or current user. Please verify if the certificate exists.
  • 33556: Invalid character in the thumbprint [Cert Hash “%hs”]. Please provide a certificate with valid thumbprint.
  • 33557: Invalid thumbprint length [Cert Hash “%hs”]. Please provide a certificate with valid thumbprint.
  • 33558: Encryption scan can not be resumed because no encryption scan is in progress.
  • 33559: Specified workload group does not exist. Retry with a valid workload group.
  • 33560: TDE Encryption scan suspended for database id [%d]. Will not auto resume. Please resume manually to restart.
  • 33561: Encryption scan can not be suspended because no encryption scan is in progress.
  • 33562: TDE encryption scan state cannot be updated for database id [%d].
  • 35513: compute
  • 37201: An instance pool could not be found with name ‘%.*ls’.
  • 37202: “An instance pool with name ‘%.*ls’ is busy with another ongoing operation.
  • 37203: An instance pool with name ‘%.*ls’ is not empty.
  • 37204: An instance pool with name ‘%.*ls’ does not have enough vCore capacity for given request.
  • 39112: Duplicate file specification supplied for platform ‘%.*ls’.
  • 39113: Number of file specifications exceeds the maximum of %d.
  • 40977: ‘%.*ls’ is not a supported timezone.
  • 41670: Cannot retrieve tempdb remote file lease order id.
  • 41871: Failed to recreate XTP non-durable tables during recovery of the database ‘%.*ls’.
  • 41935: Managed Instance has reached the total capacity of underlying Azure storage account. Azure Premium Storage account is limited to 35TB of allocated space.
  • 43037: An internal error was encountered when processing the restore request. This request has been assigned a tracing ID of ‘%.*ls’. Message is ‘%.*ls’, and details are ‘%.*ls’. Provide this tracing ID/Message/Details to customer support when you need assistance.
  • 45433: The specified family %ls is not consistent with the specified SKU %ls.
  • 45434: The point in time ‘%.*ls’ for restoration can’t be later than now.
  • 45435: The operation could not be completed. The requested sku update would cause the master server to have a larger max_connections value than its replica(s).
  • 45436: The operation could not be completed. The requested storage update would cause the master server to have a larger storage size than its replica(s).
  • 45437: The operation could not be completed. Replication is not enabled for the server.
  • 45438: The timezone cannot be changed on Managed Instance.
  • 45439: Cannot create a Managed Instance with timezone ‘%.*ls’. Please use timezone ‘UTC’ instead.
  • 45440: Cannot create a Managed Instance as there are not enough available ip addresses in the selected subnet.
  • 45441: Elastic server restore verification is not supported.
  • 47131: Create or Join availability group ‘%.*ls’ has failed because there is a system availability group. Remove system availability group, then retry the operation.
  • 49410: Change tracking is currently not supported in this version of SQL Server.
  • 49510: Managed instance is busy with another operation. Please try your operation later.
  • 49511: Unable to set one or more trace flags. Unsupported trace flag(s): %ls%ls%ls.
  • 49512: Session level trace flags are not supported on managed instance.
  • 49972: Cannot add tempdb remote file to local tempdb filegroup in transition to primary.
  • 49973: Cannot remove tempdb remote file to local tempdb filegroup in transition to primary.

No new rows in sys.configurations and no new Perfmon counters. Happy spelunking!

Previous Post
SQL Server 2019 Result Set Caching?
Next Post
[Video] Demoing SQL Server 2019’s new Accelerated Database Recovery

6 Comments. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu
{"cart_token":"","hash":"","cart_data":""}