FIX: Error message when you use a table-valued function (TVF) together with the CROSS APPLY operator in a query in SQL Server 2005: "There is insufficient system memory to run this query"
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Consider the following scenario. In Microsoft SQL Server 2005, you use a table-valued function (TVF) together with the CROSS APPLY operator in a query. You use a Transact-SQL TVF or a common language runtime (CLR) TVF. In this scenario, you may receive the following error message:
Msg 701, Level 17, State 123, Line 2
There is insufficient system memory to run this query.
Typically, you experience this problem if the table on the left side of the query produces lots of rows.
This problem occurs because the memory that is used for the parameters of the TVF is not released until the query has finished running. When you use a TVF together with the CROSS APPLY operator, the TVF may be called many times even when the query is run one time. When the TVF is called many times, lots of memory is consumed.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
Microsoft SQL Server 2005 Service Pack 1 (SP1)
For information about how to obtain SQL Server 2005 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
Restart information
You do not have to restart the computer after you apply the hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Description of the standard terminology that is used to describe Microsoft software updates
Steps to reproduce the problem
To reproduce the problem faster, configure SQL Server 2005 to use a small amount of memory. To do this, run the following script in SQL Server 2005.
-- Enable advanced options
USE master
EXEC sp_configure 'show advanced options', 1
go
RECONFIGURE WITH OVERRIDE
go
-- Set the maximum amount of memory to 300 MB
exec sp_configure 'max server memory', 300
go
reconfigure with override
go
dbcc freeproccache
go
To stop and then restart the SQL Server service, run the following commands at a command prompt:
net stop mssqlserver net start mssqlserver
In SQL Server 2005, run the following Transact-SQL statements.
drop table t
go
create table t (c1 int, c2 int, c3 int, c4 int, c5 int, c6 int, c7 int, c8 int, c9 int, c10 int)
go
drop function fn_test
go
create function fn_test (@p1 int, @p2 int, @p3 int, @p4 int, @p5 int, @p6 int, @p7 int, @p8 int, @p9 int, @p10 int)
returns @t table (c1 nvarchar(4) )
with schemabinding
as
begin
insert into @t values (N'abcd')
return
end
go
drop function fn_scalar
go
create function fn_scalar (@p1 int, @p2 int, @p3 int, @p4 int, @p5 int, @p6 int, @p7 int, @p8 int, @p9 int, @p10 int)
returns nvarchar(4)
with schemabinding
as
begin
declare @s nvarchar (4)
set @s = N'abcd'
return @s
end
go
drop function fn_test2
go
create function fn_test2 ()
returns @t table (c1 nvarchar(4) )
with schemabinding
as
begin
insert into @t values (N'abcd')
return
end
go
set nocount on
go
declare @i int
set @i = 0
while @i < 5000000
begin
insert into t values (@i, @i, @i, @i, @i, @i, @i, @i, @i, @i)
set @i = @i + 1
end
go
-- The following select query returns the 701 error if you restrict max server memory to 300 MB
select count(*) from t cross apply dbo.fn_test(c1,c2,c3,c4,c5,c6,c7,c8,c9,c10)
Note These steps use a Transact-SQL TVF. This problem also occurs when you use a CLR TVF.
Back to the top
