|
DbaMgr - DbaMgr2K
A little alternative administrative console for Microsoft MSDE 1.0 and MSDE
2000 written in Microsoft Visual Basic 6.0
Foreword
I come from the Jet engine world, from the one part of VB3, but I never had a
copy of Access, what I needed to do was done by Microsoft Visual Basic code and
Visual Data Manager. Later, Microsoft released MSDE and MSDE 2000, so I
recycled myself to these Database Engines. MSDE and MSDE 2000, like their
brothers got a major restyling, in configuration and admin tasks to meet, or
reach, TCO=0 needs (Total Cost of Ownership =0). The bad thing is that
Microsoft does not include any visual tool to manage MSDE and MSDE 2000
installations, only the powerful character-based oSql.exe, a tool not to play
with and not for everyone, at least not for my usual customers... this brings
me to a nice situation.... if my customer do have a Dba among his employees, no
problem, perhaps he owns the major SQL Server engine, but what if no one is a
Dba or a Sa?? can I afford and trust him to type obscure T-Sql commands to
perform simply tasks like Backup/restore or similar? This idea comes to me by
reading Peter Swaniker article (Visual Basic Journal [now Visual Studio
Magazine] july 1999 "Managing SQL Server 7.0"), that unfortunately was
implemented on the NOT redistributable COM Namespace object, so only part of
frmMain is him due, while I'm responsible of the rest... These applications do
not claim to be bug-free, nor to be the 'panacea', but could be of interest for
someone..
More details about DbaMgr and
DbaMgr2k.
DbaMgr and DbaMgr2k provide a graphic management interface for MS MSDE 1.0 and
MSDE 2000 installations. It allows you to manage and administer your server,
databases and database objects from a Windows interface similar to the one
Microsoft Enterprise Manager provides, rather than via the standard oSql.exe
command line utility: an alternative inexpensive console/management tool for
Microsoft SQL Server 7.0/MSDE 1.0 and SQL Server 2000/MSDE2000 respectively,
plus some other functionality.Provided with built-in English and Italian
language localization, support user defined language translation.
DbaMgr2k has been vouluntary split from DbaMgr, becouse it implements some
version "2" of SQL-DMO interfaces available only on SQL Server 2000, and it
woul'd be not possible to be re-compiled from people with only SQL Server 7.0
available.
DbaMgr requires Ado2.5 (MDAC2.5) and portion of SQL Server 7.0 Client
Components containing SQL-DMO;
DbaMgr2k requires Ado2.6 (MDAC2.6) and portion of SQL Server 2000 Client
Components containing SQL-DMO.
SQL Server 7.0 installations require DbaMgr,
that can not connect to SQL Server 2000.
On the contrary, SQL Server 2000 installations require
DbaMgr2k, that can not connect to SQL Server 7.0.
Users that must manage both kind of Server from the same computer, can proceed
with the full installation of DbaMgr2k ,
and then unzip in the same folder the DbaMgr
Update package only; this will work as long as the destination computer has ADO
2.6 (MDAC2.6) and SQL-DMO Client Compenents from SQL Server 2000 installed;
further dependencies are already installed.
|
|
