Author
SQL Server Error 605
Error: SQL Error 601. Could not continue scan with NOLOCK due to data movement. SQL Sever Logs: Message Error: 605, Severity: 21, State: 3. Message Attempt to fetch logical page (13:2769683) in database 7 failed. It belongs to allocation unit 72057594291945472 not to 72057594369933312. Explanation This error generally signifies page or allocation corruption in the... » read more
SQL Server blocked access to procedure sys.xp_cmdshell
Error: Fix: Sources:
SELECT failed because the following SET options have incorrect settings: ‘ANSI_WARNINGS’
Error: Msg 50000, Level 16, State 1, Procedure uspXXXXX, Line 581 [Batch Start Line 2] uspXXXXX | SQL Error 1934 at line 505. SELECT failed because the following SET options have incorrect settings: ‘ANSI_WARNINGS’. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query... » read more
DBCC SHRINKFILE
Shrinks the current database’s specified data or log file size. You can use it to move data from one file to other files in the same filegroup, which empties the file and allows for its database removal. You can shrink a file to less than its size at creation, resetting the minimum file size to... » read more
Shrink Database Log Files in Always On
Need to create full database backup and transaction log backup on primary server to shrink the log file. The replica server log file will automatically shrink. Might need to backup the transaction log a couple of times and wait a while before the log file will automatically shrink. Sources: https://dba.stackexchange.com/questions/114787/shrink-database-in-always-on-availability https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql?view=sql-server-ver15
Log cannot be shrunk until all secondaries have move past the point where the log was added
Error: The log for database ‘xxxxx’ cannot be shrunk until all secondaries have moved past the point where the log was added. Fix: Problem with Always On. One of the secondary was not getting synchronized. Delete the AG and the thing came back to normal. But in production, if you can’t afford to delete and... » read more
Cannot shrink log file because the logical log file located at the end of the file is in use
Error: Cannot shrink log file XX (XXXXX_LOG) because the logical log file located at the end of the file is in use Always On and Log File You will get this error trying to shrink the log files if the database belongs to Always On. Fix: Preform a full database and log backup. The log... » read more