Windows 7 is not supported: Not enough memory errors and no result sets

[Jaxelr]

Current OS: Windows 7 enterprise
Python Version: 3.6.3
Pip Version: 9.0.1
RAM: 16 Gigs.

As seen in the screenshot, the steps which i followed were:

1. connected to instance
2. Ran a Select for a table with 3 records and got an error message of Not enough memory.
3. Ran a Select TOP 1 for a table with 3 records and got an error message of Not enough memory.

[pensivebrian]

Thanks for reporting @Jaxelr. We're investigating this.

[pensivebrian]

For now, we think this is Windows 7 specific. If someone experiences this issue on a non-Windows 7 OS, please let us know on this thread.

[pasimetes17]

pip 9.0.1
python 3.6
Windows 64 bit Profesional

Same with me:
XXXsafe3>SELECT * from "dbo"."tblUsers" where "LastName" like 'St%'
Not enough memory.
Time: 0.125s
It is just one record.

[mjgpy3]

I'm experiencing the same error, windows 7.

[redfox-dev]

Same with me, I see the message even when I just hit enter.

master>
Not enough memory.
Time: 0.000s
master>
Not enough memory.
Time: 0.000s
master>

[abhisheksinha89]

I am investigating this issue. Will keep you posted with updates

[ndwivedi]

Same issue windows 7.

[abhisheksinha89]

Thanks. We have narrowed this issue down to the more pager on Windows 7 does not handle UTF-8 codepage (cp65001) properly.
We are currently investigating workarounds for our tool

[abhisheksinha89]

An update for this. Since Windows 7 cmd prompt does not have good support for more paging using UTF-8 codepages and there is no good workaround for this. We are going to remove Windows7 from the supported OS list for now.
The issues appears to be in https://github.com/pallets/click/blob/92532b58b1205b70737f837567f67c59949f3dc2/click/_termui_impl.py#L288 package that we use to print results on stdout using a pager and windows 7 cannot deal with code page 65001.

We'll take a look at this at a later date.

[Jaxelr]

Thanks for the effort into looking at this issue. 👍

[chubbsm]

I'm getting the same thing on Windows 2008 R2 server.

[aflansburg]

Judging by the inactivity there may not be much interest in addressing this, but this is still persistent in Windows 7. Looking at my processes I can see the MicrosoftSqlToolsServiceLayer.exe is using 790MB. Attaching a debugger to this process didn't provide any useful information, but it could be the culprit.

Referencing an issue in a repo for a mssql vscode extension, this supports the theory that there is an issue with the MicrosoftSqlToolsServiceLayer executable.

[pensivebrian]

Closing this as won't fix. If click issue pallets/click#905 ever gets fixed, we can take another look.