Some of our databases have to be accessed from a Windows 'Jump Server'; we recently upgraded these to Windows Server 2012 R2 and we now have an issue loading external SQL files into PLSQL Developer.
e.g. When I connect to the jump server using RDP, my local drives are mapped via tsclient. I have those tsclient 'drives' mapped in the 'Files' tab within PL SQL Developer. Loading a SQL file from one of those mapped directories used to be quick (under Windows Server 2003) but it can now take 5 minutes+ to load an 800 line package body (saved as a '.sql' file)!
PLSQL Developer Details:
PL/SQL Developer
Version 12.0.2.1818 (64 bit)
407.96850 - Unlimited user license
Service Contract: 01/09/2017
Windows 8.1 Build 9600
Physical memory : 67,108,404 kB (61,927,436 available)
Paging file : 73,398,836 kB (66,716,032 available)
Virtual memory : 137,438,953,344 kB (137,438,559,064 available)
Loading the same .sql file in notepad++ is instantaneous so I don't believe we have any network latency.
Is this behaviour that has been seen before and have you any ideas on a fix?
Thanks,
Steve
e.g. When I connect to the jump server using RDP, my local drives are mapped via tsclient. I have those tsclient 'drives' mapped in the 'Files' tab within PL SQL Developer. Loading a SQL file from one of those mapped directories used to be quick (under Windows Server 2003) but it can now take 5 minutes+ to load an 800 line package body (saved as a '.sql' file)!
PLSQL Developer Details:
PL/SQL Developer
Version 12.0.2.1818 (64 bit)
407.96850 - Unlimited user license
Service Contract: 01/09/2017
Windows 8.1 Build 9600
Physical memory : 67,108,404 kB (61,927,436 available)
Paging file : 73,398,836 kB (66,716,032 available)
Virtual memory : 137,438,953,344 kB (137,438,559,064 available)
Loading the same .sql file in notepad++ is instantaneous so I don't believe we have any network latency.
Is this behaviour that has been seen before and have you any ideas on a fix?
Thanks,
Steve