Tag Info

New answers tagged

1

Well...We solved the problem. There was an Update, inside the procedure running that "select * from...". I commented the update. no more problems.


1

This may be an issue with OLEDB calls to remote servers (linked servers and SSIS configurations use OLEDB). This is a design flaw, Microsoft SQL Server bug that wasn't patched until SQL Server 2012 SP1 from what I recall where it doesn't allow remote stats to be used to optimize the query remotely. You will need to run sp_WhoIsActive (download | docs) from ...


2

It's a simple select. Why is this using fetch_cursor? The SELECT is system-generated by the Distributed Query framework, and is associated with the UPDATE you found. The Remote Update query plan operator uses the sp_cursor model to fetch rows from the remote data source. This is the cause of all the cursor API calls. I believe the cursor plan you show ...


2

It's not a bug. This behaviour is expected. If you need to increase the connections, just change the processes limit: SQL> show parameter processes processes integer 150 SQL> alter system set processes = <integer> scope=[...]; SQL> shutdown immediate; SQL> startup; -- Either using pfile or spfile, you'll ...


2

Oracle up to 11g used a thread based model on Windows and a process based model on Linux. Quote from the manual: A process is a mechanism in an operating system that can run a series of steps. The mechanism depends on the operating system. For example, on Linux an Oracle background process is a Linux process. On Windows, an Oracle background process is ...



Top 50 recent answers are included