While this article is geared mainly toward MSDE users, all of the tools described within can, as far as we know, work against regular editions of SQL Server. Some can even work against Access, Oracle, and other database platforms.
MSDE does not include graphical management tools like Enterprise Manager, Query Analyzer, and Profiler. So, you may have a hard time even verifying that the MSDE install went fine, never mind creating databases, objects and users. There are several ways to manage MSDE installations.
Some of the tools listed below are free, others have a range of pricetags. We will try to update the links to indicate which ones are free.
(Please let us know if we missed your favorite product, or if you have a favorable or non-favorable review of any of the tools listed below.)
Existing Client Tools
If you have an existing machine with SQL Server client tools installed, you can manage the MSDE instance through these… as long as you have a valid and legal Client Access License (CAL). You can take the SQL Server install CD, run it on the client(s), and choose “Install client tools only” during setup. This will install Query Analyzer, Enterprise Manager, and other useful toolsâ€â€?but will not install the database engine.
This has been a point of concern in the past, because SQL Server licensing is not cheap. However, Microsoft decided to lower the price of Developer Edition to $49, effective August 2003. See their “how to buy” p… for details. You can install a licensed developer edition on one client, and from there manage your *development* SQL Servers using those client tools. Note that you cannot use developer edition to manage any SQL Server databases in production, including MSDE.
Other Microsoft Tools
The SQL Server Web Data Administrator installs a web-based GUI that you can use to manage your database(s) from anywhere, using only a web browser.
The Visual Studio.NET IDE has a Server Explorer, which allows you to add a SQL Server connection — through which you can create stored procedures, manage tables, and view data. Not all of the administrative tasks you would want to perform against your database, but you can accomplish most development issues.
Similarly, ASP.NET Web Matrix allows partial control over SQL Server and MSDE data sources.
Access 2000 and 2002 will allow you to perform rudimentary data manipulation tasks using pass-through queries.
For complete control over MSDE, you can also write your own applications that manage MSDE objects and data, using SQL-DMO.
You can also use ADOX … see 4GuysFromRolla and the core reference for ADOX [MSDN Online].
Some articles on helping you build your own object/data tools: 15 Seconds and 4guysFromRolla.
OSQL command-line utility
To apply scripts (such as CREATE DATABASE, ALTER TABLE, EXEC sp_adduser, etc) you can use the command-line utility OSQL.exe, which comes with MSDE. To use, simply open a command prompt, and issue something like this:
osql -E -S (local)\instance_name -i c:\yourScript.sql -o c:\output.txt
For an article more deeply describing the use of OSQL, see KB #325003.
For a Microsoft example demonstrating how to backup an MSDE database using OSQL, see KB #241397.
If you’re not familiar with using OSQL, or you are not familiar with generating .sql scripts, then you should have a copy of Books Online handy. See Article #2229 for information on obtaining the most recent version of Books Online.
3rd Party Tools
Some of these applications are web-based, and some are windows-based. All claim to be able to manage at least some aspect of SQL Server installations (and, by extension, MSDE) — be it schema and objects or merely data management. I have not had a chance to review the majority of these tools.
DbaMgr (Andrea Montanari)
DBAMgr (SnapFiles)
MSDE Management Tools (SQL Server 2000 Resource Kit)
MSDE Manager (Vale Software)
MSDE Manager (White Bear Consulting)
Home