System errors.

Troubleshooting SQL Server

Troubleshooting

System errors.

Two system errors can appear in the Save Incomplete dialog box when you exceed Microsoft® SQL Server limitations that are not controlled by SQL Server Enterprise Manager.

ODBC error text

[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 transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.

Explanation

This error occurs because there is insufficient log space to complete the transaction.

Action
  • 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 bulk copying (bcp utility).
ODBC error text

[Microsoft][ODBC SQL Server Driver]Timeout expired.

Explanation

The timeout can occur when you're updating the database with any Transact-SQL changes.

Action
  • 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.

See Also

ALTER DATABASE

Physical Database Files and Filegroups

remote query timeout Option

Saving a Change Script

sp_configure