A short introduction to partitioning in SQL Server 2005: very large tables and indexes are split into smaller parts by ranges, across filegroups, for performance.
SQL SERVER – Solution – Log File Very Large – Log Full
Is your log file too big, or is the log full? Fix it in three steps: back up the log file, truncate it, then shrink it. I link my two detailed posts too.
SQL SERVER – FIX : Error 3154: The backup set holds a backup of a database other than the existing database
Error 3154 says the backup set holds a backup of a database other than the existing database. Use WITH REPLACE in RESTORE, or drop the old database first.
SQL SERVER – Fix : Error : Msg 3117, Level 16, State 4 The log or differential backup cannot be restored because no files are ready to rollforward
Msg 3117 means the log or differential backup cannot be restored because no files are ready to rollforward. Restore the full backup WITH NORECOVERY first.
SQL SERVER – FIX : Error : msg 2540 – The system cannot self repair this error
Msg 2540 means the system cannot self repair this error, usually corrupt metadata or system files. My fix order: restore the backup, DBCC repair, check hardware.
SQL SERVER – T-SQL Script to Attach and Detach Database
Move a database to a new server in three steps: Detach Database with sp_detach_db, copy the data and log files, then attach it again with CREATE DATABASE.
SQL SERVER – 2005 – SSMS – Enable Autogrowth Database Property
How to enable Autogrowth for a database in SSMS: open the database Properties, go to Files and click the small button in the Autogrowth column.