HeidiSQL 7.0 released
- Basic support for Microsoft SQL Server, allowing to execute queries, edit grid data and to do a data-only export
- Introduce a separate dialog for all grid export actions, allowing to set up various options before file is created
- Threaded query execution, including a button to stop long running queries
- Enhanced completion proposal
- Grid editing support for binary primary keys
- Implement multi statements in one go for query tabs, to speed up large scripts with many single queries
- User manager: Random password proposals in dropdown menus
- User manager: Support account resource limits
- User manager: Support SSL settings
- Support pluggable authentication on MariaDB 5.2 and MySQL 5.5.7
- Indicate MariaDB and Percona Server with appropriate icons
- Support virtual columns on MariaDB
- File import dialog rewritten
- Session list now resizable instead of auto-sized
- Finally fix NULL-error for FOREIGN_KEY_CHECKS in SQL export
- Support "tabs to spaces" in query editor
- Paint Windows 7 taskbutton progress bar e.g. when executing multiple queries
- Show application screen in Windows 7 Flip3D
- Fetch original SQL code in VIEW editor
- Several fixes for Wine usage
- Support BIT fields in grids and export output
- Fix window placement problems due to multi monitor setup
- Fix flicker on status bar
- Add right click option to toggle visibility of horizontal scrollbar in SQL log (this is for David)
Get it from the download page.
messages at the end of server log, before crash ? messages from mysql server in syslog (if linux), eventlog (if windows) ?
what value caused the crash (data type of field, characters input) ? what´s the last sql entry in heidsql console panel before crash ?
All is good so far.
One thing that really annoys me is that I'm unable to close the first Query Tab. It's most annoying when I load a file into it that could do damaging things to the database. I'd like to be able to close it.
I updated from 6.x (sorry, don't remember the exact version) to 7.0 and cannot connect to my saved database connections now. Startup of the program is considerably slower now and when I try to connect to one of my databases there is a long pause (approx 5 seconds) and a message box opens with this error: "SQL Error (2003): Can't connect to MySQL server on [IP address] (10060)." I AM able to connect to the same databases using MySQL Workbench on both my Mac and Windows computers.
Uninstalling, rebooting, reinstalling did nothing - the connections were still there, which I don't understand - uninstalling means getting rid of everything - at least it should...
Before replying I deleted my saved connections in HeidiSQL, uninstalled it, restarted Windows, and then reinstalled from a fresh download. Same thing.
I'd love to attach a screenshot of my settings and the error window, but I can't see how I would (no "attach image" button above this editor box).
I am running Windows 7 Ultimate within VMWare Fusion v3.3 on Mac OSX 10.7.3. I had HeidiSQL open and had been working in it. A fellow worker informed me that v7.0 was available. I downloaded and installed. Then, after restarting the program I started getting the connection issues.
I would appreciate it if you could provide detailed instructions on completely uninstalling HeidiSQL, including any registry entries, wherever the program saves connection information (obviously that information isn't removed during an uninstall), and any other files that aren't removed during an uninstall.
This is an extremely important tool.
About the uninstall issue I will have to check that - this is probably some InnoSetup seting I was not aware of.
Frustrating, to say the least. Since we discovered HeidiSQL several months ago, it quickly replaced all of our SQL clients! Yet, I'm the only one in the office that's run into this issue...
If there is any additional information I can provide to help resolve this, let me know - I'd like to get this resolved as soon as possible. In the meantime I have to revert to MySQL Workbench and ToadSQL for MSSQL! The horror!
Please login to leave a reply, or register at first.