microsoft.data.tools.schema.sql.dll

Company

Microsoft Corporation

Description
Version
13.0.3260.1
Architecture
32 bit
Threat Score
0 %
Original size
10290.9 Kb
Download size
2207.9 Kb
MD5
44fe8e3059cc0cfbc82cca55c53b3857
SHA1
f9df308cda43bfe81d9faee615611ab7774d9e3c
SHA256
01fde1d0cbac9d2b0041b4a7c7bef8d1ca97b4e0b5dde88c1fc29c1435a0845e

 Error saving report to disk: {0}

 Unknown parse error encountered.

 to reconnect to database: {0}

 to resolve deployment source.

!Disable and reenable DDL triggers

#A fatal parser error occurred: {0}.

%Unable to query collation from server

'Error Executing post-deployment script.

&

Error Executing pre-deployment script.

(Unable to identify application metadata.

(Unable to recognize event group type {0}

+Unable to obtain xslt for the given package

-An error occurred while verifying constraints

-Unable to register data-tier application: {0}

.Unable to provide access to specified content.

/An error occurred while trying to encrypt data.

0An error occurred and deployment cannot continue

2Unable to read data-tier application registration.

3The inline function {0} should start with RETURN.

8An error occurred while loading deployment contributors.

9The error code for for error message '{0}' was not found.

?Unable to import bacpac. Inner exception may have more details.

AAn error occurred while attempting to connect to the server: {0}.

CAn error occurred while moving the file. Check the inner exception.

CError the database type '{0}' is not understood by the data reader.

DAn error was received from SQL Server while attempting to reverse engineer elements of type {0}: {1}

Do not drop error messages

E10019: Unable to deserialize row from JSON provider.  File may be corrupt or in non supported format.

EAn unexpected error occurred. Contact product support for assistance.

EUnable to open a connection to the master database. The user doesn't have login access to the master.

Enable C2 audit tracing

Error Messages

Error extracting database:{0}

Error while reading the stream.

Exclude error messages

Extended T-SQL Verification encoutered a fatal error and cannot continue.  If this problem persists, extended verification can be disabled in the project settings.

FBatch Command during reverse engineer failed with Error Code: {0} Line Number: {1} Error Message: {2}.

GAn error occurred while adding references.  Deployment cannot continue.

Gathering error messages

J50006: Error the database type '{0}' is not understood by the data reader.

JSuppression messages cannot be saved to the XML string. Error message: {0}

JUnable to read a file from package.  Package may be corrupt. File = '{0}'.

MThe XML string for a suppression message cannot be parsed. Error message: {0}

OThe path for the XML suppression file cannot be constructed. Error message: {0}

OThe suppression message could not be read from the XML file. Error message: {0}

PAn error occurred during deployment plan generation. Deployment cannot continue.

PAn error occurred while attempting to reverse engineer elements of type {0}: {1}

PAn unexpected internal error has blocked the ability to validate database drift.

Q{0} contains a statement that is not supported on {1}. The specific error is: {2}

SA {0} contains a statement that is not supported on {1}. The specific error is: {2}

The DAC Framework is unable to deploy a DAC package containing a data value of type DECIMAL or NUMERIC within a sql_variant column that has precision greater than 28.

The column {0} on table {1} must be added, but the column has no default value and does not allow NULL values. If the table contains data, the ALTER script will not work. To avoid this issue you must either: add a default value to the column, mark it as allowing NULL values, or enable the generation of smart-defaults as a deployment option.

The column {0} on table {1} must be changed from NULL to NOT NULL. If the table contains data, the ALTER script may not work. To avoid this issue, you must add values to this column for all rows or mark it as allowing NULL values, or enable the generation of smart-defaults as a deployment option.

The database being updated has objects that are in an error state.  Errors could occur due to undetected blocking dependencies.

To re-enable the script after enabling SQLCMD mode, execute the following:

Unable to connect to master or target server '{0}'. You must have a user with the same password in master or target server '{0}'.

Unable to import database.

Unable to parse collation {0}

Unable to proceed with DAC operations on the target instance because it does not support DACs. Specify another instance, or upgrade to a version that supports DACs.

Unable to query current user.

Unable to recognize event {0}

WWhen false, Error Messages in the target database that are not defined in the source will be dropped during deployment.

When true, Error Messages will be excluded from consideration during deployment. No Error Messages will be added, modified or dropped.

Your permissions to see all objects in the server or database could not be verified.  The original error was:

ZA conversion error occurred while converting a column from sqlType '{0}' to clrType '{1}'.

ZUnable to validate the number of rows that were imported to table {0} ({1} rows expected).

An error occurred while adding references for the target model.  Deployment cannot continue.

^Unable to deserialize row from JSON provider.  File may be corrupt or in non supported format.

Last update: 18/08/2025