Msg 1813 says CREATE DATABASE is aborted when you attach a database with a corrupt log. My step by step fix rebuilds the log and needs a server restart.
SQL SERVER – Fix : Error Msg 4214 – Error Msg 3013 – BACKUP LOG cannot be performed because there is no current database backup
Fix the SQL Server error Msg 4214 and Msg 3013, where BACKUP LOG fails because no current database backup exists. Here is why it happens.
SQL SERVER – 2005 – SSMS – View/Send Query Results to Text/Grid/Files
Three ways to send query results to text, grid or file in SSMS: the shortcuts CTRL+T, CTRL+D and CTRL+SHIFT+F, the toolbar, or the menu bar.
SQL SERVER – FIX : ERROR Msg 244, Level 16, State 1 – FIX : ERROR Msg 245, Level 16, State 1
Msg 244 and Msg 245 come from converting a value to an incompatible data type, often with CAST or ISNULL. Examples of both, and why ISNULL casts to the first type.
SQL SERVER – FIX : Error : msg 8115, Level 16, State 2, Line 2 – Arithmetic overflow error converting expression to data type
Msg 8115, arithmetic overflow error, comes when a value is too big for its column, like 111111 in a TINYINT. Check the value or widen the column definition.
SQL SERVER – Fix : Error : Server: Msg 131, Level 15, State 3, Line 1 The size () given to the type ‘varchar’ exceeds the maximum allowed for any data type (8000)
Msg 131 says the size given to varchar exceeds the maximum allowed (8000). Use VARCHAR(8000), or VARCHAR(MAX) in SQL Server 2005 as the TEXT replacement.
SQL SERVER – Fix : Error 8629 The query processor could not produce a query plan from the optimizer because a query cannot update a text, ntext, or image column and a clustering key at the same time.
Error 8629 appears when one UPDATE changes a text or image column and a clustering key together. Here is why SQL Server blocks it and a fix.