Apex SQL Tools Blog

Some of you have been chafing at the bit for fixes and new features in ApexSQL Edit. Some of us have too. We've made some fundamental changes at ApexSQL in the last few days that will ensure we're on the fast track to delivering these long awaited fixes, features.

As of this week we've restructured the "business" of ApexSQL Edit, which was formally a joint partnership between Ashton Hobbs and ApexSQL LLC.

Ashton created ApexSQL Edit from concept to release and used to manage the entire support forum. Overtime the partnership changed so that ApexSQL took over the help file, then support activities and testing. But even as we added economies of scale they were never enough to keep pace with the demands of this complex tool. Recently we have arrived at an agreement that allows ApexSQL LLC to fully acquire all remaining rights (and responsibilities) to ApexSQL Edit. This allows us to increase the through put on this app. exponentially, empowers us to effect change and frees Ashton to pursue some excellent technology for ApexSQL that he hasn't been able to release.

We have some challenges ahead to align ApexSQL Edit with our other apps, fix all outstanding bugs, streamline and simplify the app and then once a high quality baseline has been achieved launch an aggressive development schedule. The next few weeks will be spent managing this transition but we have already begun. I have already allocated some of my best devs and analysts to this task and we're going to be putting as many resources into this as the app. can hold.

The plan includes

Deprecating underperforming and/or overly-complex features that most users don't want or need. We'll be posting a list.

Replacing some modules - like formatting and extended props editor, that were underperforming, with completed, tested components we have ready.

Standardizing the code for a fully seamless experience with all other ApexSQL apps.

Fixing all reported issues

Streamlining the implementation of source control, to make it simpler and work better.

Adding some features like native source control drivers (Vault, Subversion, Team Foundation Server), Debugging and Profiling. The good news is all of this technology has *already* been built and tested and just needs to be rolled out. This doesn't mean it will be released immediately but does mean we won't have to start a dev cycle to build these.

In the interim we'll be accepting any and all constructive feedback on the forum. We are interested in your thoughts, suggestions and ideas on the ApexSQL Edit forum.

Specific business, comments, suggestions, complaints etc can be directed to myself. I understand and appreciate a lot of people's frustration with the delays. I wish this transition had taken place 6 mos. (or 2 years) earlier myself.

In an interesting historical note, ApexSQL Log was acquired in a similar way and now is one of our best selling products. It's quality and performance are top notch and it's outlived it's peers at Lumigent and Red-Gate. ApexSQL Log is now the unquestioned best Log Reader in the SQL market. My goal is to say the same thing about ApexSQL Edit very soon.

Your patience and continued support is very much appreciated.

Labels: Announcement, ApexSQL, ApexSQL Edit

...

posted by Brian Lockwood on Monday, April 07, 2008 0 comments

Product Update Alert - ApexSQL Edit 2005.30.0145

A Minor Fix version of ApexSQL Edit 2005.30.0145 has been released.

Use the following link for downloading.
Auto-updater should work on this build.

Here are the complete release notes for the new version.

Product Update Alerts will be posted on this blog. For automatic notification pls subscribe to RSS Feed.
The product will also automatically check for and notify users of new versions (as well as allow for automatic update via the application interface).