Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  SQL Server:SQL Server Enterprise Manager Error Messages  [ 202 result(s) ]
MICROSOFT 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Data exists in table '[table name]', database '[database name]', that violates CHECK constraint '[constraint name]' being added. ALTER command has been MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to create constraint. See previous errors. Unable to add constraint. Appears when a new constraint has failed on existing data or your constraint expression contains an error. Compare the ODBC error text that appears in the Save Incomplete dialog box with the error text shown below to determine the appropriate solution. Existing data does not match the check constraint.
• Change the data (for example, by using SQL Server Enterprise Manager) to match the constraint. • Clear the Check existing data on creation check box in the Tables property page for the check constraint in question. • Change the constraint expression in the Tables property page for the check constraint in question.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Can't allocate space for object 'Syslogs' in database 'Guest' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the tr MICROSOFT
This error occurs because there is insufficient log space to complete the transaction.
• Follow the recommendation in the message and delete the transaction log. (Typically this action will not entirely solve the problem.) • Increase the size of the database to accommodate the change. With large databases, changes that require the recreation of tables (for example, changing a column data type or size) may not be possible using SQL Server Enterprise Manager. You may need to use methods of transferring data that don't require transactions, such as BCP(BulkCopyProgram).
SQL Server Enterprise Manager Error Messages
Comments
 
  -  Column with (+) operator does not reference a valid table.  MICROSOFT
The operator you've used in the query column must reference a valid table. SQL Server Enterprise Manager cannot validate the table currently referenced.
Verify that the table exists in the database and that SQL Server Enterprise Manager has access to it.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  Unable to create index. Appears when a new index has failed on existing data.  MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]Create unique index aborted on duplicate key. Primary key is '[primary key data]' [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to create constraint. See previous errors. A unique index was created in the Indexes/Keys property page but duplicate data exists in the database. The value after the phrase "Primary key is" is the first duplicate value that Microsoft SQL Server found as it created the index.
• Remove duplicate data from the database (for example, by using SQL Server Enterprise Manager). • Change the option in the Indexes/Keys property page to allow duplicate rows in the index.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column '[column name]' specified in constraint definition.  MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to create constraint. See previous errors. • The text value in the check constraint expression on the Tables property page is not enclosed in single quotation marks ('). • A column that participates in the check constraint has been renamed. For example, if the original constraint had the expression (cityname = 'Paris') and you renamed the column to city, you would see the same error except that 'cityname' would be the invalid column shown in the error message.
Correct the expression and save the table.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  Unsupported SQL.  MICROSOFT
There is an error in the syntax of your query. SQL Server Enterprise Manager has attempted to locate the source of the error.
Review your query syntax and correct the error before running your query.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  SQL statement could not be parsed.  MICROSOFT
There is an error in the syntax of your query. SQL Server Enterprise Manager has attempted to locate the source of the error.
Review your query syntax and correct the error before running your query.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  Unable to modify table. Appears when a new constraint has failed on existing data. Compare the ODBC error text that appears in the Save Incomplete dialog box with the two ODBC errors shown below to MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]The column [column name] in table Tmp_ [table name] may not be null. A new database column has been added that doesn't allow null values and doesn't provide a default value. The table name in question appears after "Tmp_".
Change the column properties. Either select the Allow Nulls property or type a Default Value setting. ODBC error text [Microsoft][ODBC SQL Server Driver][SQL Server]Attempt to insert the value NULL into column '[column name]', table '[database name] TMP_ [table name]'; column does not allow nulls. INSERT fails. [Microsoft][ODBC SQL Server Driver][SQL Server]Command has been aborted. The Allow Nulls property on an existing database column has been cleared, but the column has existing null values in it. The table name in question appears after "TMP_". Go to the column and select the Allow Nulls property.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  Appropriate SQL cannot be generated.  MICROSOFT
SQL Server Enterprise Manager requires that you follow specific rules when designing queries. This error may appear if you have used the diagram or grid pane to create a query that cannot be expressed in a Transact-SQL statement.
Verify the query options you have selected.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  [Microsoft][ODBC SQL Server Driver]Timeout expired.  MICROSOFT
The timeout can occur when you're updating the database with any Transact-SQL changes.
• Try again later to save the diagram or selected tables. • Save a change script and apply it to the database at a later time. • Increase the SQL Query Time-out value and try to save the diagram or selected tables again. To increase the SQL Query Time-out value 1. From the Tools menu, choose Options. 2. In the left pane, click Data Tools, and then click Data View. 3. Type a new value in the SQL query time-out box.
SQL Server Enterprise Manager Error Messages
Comments
 
 

 
SQL Server Enterprise Manager Error Messages (201)
SQL Server System Error Messages  (1)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next