SQL Server: Fix Msg 8630, Level 16, State 1, Line 1 – Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x80040e19).

This is going to be a quick reference for people encountering this error and to do the fix more than a blog post but I do show a small trick on how to do an UPDATE in chunks 😉 The Error: I ran into this error with (Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) - 11.0.7462.6 … Continue reading SQL Server: Fix Msg 8630, Level 16, State 1, Line 1 – Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x80040e19).

SQL Server: Fix – Msg 1204, Level 19, State 4 – The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time…

This is an error that does not happen often. In fact, I came across this for the first time when one of my co-workers Inken HOEIJMANS asked me about this. With her permission, I am reproducing her code solution here. Thank you Inken! She was trying to run a MERGE statement using a large source … Continue reading SQL Server: Fix – Msg 1204, Level 19, State 4 – The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time…

SQL Server: Fix: Transaction (Process ID) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction

I have a nightly SQL Agent job that aggregates backup information from system views to power a Power BI dashboard that the DBA's review periodically for database backup failures. It is actually a PowerShell job that runs every night in parallel to collect the data from hundreds of instances (both SQL Server and Oracle). As … Continue reading SQL Server: Fix: Transaction (Process ID) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction

SQL Server: Delete In Chunks To Avoid Log Growth

Today, I had to perform a DELETE that happened to remove quite a bit of data. This caused two issues for me Log file growth which fills up the Transaction Log of the DB TempDB was getting full To avoid both problems I deleted in chunks. OPTION #1: DELETEing in Chunks is easier than you … Continue reading SQL Server: Delete In Chunks To Avoid Log Growth

SQL Server: Time To Switch Schema Of All Objects Away From “dbo”

What are Schemas for? All of you are familiar with the default and built-in schema "dbo". When you create an object without a schema, "dbo" becomes the schema for the object. Generally, it is NOT considered a good practice from a manageability or security perspective to have everything owned by "dbo". The alternative is to … Continue reading SQL Server: Time To Switch Schema Of All Objects Away From “dbo”