MSDE and Enterprise Manager

If you have a machine running MSDE and you use Enterprise
Manager to connect to it, should you be able to set up
database maintenance plans that will delete expired
backups?
I'm seeing a situation where you can set up the
maintenance plan but the drop down box for the type of
period (days, weeks, etc) after which to delete expired
backups is blank.
My first thought is that there's an issue with using EM
to set up maintenance plans on MSDE.
Thanks for any assistance.
hi Charles,
"Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> If you have a machine running MSDE and you use Enterprise
> Manager to connect to it, should you be able to set up
> database maintenance plans that will delete expired
> backups?
> I'm seeing a situation where you can set up the
> maintenance plan but the drop down box for the type of
> period (days, weeks, etc) after which to delete expired
> backups is blank.
> My first thought is that there's an issue with using EM
> to set up maintenance plans on MSDE.
> Thanks for any assistance.
unfortunately, your first thought should be that you are not licensed to use
Enterprise Manager against MSDE instances, and you should rely on self based
solutions or third party tools
(http://www.microsoft.com/sql/msde/partners/default.asp or
http://www.aspfaq.com/show.asp?id=2442 , google for others)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for your message. My understanding of the licensing is you can use
Enterprise Manager IF you own a copy of SQL Server Standard or greater. If my
understanding is correct, then the issue goes back to functionality. Do you
agree?
In case you are wondering, you might use MSDE even if you have an installed
version of SQL Server if the application you are using is based on one or the
other. Great Plains, for example, knows which one you are using and has
specific licenses.
"Andrea Montanari" wrote:

> hi Charles,
> "Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
> news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> unfortunately, your first thought should be that you are not licensed to use
> Enterprise Manager against MSDE instances, and you should rely on self based
> solutions or third party tools
> (http://www.microsoft.com/sql/msde/partners/default.asp or
> http://www.aspfaq.com/show.asp?id=2442 , google for others)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||That's not quite correct. The Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp says the following:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
The key phrase here is "using MSDE in conjuntion with a properly licensed
copy of SQL Server 2000." Simply owning a copy of SQL Server Standard
Edition isn't enough, and you'll have to talk to your laywer to figure out
what that phrase means. All I've been told is that it doesn't apply in most
cases and requires a room full of lawyers and a white board to understand.
Rather than go through all that, you're probably better off putting Andrea's
suggestion to work and using a third-party tool.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charles Allen" <CharlesAllen@.discussions.microsoft.com> wrote in message
news:18142445-2FBB-43EC-9719-8751C5AC767D@.microsoft.com...[vbcol=seagreen]
> Thanks for your message. My understanding of the licensing is you can use
> Enterprise Manager IF you own a copy of SQL Server Standard or greater. If
> my
> understanding is correct, then the issue goes back to functionality. Do
> you
> agree?
> In case you are wondering, you might use MSDE even if you have an
> installed
> version of SQL Server if the application you are using is based on one or
> the
> other. Great Plains, for example, knows which one you are using and has
> specific licenses.
> "Andrea Montanari" wrote:
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end

MSDE 2000 & SQL Server 7 installed together?

Hi group!
I'm developing an application using Access/SQL Server.
The end client (government...) only has SQL server 7
installed and has not plans to upgrade in the development
timeframe.
I'd like to use SQL Server 2000 functions in my app. So
I'm wondering if I can reccomend an installation of MSDE
2000 alongside their SLQ server 7.
Is this technically possible?
If not, I'll have to rethink my design and do it in SQL
Server 7.
TIA
Andrew
hi Andrew,
"Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> Hi group!
> I'm developing an application using Access/SQL Server.
> The end client (government...) only has SQL server 7
> installed and has not plans to upgrade in the development
> timeframe.
> I'd like to use SQL Server 2000 functions in my app. So
> I'm wondering if I can reccomend an installation of MSDE
> 2000 alongside their SLQ server 7.
> Is this technically possible?
> If not, I'll have to rethink my design and do it in SQL
> Server 7.
MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
relative mix, can coexiste on the same server...
the 7.0 code based server will be the default instance while the 2000 code
based server(s) have to be named instances.. up to 16 different isntances of
SQL Server 2000/MSDE 2000 can be (technically) hosted on the same sarver...
MDAC stack will be updated at 2.6 version (minimum requirement for SQL
Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
which I strongly recommend.
if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
7.0 edition should be unusable as the COM binaries will be replaced with the
higher version, and only 2000 based tools will be available for management..
one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
Analyzer and so on) but only the COM objects they rely on... so I really
have no idea (never tried myself) what the end position will be...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for that - I've now got access to a machine with SQL 7.0 on it, so I
can have a go at the installation and see how it works.
Andrew
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2qojtiF127domU1@.uni-berlin.de...
> hi Andrew,
> "Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
> news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
> relative mix, can coexiste on the same server...
> the 7.0 code based server will be the default instance while the 2000 code
> based server(s) have to be named instances.. up to 16 different isntances
of
> SQL Server 2000/MSDE 2000 can be (technically) hosted on the same
sarver...
> MDAC stack will be updated at 2.6 version (minimum requirement for SQL
> Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
> which I strongly recommend.
> if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
> 7.0 edition should be unusable as the COM binaries will be replaced with
the
> higher version, and only 2000 based tools will be available for
management..
> one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
> Analyzer and so on) but only the COM objects they rely on... so I really
> have no idea (never tried myself) what the end position will be...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

MSDb and Master maintenance

Using the Database Maintenenace Plan Wizard I set up
maintenance plans for each of the databases on my MS SQL
Server. This is working fine except for the "msdb"
and "master" databases. For these I get the following
errors. What am I doing wrong?
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
You probably try to do log backups. You can't do log backup on master. You can on model, but that is
overkill and would require setting it to full recovery mode. I suggest you create two plans, One in
which you do log backup, another in which you don't.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <schuster@.llnl.gov> wrote in message news:4aa201c49f30$4fc629d0$a601280a@.phx.gbl...
> Using the Database Maintenenace Plan Wizard I set up
> maintenance plans for each of the databases on my MS SQL
> Server. This is working fine except for the "msdb"
> and "master" databases. For these I get the following
> errors. What am I doing wrong?
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> ----
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

MSDb and Master maintenance

Using the Database Maintenenace Plan Wizard I set up
maintenance plans for each of the databases on my MS SQL
Server. This is working fine except for the "msdb"
and "master" databases. For these I get the following
errors. What am I doing wrong?
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 8:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
----
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
(trusted)
Starting maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:01 AM
[1] Database msdb: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub
task is ignored.
End of maintenance plan 'DB Maintenance Plan msdb' on
9/20/2004 4:00:02 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)You probably try to do log backups. You can't do log backup on master. You can on model, but that is
overkill and would require setting it to full recovery mode. I suggest you create two plans, One in
which you do log backup, another in which you don't.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <schuster@.llnl.gov> wrote in message news:4aa201c49f30$4fc629d0$a601280a@.phx.gbl...
> Using the Database Maintenenace Plan Wizard I set up
> maintenance plans for each of the databases on my MS SQL
> Server. This is working fine except for the "msdb"
> and "master" databases. For these I get the following
> errors. What am I doing wrong?
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 8:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> ----
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged
> on to SQL Server 'EPDDOCS3' as 'NT AUTHORITY\SYSTEM'
> (trusted)
> Starting maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:01 AM
> [1] Database msdb: Check Data and Index Linkage...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub
> task is ignored.
> End of maintenance plan 'DB Maintenance Plan msdb' on
> 9/20/2004 4:00:02 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>