Thema: Datenbanksoftware und Tools diverses ...

[SiLæncer]

Database .NET is a simple, uniform and intuitive database management tool for multiple databases. It makes Local and Remote database administration easier without installing anything. With it you can Create databases, Design tables, Edit data, Export data, Generate scripts and run SQL queries.

An innovative, powerful and intuitive multiple database management tool, based on .NET Framework 4.0.

Freeware

Whats new: >>

Code: [Auswählen]

- Row editing ( Data Editor ):
Add: New form editor and Form view ( Form Editor * and Form Viewer ): more intuitive and simple way to edit or browse the column in all field data (4764/4777)
Add: increase in the status bar field NULL / NOT NULL (4764)
Upd: status bar field data type change mining database type (System.Type -> DBType) (4764)
Fix: When a query or edit data output more, the background of the bottom position appears unusual all black (4764)
- Auto-completion, and perception ( Auto Complete and IntelliSense * ):
Add: table fields automatically perceived increased UPDATE and DELETE commands processing (4777)
Upd: field automatically senses first processing (4777)
Upd: auto-complete display project increases the maximum to 100 (4777)
Fix: modified SYSTABLES field can not perceive problems (4777)
- The main program update ( Main ):
Fix: The status window displays when you switch to another program and cover, when to return to the main program still can not back upper display (4777)
Upd: Title increase connection at the beginning of the name of the database, and more open to clear the instance under the taskbar display distinction (4777)
Add: (Oracle) Object Browser PROCEDURES / FUNCTIONS open the context menu, increase SCRIPT AS (CREATE / EXECUTE) such as script generation (4764)
Add: (Oracle) support the the DBMS_OUTPUT output message is displayed, convenience, such as: stored procedures, functions, packages, and triggers is used debug messages (4764)
Upd: Improved display informative messages ( Displaying Informational messages ): as ParseOnly / the CREATE / DROP / ALTER...etc executed successfully but editorial errors or additional message (4764)
Upd: display informative messages ( Displaying informational to be messages ): Join Oracle ADO.NET Managed Provider Support (4764)
Upd: (MySQL / Firebird) database compression (Shrink Database): to deal with progress display (4764)
Fix: (SQL Server) the impact of the amendment (4730): CREATE / ALTER PROC / VIEW / FUNCTION commands such treatment (4759)
Upd: Open Access database and attached to a non-default file name All files (*. *), Increase the automatic judgments mdb / mde or accdb / accde file formats (4759)
Upd: (SQLite) update the components System.Data.SQLite.DLL 1.0.84.0 (3.7.15.2) (2013/01/09) (4759)
Upd: other contains many minor fixes and optimization update ... cumulative processing (4777)
http://fishcodelib.com/Database.htm

[SiLæncer]

Database Browser is an easy to use tool allows you to connect to any database (Oracle, MS-SQL, MySQL, Firebird, etc) and browse or modify data, run sql scripts, export and print data.

Features

    * Works directly with Oracle, MS Sql Server, ODBC, MySql, PostgreSQL, Interbase and Firebird
    * Support for ODBC connection strings
    * Unlimited number of connections
    * One click switching from one connection to another
    * One click table browsing
    * Data browsing
    * Data exports into CSV, Excel, Html files
    * Execution history
    * SQL Builder with wide range of supported databases
    * Execution Log
    * Incremental Table Search

What's new: >>

unbekannt

http://www.etl-tools.com/database-editors/database-browser/overview.html

[SiLæncer]

What's new: >>

unbekannt

http://www.etl-tools.com/database-editors/database-browser/overview.html

[SiLæncer]

MDB Viewer Plus is a tabbed viewer/editor for Access MDB files. It provides a quick and easy way to create, view, edit and search/querry MDB files without having Microsoft Access installed. It is not a full database development solution but allows you to view/edit MDB files without an Access license.

Imports and exports to a variety of formats.

License: Freeware

What's new: >>

2.41

New add table relationship feature.

2.43

Maintenance release.

http://www.alexnolan.net/software/mdb_viewer_plus.htm

[SiLæncer]

Changelog:

Code: [Auswählen]

# Functionality Added or Changed
* InnoDB: The innodb_print_all_deadlocks configuration option from MySQL 5.6 was backported to MySQL 5.5. This option records each deadlock condition in the MySQL error log, allowing easier troubleshooting if frequent deadlocks point to application coding issues.
* In RPM packages built for Unbreakable Linux Network, libmysqld.so now has a version number.
# Bugs Fixed
* InnoDB; Performance: Some data structures related to undo logging could be initialized unnecessarily during a query, although they were only needed under specific conditions.
* InnoDB; Performance: Optimized read operations for compressed tables by skipping redundant tests. The check for whether any related changes needed to be merged from the insert buffer was being called more often than necessary.
* InnoDB; Performance: Immediately after a table was created, queries against it would not use loose index scans. The issue went away following an ALTER TABLE on the table. The fix improves the accuracy of the index statistics gathered when the table is first created, and prevents the query plan from being changed by the ALTER TABLE statement.
* InnoDB; Partitioning: Previously, when attempting to optimize one or more partitions of a partitioned table that used a storage engine that does not support partition-level OPTIMIZE, such as InnoDB, MySQL reported Table does not support optimize, doing recreate + analyze instead, then re-created the entire table, but did not actually analyze it. Now in such cases, the warning message is, Table does not support optimize on partitions. All partitions will be rebuilt and analyzed. In addition, the entire table is analyzed after first being rebuilt.
* InnoDB: On systems that cannot handle unaligned memory access, depending on the stack frame alignment, a SIGBUS error could occur during startup. This issue was observed on Solaris 64-bit systems.
* InnoDB: The status variable Innodb_buffer_pool_read_ahead_evicted could show an inaccurate value, higher than expected, because some pages in the buffer pool were incorrectly considered as being brought in by read-ahead requests.
* InnoDB: Creating an index on a CHAR column could fail for a table with a character set with varying length, such as UTF-8, if the table was created with the ROW_FORMAT=REDUNDANT clause.
* InnoDB: The server could halt with an assertion error while creating an index: InnoDB: Assertion failure in thread thread_num in file row0merge.cc line 465 This issue affected tables with a combination of ROW_FORMAT=REDUNDANT off-page columns, and an index on a column prefix.
* InnoDB: If the server crashed at a precise moment during an ALTER TABLE operation that rebuilt the clustered index for an InnoDB table, the original table could be inaccessible afterward. An example of such an operation is ALTER TABLE ... ADD PRIMARY KEY The fix preserves the original table if the server halts during this operation. You might still need to rename the .ibd file manually to restore the original table contents: in MySQL 5.6 and higher, rename from #sql-ib$new_table_id.ibd to table_name.ibd within the database directory; prior to MySQL 5.6, the temporary file to rename is table_name#1 or #2.
* InnoDB: An error at the filesystem level, such as too many open files, could cause an unhandled error during an ALTER TABLE operation. The error could be accompanied by Valgrind warnings, and by this assertion message: Assertion `! is_set()' failed. mysqld got signal 6 ;
* InnoDB: A RENAME TABLE statement could stall for several minutes before timing out. This issue could occurred for a table using compression, with change buffering enabled.
* InnoDB: During shutdown, with the innodb_purge_threads configuration option set greater than 1, the server could halt prematurely with this error: mysqld got signal 11 A workaround was to increase innodb_log_file_size and set innodb_purge_threads=1. The fix was backported to MySQL 5.5 and 5.1, although those versions do not have the innodb_purge_threads configuration option so the error was unlikely to occur.
* InnoDB: If the value of innodb_force_recovery was less than 6, opening a corrupted table might loop forever if a corrupted page was read when calculating statistics for the table. Information about the corrupted page was written repeatedly to the error log, possibly causing a disk space issue. The fix causes the server to halt after a fixed number of failed attempts to read the page. To troubleshoot such a corruption issue, set innodb_force_recovery=6 and restart.
* InnoDB: The value of the innodb_version variable was not updated consistently for all server releases for the InnoDB Plugin in MySQL 5.1, and the integrated InnoDB component in MySQL 5.5, 5.6, and higher. Since InnoDB and MySQL Server development cycles are fully integrated and synchronized, now the value returned by the innodb_version variable is the same as for the version variable.
* Partitioning: Concurrent ALTER TABLE ... REBUILD PARTITION operations could interfere with one another, even when not running against the same table, because they both used global memory for storage. Now each partition rebuild operation stores intermediate data in memory that is local to that process.
* Partitioning: Inserting any number of rows into an ARCHIVE table that used more than 1000 partitions and then attempting to drop the table caused the MySQL Server to fail.
* Replication: After dropping a column from the slave's version of a table, then altering the same column of this table on the master (so that a type conversion would have been required had the column not been droppped on the slave), inserts into this table caused replication to fail.
* Replication: When a binary log is replayed on a server (for example, by executing a command like mysqlbinlog binlog.000001 | mysql), it sets a pseudo-slave mode on the client connection used, so that the server can read binlog and apply binary log events correctly. However, the pseudo-slave mode was not disabled after the binary log dump was read, which caused unexpected filtering rules to be applied to SQL statements subsequently executed on the same connection.
* Replication: When using statement-based replication, and where the master and the slave used table schemas having different AUTO_INCREMENT columns, inserts generating AUTO_INCREMENT values logged for a given table on the master could be applied to the wrong table on the slave.
* Replication: Repeated execution of CHANGE MASTER TO statements using invalid MASTER_LOG_POS values could lead to errors and possibly a crash on the slave. Now in such cases, the statement fails with a clear error message.
* Replication: If the disk becomes full while writing to the binary log, the server hangs until space is freed up manually. It was possible after this was done for the MySQL server to fail, due to an internal status value being set when not needed. Now in such cases, rather than trying to set this status, a warning is written in the error log instead.
* Microsoft Windows: Dynamic file names (with colons) are no longer allowed. Static file names using the Alternate Data Stream (ADS) NTFS functionality of Microsoft Windows may continue to be used.
* Joins of exactly 32 tables and containing a HAVING clause returned an empty result.
* A buffer-handling problem in yaSSL was fixed.
* A mysys library string-formatting routine could mishandle width specifiers.
* In certain cases, UpdateXML() could return NULL incorrectly.
* Metadata locking and table definition cache routines did not always check length of names passed to them.
* XA START had a race condition that could cause a server crash.
* Enabling the query cache during high client contention could cause the server to exit.
* There was a performance regression for queries using SELECT ... INTO user variables and a WHERE condition on one or more of the variables in the INTO list.
* The server sometimes failed to respect MAX_CONNECTIONS_PER_HOUR limits on user connections.
* Output generated with mysqldump --routines could produce syntax errors when reloaded.
* With the thread pool plugin installed, a workload consisting of concurrent KILL statements and ping queries caused the server to exit.
* CHECK TABLE and REPAIR TABLE could crash if a MyISAM table had a corrupt key (.MYI) file. Now the server produces an error.
* Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak.
* For dumps of the mysql database, mysqldump skipped the event table unless the --events option was given. To skip this table if that is desired, use the --ignore-table option instead
* For MEMORY tables with HASH indexes, DELETE sometimes failed to delete all applicable rows.
* The mysql client could mishandle the delimiter command if it occurred on a line during which mysql was looking for the end of a quoted string.
* mysqld_safe used the nonportable -e test construct.
* Configuring the server with performance_schema_events_waits_history_size=0 and performance_schema_events_waits_history_long_size=0 could cause a Performance Schema segmentation fault.
* DECIMAL multiplication operations could produce significant inaccuracy.
* For subqueries executing using a filesort, the optimizer could produce an incorrect result containing wrong rows.
* UNION type conversion could incorrectly turn unsigned values into signed values.
* During the startup process, mysqld could incorrectly remove the PID file of an already running mysqld.
www.mysql.com

[SiLæncer]

Vor fast genau zwei Jahren erschien MySQL 5.5 als erste Version nach der Übernahme von Sun durch Oracle. Sie ersetzte das alte MyISAM-Backend durch das transaktionsfähige InnoDB als Voreinstellung für Tabellen. Mit der heute veröffentlichten Version 5.6 kann InnoDB nun MyISAM komplett ersetzen, da es die diesem bislang vorbehaltene Volltextsuche nachrüstet.

Ein weiterer Schwerpunkt der Entwicklung war das Beschleunigen von Subqueries. Sie sollen nun durch Semi-Joins und Materialisierung deutlich schneller laufen, und es soll nicht mehr nötig sein, Subqueries durch Joins zu ersetzen. Viele Änderungen an den Datenstrukturen, etwa ALTER TABLE, führt MySQL 5.6 online aus, was längere Stillstandszeiten vermeidet. EXPLAIN informiert nun auch über die Ausführungspläne von UPDATE-, DELETE- und INSERT-Kommandos

Der ganze Artikel

Quelle : www.heise.de

[SiLæncer]

This tool allows completely manage any Interbase >5.x/Firebird database. It is based on Borland IBX components. It contains following modules:

    SQL Editor
    It contains SQL Editor with syntax highlighting with Result Buffer. You can run any type of sql statement or script. Output is flushed to formatted text, not to grid, what it allows more flexible and synoptic result overview.
    You can also export/import data to/from CSV, XML, raw batch file or printer.
    Every correctly run statement is saved in SQL History Buffer. You can open multiple instances of this editor to run "simultaneous" queries.
    Object Explorer
    Here you can inspect every database object including its detail properties. Some object you can edit too. Also you can extract metadata of all objects including data for tables.
    Event Watcher
    Here you can inspect user defined event triggering.
    Performance Monitor
    This tool allows profile and watch database operations. It contains following modules:
        Memory usage of watched database
        Number of writes and read to database and to buffer cache
    User Manager
    Allows you add, edit and delete database users and roles.
    Grant Manager
    Allows to grant or revoke privileges on all database objects.
    Services
    Here are available following services:
        Server Log View
        Server Properties Overview
        Database Statistics Overview
        Database Validation Task

Freeware

http://www.mitec.cz/ibq.html

[SiLæncer]

Changelog:

Code: [Auswählen]

# changes-

- Prevent execution of enum_recv from SQL (Tom Lane)
The function was misdeclared, allowing a simple SQL command to crash the server. In principle an attacker might be able to use it to examine the contents of server memory. Our thanks to Sumit Soni (via Secunia SVCRP) for reporting this issue. (CVE-2013-0255)
- Fix multiple problems in detection of when a consistent database state has been reached during WAL replay (Fujii Masao, Heikki Linnakangas, Simon Riggs, Andres Freund)
- Fix detection of end-of-backup point when no actual redo work is required (Heikki Linnakangas)
This mistake could result in incorrect "WAL ends before end of online backup" errors.
- Update minimum recovery point when truncating a relation file (Heikki Linnakangas)
Once data has been discarded, it's no longer safe to stop recovery at an earlier point in the timeline.
- Fix recycling of WAL segments after changing recovery target timeline (Heikki Linnakangas)
Properly restore timeline history files from archive on cascading standby servers (Heikki Linnakangas)
- Fix lock conflict detection on hot-standby servers (Andres Freund, Robert Haas)
- Fix missing cancellations in hot standby mode (Noah Misch, Simon Riggs)
The need to cancel conflicting hot-standby queries would sometimes be missed, allowing those queries to see inconsistent data.
- Prevent recovery pause feature from pausing before users can connect (Tom Lane)
- Fix SQL grammar to allow subscripting or field selection from a sub-SELECT result (Tom Lane)
- Fix performance problems with autovacuum truncation in busy workloads (Jan Wieck)
Truncation of empty pages at the end of a table requires exclusive lock, but autovacuum was coded to fail (and release the table lock) when there are conflicting lock requests. Under load, it is easily possible that truncation would never occur, resulting in table bloat. Fix by performing a partial truncation, releasing the lock, then attempting to re-acquire the lock and continue. This fix also greatly reduces the average time before autovacuum releases the lock after a conflicting request arrives.
- Improve performance of SPI_execute and related functions, thereby improving PL/pgSQL's EXECUTE (Heikki Linnakangas, Tom Lane)
Remove some data-copying overhead that was added in 9.2 as a consequence of revisions in the plan caching mechanism. This eliminates a performance regression compared to 9.1, and also saves memory, especially when the query string to be executed contains many SQL statements.
A side benefit is that multi-statement query strings are now processed fully serially, that is we complete execution of earlier statements before running parse analysis and planning on the following ones. This eliminates a long-standing issue, in that DDL that should affect the behavior of a later statement will now behave as expected.
- Restore pre-9.2 cost estimates for index usage (Tom Lane)
An ill-considered change of a fudge factor led to undesirably high cost estimates for use of very large indexes.
- Fix intermittent crash in DROP INDEX CONCURRENTLY (Tom Lane)
- Fix potential corruption of shared-memory lock table during CREATE/DROP INDEX CONCURRENTLY (Tom Lane)
- Fix COPY's multiple-tuple-insertion code for the case of a tuple larger than page size minus fillfactor (Heikki Linnakangas)
The previous coding could get into an infinite loop.
- Protect against race conditions when scanning pg_tablespace (Stephen Frost, Tom Lane)
CREATE DATABASE and DROP DATABASE could misbehave if there were concurrent updates of pg_tablespace entries.
- Prevent DROP OWNED from trying to drop whole databases or tablespaces (Álvaro Herrera)
For safety, ownership of these objects must be reassigned, not dropped.
- Fix error in vacuum_freeze_table_age implementation (Andres Freund)
The main consequence of this mistake is that lowering vacuum_freeze_min_age would cause full-table vacuuming scans to occur much more frequently than intended.
- Prevent misbehavior when a RowExpr or XmlExpr is parse-analyzed twice (Andres Freund, Tom Lane)
This mistake could be user-visible in contexts such as CREATE TABLE LIKE INCLUDING INDEXES.
- Improve defenses against integer overflow in hashtable sizing calculations (Jeff Davis)
- Fix some bugs associated with privileges on datatypes (Tom Lane)
- There were some issues with default privileges for types, and pg_dump failed to dump such privileges at all.
- Fix failure to ignore leftover temporary tables after a server crash (Tom Lane)
- Fix failure to rotate postmaster log files for size reasons on Windows (Jeff Janes, Heikki Linnakangas)
Reject out-of-range dates in to_date() (Hitoshi Harada)
- Fix pg_extension_config_dump() to handle extension-update cases properly (Tom Lane)
This function will now replace any existing entry for the target table, making it usable in extension update scripts.
- Fix PL/pgSQL's reporting of plan-time errors in possibly-simple expressions (Tom Lane)
The previous coding resulted in sometimes omitting the first line in the CONTEXT traceback for the error.
- Fix PL/Python's handling of functions used as triggers on multiple tables (Andres Freund)
- Ensure that non-ASCII prompt strings are translated to the correct code page on Windows (Alexander Law, Noah Misch)
This bug affected psql and some other client programs.
- Fix possible crash in psql's \? command when not connected to a database (Meng Qingzhong)
- Fix possible error if a relation file is removed while pg_basebackup is running (Heikki Linnakangas)
- Tolerate timeline switches while pg_basebackup -X fetch is backing up a standby server (Heikki Linnakangas)
- Make pg_dump exclude data of unlogged tables when running on a hot-standby server (Magnus Hagander)
This would fail anyway because the data is not available on the standby server, so it seems most convenient to assume --no-unlogged-table-data automatically.
- Fix pg_upgrade to deal with invalid indexes safely (Bruce Momjian)
- Fix pg_upgrade's -O/-o options (Bruce Momjian)
- Fix one-byte buffer overrun in libpq's PQprintTuples (Xi Wang)
This ancient function is not used anywhere by PostgreSQL itself, but it might still be used by some client code.
- Make ecpglib use translated messages properly (Chen Huajun)
- Properly install ecpg_compat and pgtypes libraries on MSVC (Jiang Guiqing)
- Include our version of isinf() in libecpg if it's not provided by the system (Jiang Guiqing)
- Rearrange configure's tests for supplied functions so it is not fooled by bogus exports from libedit/libreadline (Christoph Berg)
- Ensure Windows build number increases over time (Magnus Hagander)
- Make pgxs build executables with the right .exe suffix when cross-compiling for Windows (Zoltan Boszormenyi)
- Add new timezone abbreviation FET (Tom Lane)
www.postgresql.org

[SiLæncer]

3.5.7.0 (2013-02-15)

- bug #3779 [core] Problem with backslash in enum fields
- bug #3816 Missing server_processlist.php
- bug #3821 Safari: white page
- Correct detection of the Chrome browser

http://www.phpmyadmin.net/home_page/index.php

[SiLæncer]

Database .NET is a simple, uniform and intuitive database management tool for multiple databases. It makes Local and Remote database administration easier without installing anything. With it you can Create databases, Design tables, Edit data, Export data, Generate scripts and run SQL queries.

An innovative, powerful and intuitive multiple database management tool, based on .NET Framework 4.0.

Freeware

Whats new: >>

Code: [Auswählen]

- The main program update ( Main ):
Add: Support database object script generation batch processing ( Script all database objects ) (4800)
Fix: the correction the Properties and NavigationProperties properties of (OData) repeat when exception handling (4800)
Upd: Updated Czech interface language Czech language (by Šůla Jiří) (4800)
Upd: update all language files, support for a more complete interface the localized display (4800)
Upd: (MySQL) update the components MySql.Data.dll 6.6.5 (2013/02/05) (4794)
Upd: other contains many minor fixes and optimization update ... cumulative processing (4800)
Upd: Update Database. NET Additional Files ( ) (2013/02/08)
Misc: Compatible with PostgreSQL 9.2.3 (2013/02/07)
Misc: Compatible with MySQL 5.6.10 (2013/02/01) / MySQL 5.5.30 (2013/02/05) / MySQL 5.1.68 (2013/01/11)
- Row editing ( Data Editor ):
Add: Add a quick tour of the edit button ( Quick Button ): where rapid button click of mouse movement, you can directly browse or edit where data (4794/4800)
Add: data grid editing (Cell): New date picker ( DateTime Picker ) (4800)
Add: Form Editor ( Form Editor * ): New obtain the current date set ( Get current date ) (4800)
Fix: Form Editor ( Form Editor * ): correction edit unsaved state secondary open editing can not save (4800)
Fix: Form browser ( Form Viewer ): the correct custom SQL command query open failure (4800)
Fix: correction custom SQL command query, the status bar may lead to not display (4800)
Fix: Form data grid editor ( Form and Cell Editor *): improvement and correction of the new row (NewRow) handling multiple issues (4800)
Fix: Fixed multiple selection row delete if contains the same row, in the the delete other same row still displays the error message (4800)
- SQL Editor ( SQL Editor ):
Upd: message is displayed in a different color to distinguish between the implementation of the successes and failures of the results ( Different color for messages ) (4800)
Add: the tab menu increased all off function (Close All) (4800)
Upd: significantly improved tab and Batch the close processing speed (Close All But This / Close All) (4800)
Upd: Improved Repeat GO [count] parsing processing (for all database processing) (4800)
- Code Management ( Code Manager ):
Upd: Improved rename the directory and file processing speed, remove unnecessary heavy brush handle (4800)
- SQL Performance Analyzer ( SQL Profiler * ) and:
Add: (SQL Server) to add conditions screening function ( Filter ): designated or exclude the analysis of data (4800)
Add: data column shows the increase in the right-click menu Copy functions (Copy) (4800)
Upd: the open query page history feature ( SQL Execution History :, the original Additional features ) (4794)
Upd: historical record keeping (SaveAs. ..) SQL command content Tab characters turn blank, in order to split the field character as the difference between (4794/4800)
- Auto-completion, and perception ( Auto Complete and IntelliSense * ):
Add: Increase tables sensations are processed automatically (SELECT * FROM / DELETE FROM / INSERT INTO) + Space (4794)
Add: Add shortcuts List Members List Members: Ctrl + J (4794)
Add: table fields automatically perceived increase INSERT command complete treatment process (including the SELECT / UPDATE / DELETE / INSERT) (4794)
Upd: (the SQLServer / SQL Azure / SybaseASE) when inserted into the table schema non-dbo automatically append schema name (4794)
Fix: Fixed a query displays only contains characters] (% word%) will not be displayed without any match [prefix] (word%) completed window (4794)
Fix: fix Schema or Table contains QuotedString, lead field perception problem (4794) 
http://fishcodelib.com/Database.htm

[SiLæncer]

Database Browser is an easy to use tool allows you to connect to any database (Oracle, MS-SQL, MySQL, Firebird, etc) and browse or modify data, run sql scripts, export and print data.

Features

    * Works directly with Oracle, MS Sql Server, ODBC, MySql, PostgreSQL, Interbase and Firebird
    * Support for ODBC connection strings
    * Unlimited number of connections
    * One click switching from one connection to another
    * One click table browsing
    * Data browsing
    * Data exports into CSV, Excel, Html files
    * Execution history
    * SQL Builder with wide range of supported databases
    * Execution Log
    * Incremental Table Search

What's new: >>

unbekannt

http://www.etl-tools.com/database-editors/database-browser/overview.html

[SiLæncer]

5.0.0.5

+ Support for BDE was introduced
- Various bug fixes

http://www.etl-tools.com/database-editors/database-browser/overview.html

[SiLæncer]

Database .NET is a simple, uniform and intuitive database management tool for multiple databases. It makes Local and Remote database administration easier without installing anything. With it you can Create databases, Design tables, Edit data, Export data, Generate scripts and run SQL queries.

An innovative, powerful and intuitive multiple database management tool, based on .NET Framework 4.0.

Freeware

Whats new: >>

Code: [Auswählen]

- The main program update ( Main ):
Add: Support database object script generation batch processing ( Script all database objects ) (4800)
Fix: the correction the Properties and NavigationProperties properties of (OData) repeat when exception handling (4800)
Upd: Updated Czech interface language Czech language (by Šůla Jiří) (4800)
Upd: update all language files, support for a more complete interface the localized display (4800)
Upd: (MySQL) update the components MySql.Data.dll 6.6.5 (2013/02/05) (4794)
Upd: other contains many minor fixes and optimization update ... cumulative processing (4800)
Upd: Update Database. NET Additional Files ( ) (2013/02/08)
Misc: Compatible with PostgreSQL 9.2.3 (2013/02/07)
Misc: Compatible with MySQL 5.6.10 (2013/02/01) / MySQL 5.5.30 (2013/02/05) / MySQL 5.1.68 (2013/01/11)
- Row editing ( Data Editor ):
Add: Add a quick tour of the edit button ( Quick Button ): where rapid button click of mouse movement, you can directly browse or edit where data (4794/4800)
Add: data grid editing (Cell): New date picker ( DateTime Picker ) (4800)
Add: Form Editor ( Form Editor * ): New obtain the current date set ( Get current date ) (4800)
Fix: Form Editor ( Form Editor * ): correction edit unsaved state secondary open editing can not save (4800)
Fix: Form browser ( Form Viewer ): the correct custom SQL command query open failure (4800)
Fix: correction custom SQL command query, the status bar may lead to not display (4800)
Fix: Form data grid editor ( Form and Cell Editor *): improvement and correction of the new row (NewRow) handling multiple issues (4800)
Fix: Fixed multiple selection row delete if contains the same row, in the the delete other same row still displays the error message (4800)
- SQL Editor ( SQL Editor ):
Upd: message is displayed in a different color to distinguish between the implementation of the successes and failures of the results ( Different color for messages ) (4800)
Add: the tab menu increased all off function (Close All) (4800)
Upd: significantly improved tab and Batch the close processing speed (Close All But This / Close All) (4800)
Upd: Improved Repeat GO [count] parsing processing (for all database processing) (4800)
- Code Management ( Code Manager ):
Upd: Improved rename the directory and file processing speed, remove unnecessary heavy brush handle (4800)
- SQL Performance Analyzer ( SQL Profiler * ) and:
Add: (SQL Server) to add conditions screening function ( Filter ): designated or exclude the analysis of data (4800)
Add: data column shows the increase in the right-click menu Copy functions (Copy) (4800)
Upd: the open query page history feature ( SQL Execution History :, the original Additional features ) (4794)
Upd: historical record keeping (SaveAs. ..) SQL command content Tab characters turn blank, in order to split the field character as the difference between (4794/4800)
- Auto-completion, and perception ( Auto Complete and IntelliSense * ):
Add: Increase tables sensations are processed automatically (SELECT * FROM / DELETE FROM / INSERT INTO) + Space (4794)
Add: Add shortcuts List Members List Members: Ctrl + J (4794)
Add: table fields automatically perceived increase INSERT command complete treatment process (including the SELECT / UPDATE / DELETE / INSERT) (4794)
Upd: (the SQLServer / SQL Azure / SybaseASE) when inserted into the table schema non-dbo automatically append schema name (4794)
Fix: Fixed a query displays only contains characters] (% word%) will not be displayed without any match [prefix] (word%) completed window (4794)
Fix: fix Schema or Table contains QuotedString, lead field perception problem (4794)
http://fishcodelib.com/Database.htm

[SiLæncer]

Whats new: >>

 Add: Increase xls,. Xlsx,. Xlsm, xlsb file type the database automatically detect processing (the original omissions processing) (4813)
Upd: other contains Various minor fixes and updates ... cumulative processing (4813)
- Row editing and browsing ( Data Editor and Browser ):
Upd: Improving the browse mode to NULL displayed with the edit mode (4813)
Fix: correction (4808) led to the numeric type is NULL, the browse mode delay (4813)
Upd: Browse mode allows clicking on the field to sort (Sorting by clicking the column header) (with edit mode) (4808)
- Database Diagrams ( Database Diagram * ):
Add: Increase inquiry options: generate charts can choose to generate only the current table or all dependent tables associated (4808)
Upd: improving processing speed, when the table contains more associated significant improvement (4808)
Fix: Fixed the Save Image (SaveAs) and print (Print) output not synchronized update the chart window size problem (4808)
- Table editing ( Table Editor ):
Fix: (SQLCe / SQLAzure / SQL Server) to resolve when CONSTRAINT NAME contains exceptions character can not change the default value (Default Value) (4808)
- Script generation ( Data Definition Language ):
Upd: the processing SQLCe data table field default value (Default Value), removal of the original content at the end of the extra newline characters (4808)
- SQL Performance Analyzer ( SQL Profiler * ) and:
Upd: Log Mode History ( SQL Execution History ): the original record Total time change record Execution time (4808)

http://fishcodelib.com/Database.htm

[SiLæncer]

Exportizer is a free database export tool. It allows you to export data to a file, clipboard, or printer. Exportizer works via BDE or ADO. It can convert DB, DBF, text, CSV to text, CSV, XLS, RTF, XML, HTML, DBF, and INSERT statements. Many export options ensure full control over output. There is an ability to specify the source-to-target field mappings. Export operations can be performed either via the program interface or via command line with large number of parameters. You can easily generate needed command line directly from the GUI. It is possible to copy data to the clipboard or print it. There are several utility functions for data manipulating and bookmarking.

Features:

Opening tables from multi-table database files like XLS, XLSX, XLSM, XLSB, MDB, ACCDB, HTML, GDB, IB, FDB, UDL, and other multi-table databases like ODBC data sources etc.
Exporting data from all files, which are located in one folder, or all tables from a multi-table data source, at once (from interface or via command line).
Ability to specify custom increment number for Increment Field Value function.
Exporting data to Excel (XML-based) and DATABASE formats.
Using extra command line line options like /Silent, /LogFile, /CloseOnError etc.
Using extra export modes like Append and Empty+Insert.

Freeware

http://www.vlsoftware.net/