Closed apelade closed 9 years ago
tried reverting to check.. no longer stops at the Proceed point.. closing until I figure it out
just to keep the notes: Drivers: In the sqlalchemy page they mention adodbapi driver but it's still on an old version of sqlalchemy. If on linux it would make more sense to check out tds route.
Did a few more tries with Python3.4+pymssql, I see that it's 3.4 in travis. That and pymssql seemed to at least show the rows before Proceed? https://gist.github.com/apelade/39f5872a0aaf2bdd8f14
That got an OperationalError, so thought to try different driver Python 3.3+pyodbc, different size fraction, schema. Getting alot of: No approximation known for driver pyodbc DEBUG:root:failed to get approximate rowcount for table_name Had better luck with pymssql
Modifying the test_subsetter.py to work against my setup..
The issue
Answered 'n' and it appeared to proceed. Restarted to kill the connection. Ctrl-C and Ctrl-Z did not halt it. Possibly still trying to process the massive db? There is something else wrong with my databases, users, or command - I don't get the list of changes before Proceed? is offered. It appeared to be busy or hang, cursor blinking.
Stack versions: Windows7 Python 3.4.2 pip (1.5.6) pymssql (2.1.1) rdbms-subsetter (0.2.1) setuptools (2.1) SQLAlchemy (0.9.8)
Thanks for the project, will be watching closely! We are trying to use it for our 250GB Microsoft SQL Server DB, no luck so far. Took me a while to figure out the dependencies to use and the connection string, so that would really promote adoption for casual users. I made it to the point of getting KeyErrors.