![The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’](https://www.sqlnethub.com/wp-content/uploads/2017/09/error-640x300.jpg "The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’")
When using In-Memory OLTP in SQL Server 2014, under certain conditions you might get the below error message: The transaction log for database ‘[database_name]’ is full due to ‘XTP_CHECKPOINT’ Symptoms One symptom due to the above issue, is that the transaction log of a memory-optimized table, might continue to grow,…
This article discusses how you can resolve the error message: There is insufficient system memory in resource pool ‘internal’ to run this query. Even though you might get the above error message for different occasions, one thing is for sure (after all, the message is quite self-explanatory), it has to…
I have recently experienced an issue which had to do with a third-party application that was trying to retrieve some meta information from a specific SQL Server Instance. It was actually trying to retrieve the names of all the databases contained within that instance. However it was returning the following…
A few days ago I was trying to attach some databases on a SQL Server 2005 instance. The database files were copied over the network and located on a drive on the DBMS server. Though, while I was trying to attach the databases I was getting an error message of…
At some time in the past, I set up a maintenance plan in one SQL Server instance for rapidly tuning up a set of databases with some simple tasks such as index rebuild, etc., and I got the error message: “No global profile is configured. Specify a profile name in…
Well, after a few days of actually doing nothing but sleeping and resting because of the flu, here I am back to blogging! 🙂 A very neat feature of SQL Server is the way it lets the DBA to control connections. To this end, you can explicitly control connections with…
This post’s purpose is to explain the above connectivity error and ways of resolving it. In some cases (upon “wrong” actions or network problems 🙂 we might get the following error in SQL Server: A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider,…
Well, as the error message says, whenever we have a division within a SQL query and the denominator has the value of zero (0) we get this error. The exact error we get in SQL Server is: Msg 8134, Level 16, State 1, Line [Here goes the line of the…
There are many times were we need to handle NULL and “empty” values in SQL Server.Though there is a difference between a NULL and an “empty” value. In this example we will examine the above issue. Consider the following table: CREATE TABLE [dbo].[table_A]([id] [int] NOT NULL,[name] [varchar](50) NULL,CONSTRAINT [PK_table_A] PRIMARY…
There are many times where a query may result to the following error: String or binary data would be truncated. The statement has been terminated. We will go through a simple example for explaining this behavior. Reproducing the “String or binary data would be truncated” error Creating the Sample Table Consider…
There are cases where a SQL Server database developer might get an error message similar to: “The multi part identifier could not be bound“. This happens because of the way the database developer handles table scopes within the query. Read the article below, in order to better understand this error,…
SQL Server 2008 is undoubtedly an extremely powerful Relational Database Management System. It comes with many new features that increase the database developer’s productivity and make the life of the DBA easier. In September 2008, Microsoft has published the SQL Server 2008 Feature Pack, which includes various stand-alone install packages…
