October 30, 2009 at 11:07 am
Hi,
We have SQL Server 2005 Developer edition x86 with SP3 . We have 4 GB Memory and Max memory is set to 3.5 GB. I ran a query which delete 8000 rows and i got the following dump in error log. The default file growth for database is set 10% increment and the database is in SIMPLE recovery model & still the log file increasing rapidly. I noticed at the end its saying insuffieient memory "There is insufficient system memory to run this query". I wondering 4 GB of memory is not enough to run such kind of a query? please advice me to take proper steps to avoid this memory issue.
Memory Manager
VM Reserved = 1933576 KB
VM Committed = 1909688 KB
AWE Allocated = 0 KB
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB 2009-10-29 23:21:50.69 spid75
Memory node Id = 0
VM Reserved = 1929416 KB
VM Committed = 1905680 KB
AWE Allocated = 0 KB
SinglePage Allocator = 69080 KB
MultiPage Allocator = 235040 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLGENERAL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 1968 KB
MultiPage Allocator = 1640 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLBUFFERPOOL (Total)
VM Reserved = 1654624 KB
VM Committed = 1654624 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 0 KB
MultiPage Allocator = 400 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLQUERYEXEC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 232 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLOPTIMIZER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 1768 KB
MultiPage Allocator = 72 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLUTILITIES (Total)
VM Reserved = 360 KB
VM Committed = 360 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 128 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLSTORENG (Total)
VM Reserved = 6592 KB
VM Committed = 6592 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 1968 KB
MultiPage Allocator = 328 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLCONNECTIONPOOL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 392 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLCLR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLSERVICEBROKER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 80 KB
MultiPage Allocator = 192 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLHTTP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SNI (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 56 KB
MultiPage Allocator = 16 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_FULLTEXT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLXP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_QSRANGEPREFETCH (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 24 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_BHF (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 64 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLQERESERVATIONS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 4176 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_HOST (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 64 KB
MultiPage Allocator = 64 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SOSNODE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 5544 KB
MultiPage Allocator = 7776 KB 2009-10-29 23:21:50.69 spid75
MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 24 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_OBJCP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 208 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_SQLCP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 3024 KB
MultiPage Allocator = 224360 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_PHDR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_XPROC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 24 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_TEMPTABLES (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 40 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_NOTIF (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_VIEWDEFINITIONS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_XMLDBTYPE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_XMLDBELEMENT (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_XMLDBATTRIBUTE (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_STACKFRAMES (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 0 KB
MultiPage Allocator = 8 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERTBLACS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 136 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERKEK (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERDSH (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERUSERCERTLOOKUP (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERRSB (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERREADONLY (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 32 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_BROKERTO (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 8 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_EVENTS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
CACHESTORE_SYSTEMROWSET (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 136 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
USERSTORE_SCHEMAMGR (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 6104 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
USERSTORE_DBMETADATA (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 400 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
USERSTORE_TOKENPERM (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 128 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
USERSTORE_OBJPERM (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 312 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
USERSTORE_SXC (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 16 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
OBJECTSTORE_LBSS (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 40 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
OBJECTSTORE_SNI_PACKET (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 712 KB
MultiPage Allocator = 48 KB 2009-10-29 23:21:50.69 spid75
OBJECTSTORE_SERVICE_BROKER (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 256 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75
OBJECTSTORE_LOCK_MANAGER (Total)
VM Reserved = 8192 KB
VM Committed = 8192 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 44992 KB
MultiPage Allocator = 0 KB 2009-10-29 23:21:50.69 spid75 Buffer Distribution: Stolen=1685 Free=30941 Cached=7084
Database (clean)=160986 Database (dirty)=4101
I/O=0, Latched=3 2009-10-29 23:21:50.69 spid75 Buffer Counts: Committed=204800 Target=204800 Hashed=165093
Internal Reservation=40960 External Reservation=391
Stolen Potential=185403
Min Free=64 Visible=204800
Available Paging File=3467722752
2009-10-29 23:21:50.69 spid75 Procedure Cache: TotalProcs=5 TotalPages=28453 InUsePages=377 2009-10-29 23:21:50.69 spid75 Process physical/virtual memory pressure: 0/0 System physical memory pressure: 0 2009-10-29 23:21:50.69 spid75 Global Memory Objects:
Resource=232
Locks=5627
SE Schema Mgr=762
SQLCache=41
Replication=2
ServerGlobal=26
XPGlobal=2
Xact=27
SETLS=2
DatasetMemObjs=4
SubpDescPmos=2
SortTables=2 2009-10-29 23:21:50.69 spid75 Query Memory Objects: Grants=2 Waiting=0 Maximum=136017 Available=135495 Limit=146205 2009-10-29 23:21:50.69 spid75 Query Memory Objects: Next Request=0 Waiting For=0 Cost=0 Timeout=0 Wait Time=0 Last Target=153900 2009-10-29 23:21:50.69 spid75 Small Query Memory Objects: Grants=0 Waiting=0 Maximum=7151 Available=7151 Limit=7151 2009-10-29 23:21:50.69 spid75
Optimization Queue
Overall Memory = 1344798720 Target Memory = 1294409728 Last Notification = GROW Timeout = 6 Early Termination Factor = 5
2009-10-29 23:21:50.69 spid75
Small Gateway
Configured Units = 8 Available Units = 8 Acquires = 0
Waiters = 0 Threshold Factor = 250000 Threshold = 250000
2009-10-29 23:21:50.69 spid75
Medium Gateway
Configured Units = 2 Available Units = 2 Acquires = 0
Waiters = 0 Threshold Factor = 12 Threshold = -1
2009-10-29 23:21:50.69 spid75
Big Gateway
Configured Units = 1 Available Units = 1 Acquires = 0
Waiters = 0 Threshold Factor = 8 Threshold = -1
2009-10-29 23:21:50.69 spid75
MEMORYBROKER_FOR_CACHE
Allocations = 7088
Rate = -45863
Target Allocations = 156789
Future Allocations = 0
Last Notification = GROW 2009-10-29 23:21:50.69 spid75
MEMORYBROKER_FOR_STEAL
Allocations = 1547
Rate = -327
Target Allocations = 158009
Future Allocations = 0
Last Notification = GROW 2009-10-29 23:21:50.69 spid75
MEMORYBROKER_FOR_RESERVE
Allocations = 522
Rate = 0
Target Allocations = 164160
Future Allocations = 36551
Last Notification = GROW 2009-10-29 23:21:50.70 spid75 Error: 701, Severity: 17, State: 123.
2009-10-29 23:21:50.70 spid75 There is insufficient system memory to run this query.
2009-10-29 23:27:56.45 spid79 Autogrow of file 'Mydb_log' in database 'Mydbtook 64375 milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
2009-10-30 00:00:37.90 spid14s This instance of SQL Server has been using a process ID of 1720 since 10/24/2009 1:14:26 PM (local) 10/24/2009 8:14:26 PM (UTC). This is an informational message only; no user action is required.
November 1, 2009 at 2:33 am
could you plz give me some inputs..
many thanks
November 1, 2009 at 3:05 am
Hi
We had (have) an equal problem.
* Ensure you installed all service packs
* Maybe decrease the maximal memory for SQL Server.
* Check for count of concurrent activities
* Check tempdb space
Check this thread:
There is insufficient system memory to run this query
Greets
Flo
November 1, 2009 at 10:19 am
Okay, if I have read this correctly you have two issues you want help with:
1) Transaction Log is growing when performing a delete operation
2) Memory issues when running same delete
For the first issue - that is normal. All transactions are stored in the transaction log regardless of the recovery model. The transaction log will grow as large as it needs to for the transactions being run.
For the second issue - SQL Server cannot use more than 2GB of memory on x86 systems unless the following are true:
The /3GB switch is set in the boot.ini - if this is set, the OS is limited to 1GB and applications can use up to 3GB of memory.
Or, the system has more than 4GB of memory available and the following are true:
1) /PAE switch is set in the boot.ini
2) AWE is turned on in SQL Server
Since you don't have more than 4GB of memory on the machine - you cannot use /PAE and AWE to increase the available memory to SQL Server. You can only use the /3GB switch.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 2, 2009 at 8:46 am
If the log growth is set to 10%, you might try changing this to a certain number of MB instead.
November 2, 2009 at 8:48 am
Sorry, misread your question. I was thinking space issues instead of memory. I'm not sure if changing from the % to MB will help with memory or not.
November 2, 2009 at 11:08 pm
By right even you delete 800,000 records shouldn't cause problems.
It's not about 2G or 4G memory in your machine,
Can you please post that query?
November 3, 2009 at 12:13 am
john jin (11/2/2009)
By right even you delete 800,000 records shouldn't cause problems.It's not about 2G or 4G memory in your machine,
Can you please post that query?
Mamta,
Adding to this. How are you deleting all your 8,000 rows? Are you deleting them in one go or in chunks?
If former try deleting the rows in the form small chunks this will resolve some space issues and also set your Auto Growth in terms of MB rather than in %'age. Probably SQL server has been using the memory just to do this operation and hung there.
Thanks,
November 4, 2009 at 10:08 am
I just had a similar issue on a brand-new 16-processor server with 32Gb of RAM. The pagefile was too small and incorrectly configured. Maybe this will help: http://support.microsoft.com/kb/237740
The improvement was so great we are looking at dozens of our older servers to make the same changes.
November 5, 2009 at 10:04 am
UAMCRay (11/4/2009)
I just had a similar issue on a brand-new 16-processor server with 32Gb of RAM. The pagefile was too small and incorrectly configured. Maybe this will help: http://support.microsoft.com/kb/237740The improvement was so great we are looking at dozens of our older servers to make the same changes.
You shouldn't be paging when you have 32GB of RAM. What are the memory settings you have (and do you have lock pages in memory enabled)?
November 5, 2009 at 10:18 am
Why would you not page because you had 32 GB of RAM?
November 5, 2009 at 10:30 am
andy russell (11/5/2009)
Why would you not page because you had 32 GB of RAM?
SQL Server should not be paging at all - if it is, you have problems that need to be addressed. If the server is not a dedicated server, the page file will be used by the other applications and not SQL Server.
Doesn't matter how much memory is available.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 5, 2009 at 10:34 am
Jeffrey Williams-493691 (11/5/2009)
andy russell (11/5/2009)
Why would you not page because you had 32 GB of RAM?SQL Server should not be paging at all - if it is, you have problems that need to be addressed. If the server is not a dedicated server, the page file will be used by the other applications and not SQL Server.
Doesn't matter how much memory is available.
The max memory setting for SQL is critical so that you leave enough space for the OS to work without getting choked (usually the largest cause of paging). Additional to this, if you don't have pages locked in memory set then the OS can page out the SQL Server process.
November 5, 2009 at 10:47 am
Nick, I'd like to understand better why you feel there shouldn't be paging with 32Gb RAM. You've made me curious. My server initially had only a 2Gb pagefile and 10,000 individual inserts took 90-120sec. 15,000 inserts got "insufficient memory". After increasing the pagefile based on the MS link in my previous post, 20,000 inserts took a mere 8sec!
Right now the server shows 27Gb pagefile usage, with 8Gb free RAM. The server has no users because it is a failover box, but is a Repl Subscriber to multiple production boxes. (Merge for two Db's, and Transactional for another VLDB.)
I seldom post because I have no need - I just enjoy reading others posts. But you seem to have experience so maybe I'll learn something new from you. Thx
November 5, 2009 at 10:53 am
What are your min/max settings for SQL? (I'm guessing that you are running the x64 versions of the OS and SQL and so PAE/AWE/3GB are not factors)
Viewing 15 posts - 1 through 15 (of 23 total)
You must be logged in to reply to this topic. Login to reply