July 10, 2008 at 1:30 am
Hi dear friends and It Professionals;
We have an important and urgent problem that we have been trying to solve for a month approximately but no luck :crazy: We have an SQL Server (APP141TR) and an Oracle Server (trtplfb4) and my colleagues in the factory has made a link from SQL Server to Oracle database. They have no problems selecting or updating Oracle database even inserting into it. But there is only one insert command that does not work when the table grows bigger beyond 37.893.466 records.
INSERT INTO SFDCTEST..KORD.BESLEME_TRAN (BOBIN_NO,BES_BOBIN_NO,BES_SIRA_NO,BES_TIPI,DEGISIM_TIPI,ISLEM_SIRA_NO) VALUES('B000004260','B000004108',1,'N','R',0)
"SQL Server 2005 - Provider ran out of Memory error"
They are inserting into other tables without any problems but this one does not work after the records are increased. I have discussed this case with Microsoft Partners and they suggested that the solution should be searched on the Oracle side. What do you say? Could you assist us please?
July 10, 2008 at 6:03 am
I would first try increasing the amount of memory available for linked server drivers.
They use a portion of memory reserved by SQL Server for non-SQL processes running within SQL Server. I cannot remember what the default is for SQL 2005, but the -g startup parameter allows you to configure this memory space. Don't make it too large though, SQL reserves it, so it will take memory away from other SQL processes.
July 10, 2008 at 6:17 am
Michael Earl (7/10/2008)
I would first try increasing the amount of memory available for linked server drivers.They use a portion of memory reserved by SQL Server for non-SQL processes running within SQL Server. I cannot remember what the default is for SQL 2005, but the -g startup parameter allows you to configure this memory space. Don't make it too large though, SQL reserves it, so it will take memory away from other SQL processes.
I will give it a try but I don't kno how to do it??
July 10, 2008 at 6:50 am
Make sure you look up the startup paremeters in BOL and come up with an appropriate value.
Setting the startup parameters is one of the options that MS made hard to find in SQL 2005. You have to go into the SQL Server Configuration manager (one of the tools you have probably never opened). Select the SQL Server Services section. Right-click on the MSSQL Service in the list and bring up the properties. The startup parameters are on the Advanced tab. After you change them, you will need to stop and start SQL to apply the new settings.
July 10, 2008 at 6:59 am
Michael Earl (7/10/2008)
Make sure you look up the startup paremeters in BOL and come up with an appropriate value.Setting the startup parameters is one of the options that MS made hard to find in SQL 2005. You have to go into the SQL Server Configuration manager (one of the tools you have probably never opened). Select the SQL Server Services section. Right-click on the MSSQL Service in the list and bring up the properties. The startup parameters are on the Advanced tab. After you change them, you will need to stop and start SQL to apply the new settings.
-dD:\Program Files\Microsoft SQL Server\MSSQL\data\master.mdf;-eD:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG;-lD:\Program Files\Microsoft SQL Server\MSSQL\data\mastlog.ldf
Thanks Michael, could you please let me know excatly where I have to add the "-g512" parameter??
July 10, 2008 at 8:04 am
-dD:\Program Files\Microsoft SQL Server\MSSQL\data\master.mdf;-eD:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG;-lD:\Program Files\Microsoft SQL Server\MSSQL\data\mastlog.ldf;-g512
This is the way I guess; I will try now...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply