Original Address: http://community.9cbs.net/expert/topic/3798/3798231.xml? Temp = .9782984 built a link (name = xLink) in SQL Server import the corresponding data into the Oracle database, The INSERT statement is as follows: INSERT INTO OpenQuery (xxlink, 'select colip1, col2, col3 from tableinoracle') Select Col1, col2, col3 from tableinsqlserverwhere .......
It used to be properly performed, from recent days, you can't get it, the following error Server: MSG 7399, Level 16, State 1, Line 1ole DB Provider 'MSDara' reported An Error. The Provider Ran Out of Memory. [OLE / DB Provider.] OLE DB ERROR TRACE [OLE / DB Provider 'MSDara' IROWSetChange :: Insertrow Returned 0x8007000E: The Provider Ran Out of Memory.].
Beginning to restart SQL Server or restart the server, it is possible to ensure proper execution, but it is not possible to resolve the process: add the startup parameter -g (for example using -G384) online help to the interpretation of the -g parameter: specify the virtual in megabytes The address space size, SQL Server will preserve this part of the address space for memory allocation within the SQL Server process, but place it outside the SQL Server memory pool. This area is used by SQL Server to load, such as extended procedures .dll files, distributed queries, which are referenced by OLE DB providers, and automation objects referred to in the Transact-SQL statement. The default is 256 MB.
Using this option helps adjust memory allocation, but only when SQL Server 2000 Personal Edition or SQL Server 2000 Standard Edition is greater than 3 GB or SQL Server 2000 Enterprise Edition is only available. For the configuration of less physical memory than the above value, there will be no help even if this option is used. If the memory usage requirements of SQL Server, and the virtual address space of the SQL Server process is all used, then this option is appropriate in such large memory configurations. Using this option inappropriately may cause the SQL Server instance that cannot start or encounter runtime errors.
The default value of the -g parameter should be used unless you see the following warning information in the SQL Server error log:
WARNING: Clearing Procedure Cache to Free Contiuous Memory
This information indicates that SQL Server is trying to release part of the SQL Server memory pool to find space for extended stored procedures.dll files or automation objects. In this case, the amount of memory retained by the -g switch can be considered. Use values below the default to increase the amount of available memory in the buffer pool and the thread stack; in systems that do not use a lot of extended stored procedures, distributed query, or automation objects, this method can be a workload belt that requires a large amount of memory. The benefits of performance.
