Bug in Ent Mgr Maintenance Plan Wizard if MSDE vs SQL

I have seen this "bug" many times personally, but cannot seem to find any posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT include licence for Enterprize Manager (EM)... but any technician who does have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access Licence) does have Enterprize Manag
er and can connect and manage MSDE and SQL engines/servers equally well.
Consider http://support.microsoft.com/default...22&Product=sql Here we see substantiation that one "can" use EM and Maintenance Plans on MSDE, albeit that you had better be the latest Service Pack since the sqlmaint feature was over
looked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for Database Backup, Transaction Backup (and Log text files). This is important because unless you can also choose to do so, one will end up filling the hard disk with far too many SQL
dumps.
If connected to an SQL server... the option works fine. If connected to an MSDE, the option fails to provie the drop-down for days/weeks and the resulting job created has bugs in the command line options of the job step which one must then go and manuall
y tweak to be correct (never report a bug without a workaround eh? ;-P)
John,
As far as im aware this happens because the maintenance wizard
(sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
instance registry location.
(I would maybe do this on a test machine first if possible or make sure you
have backups)
So firstly make sure the following backup folder path exists , if not create
it :
c:\program files\microsoft sql server\<MSDE instance>\Backup.
Then in regedit:
HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
there should be a BackupDirectory string value , the value data should be
the physical path to the backup folder in our case c:\program
files\microsoft sql server\<MSDE instance>\Backup.
HTH
Dylan
"John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
> I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
> Consider
http://support.microsoft.com/default...22&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
|||Thanks for the thought. No that's not what I mean (see my additional post
in next thread). About the backup folder here is what I did discover the
hard way..
When creating the Maintenance Plan...if one chooses "use the default backup
directory" then it seems to work, and the (first) backup will create the
folder path even if it did not yet exist. However if you specify a "use
this directory" to backup to... then I have found that folder you specify
had better exist already because the backup job will fail rather than create
it. So there's a little idiosyncracy for ya. (I have not experienced the
issue you mention, but perhaps that is an issue if the SQL is installed as a
"named" instance of SQL instead of the default/single instance of SQL? in
which case thank you for the additional tweaks)
John D. Sullivan
ABELSoft Corporation
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:OQXmdsjaEHA.3596@.tk2msftngp13.phx.gbl...
> John,
> As far as im aware this happens because the maintenance wizard
> (sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
> instance registry location.
> (I would maybe do this on a test machine first if possible or make sure
you
> have backups)
> So firstly make sure the following backup folder path exists , if not
create[vbcol=seagreen]
> it :
> c:\program files\microsoft sql server\<MSDE instance>\Backup.
> Then in regedit:
> HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
> there should be a BackupDirectory string value , the value data should be
> the physical path to the backup folder in our case c:\program
> files\microsoft sql server\<MSDE instance>\Backup.
> HTH
> Dylan
>
>
> "John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
> message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
any[vbcol=seagreen]
> posting on the Internet about it. I have many customers using MSDE
Enterprise[vbcol=seagreen]
> Manager when connecting to MSDE.
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> http://support.microsoft.com/default...22&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> an MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
>