Comments
Sort by recent activity
THis seems to be the problem !
I cleared the SQL prompt cache, and now the delay has gone ...
Hope this can be fixed in the next patch release,
Thanks,
Bert / comments
THis seems to be the problem !
I cleared the SQL prompt cache, and now the delay has gone ...
Hope this can be fixed in the next patch release,
Thanks,
Bert
I do not see anything happening ( no disk io , no cpu ) when I have to wait. I even tried with my AV disabled, but I did not see any changes.
I did not yet install SQL Server Management Studio on this machine. I'am still using SQL 2000 server & tools.
I manage 8 servers, but most of them are not reachable when I launch isqlw. ( they are only reachable when I connect to the VPN of my clients )
I have a Virtual PC with SQL 2005 server & tools. I will try to install SQL Prompt on the virtual PC and do the same tests.
Thanks,
Bert / comments
I do not see anything happening ( no disk io , no cpu ) when I have to wait. I even tried with my AV disabled, but I did not see any changes.
I did not yet install SQL Server Management Studio on t...
Yes, It takes nearly 5 minutes before the Window appears. I have a windows XP SP2 machine with 4Gb of ram and a P4 3.4Gh processor. I can see the isqlw.exe process in taskmanager, but it does not consume any cpu. it takes 21696 kB of memory when SQL Prompt is enabled. During the 5 minutes wait time, I can not see any cpu usage, only the memory usage changes ( raises to 21744kB ). When the window appears, it takes 27236kB memory, going to 48396kB when connected.
Without SQL Prompt, the login windows pops up in less then a second, and isql uses 6004kB of memory before login. ( 9184 kB after connection ).
The machine uses only 500Mb of the 4Gb of memory when I did this test ... / comments
Yes, It takes nearly 5 minutes before the Window appears. I have a windows XP SP2 machine with 4Gb of ram and a P4 3.4Gh processor. I can see the isqlw.exe process in taskmanager, but it does not c...