Sign In
SQL Server Express WebLog
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Tags
Archive
FAQ
Futures
General
Headlines
Installation
localdb
Pages
Product Info
Samples
Archive
Archives
December 2011
(2)
November 2011
(2)
October 2011
(2)
July 2011
(1)
March 2011
(1)
April 2010
(2)
February 2010
(2)
December 2009
(1)
November 2009
(1)
September 2009
(3)
August 2009
(3)
July 2009
(2)
June 2009
(3)
May 2009
(4)
April 2009
(1)
December 2008
(2)
November 2008
(2)
October 2008
(1)
September 2008
(1)
August 2008
(5)
June 2008
(1)
February 2008
(3)
December 2007
(1)
November 2007
(1)
August 2007
(3)
March 2007
(2)
February 2007
(1)
January 2007
(2)
December 2006
(1)
November 2006
(4)
October 2006
(2)
September 2006
(2)
August 2006
(4)
July 2006
(3)
June 2006
(6)
May 2006
(1)
April 2006
(5)
March 2006
(6)
February 2006
(1)
January 2006
(3)
December 2005
(2)
November 2005
(3)
September 2005
(3)
May 2005
(2)
December 2004
(1)
October 2004
(1)
September 2004
(1)
August 2004
(1)
July 2004
(18)
Introducing SQL Server Express Manager
MSDN Blogs
>
SQL Server Express WebLog
>
Introducing SQL Server Express Manager
Introducing SQL Server Express Manager
sqlexpress
2 Jul 2004 11:46 PM
Comments
41
For those of you who are interested in database management tools for SQL Express, I’d like to tell you about a new product that Microsoft will be releasing soon called SQL Server Express Manager (or XM for short). XM is a lightweight tool built on top of the latest version of the .NET Framework and the new SQL Server System Management Objects API. We received a lot of interest from MSDE customers for a better database management experience and we are hoping to provide that with the release of XM.
A little background on XM…
The inspiration for developing this tool came directly from customer feedback. By talking to MSDE users, we learned that in order to make SQL Server Express a successful product, we needed to provide an easy way for customers to manage their databases. For example of a feature that was implemented in direct response to a customer request is XM’s ability to connect to and managed both local and remote SQL Server instances.
Another significant result from the feedback that we received was that it reinforced the importance of designing XM with simplicity of use in mind. We want XM to be a tool that any database developer can get value out of so to that end, we have tried to optimize XM to be easy to install, easy to understand, and available to anyone. Some of the new usability features include step by step wizards to guide users through common tasks and a simplified tree view of the database objects in addition to standard functionality such as a T-SQL editor with syntax-highlighting. Like SQL Express, XM will also be freely downloadable and redistributable.
We expect to ship the first preview release of XM in time for Yukon Beta 3 but we are making every effort to provide this tool to customers earlier in the fall. Customers have also expressed an interest in more frequent product releases so we are planning to ship additional preview releases with updates to XM every 6 – 12 weeks. Our hope is this increased ship frequency will allow us to respond to customer requests more quickly.
We’d love to hear your thoughts on what features you would like to see in XM and how frequent you would like to have access to updates to the tool. If you’re interested in additional information, I will be updating this blog periodically with the latest status on XM.
I hope you’ve found this information useful and I look forward to writing to you again.
Thanks for all your time,
Eric Feng
Program Manager for SQL Server Express
41 Comments
Archive
Blog - Comment List MSDN TechNet
Comments
Loading...
Leave a Comment
Name
Comment
Please add 5 and 5 and type the answer here:
Post