I am using Enterprise manager on one server to manage SQL (MSDE) running on
another server. Am I OK so far?
When I create a maintenance plan for all databases on the MSDE server, and
set it for keeping the backup for X days, next the dropdown box which
should, I think, give options of hours, days, etc. is blank. Also, when I
put the ext3ension in as, say bak, save t6he plan then go back into it to
look at its properties, both my schedule and the extension are blank.
Any ideas ? Or, am I wrong to use EM for MSDE ?
Thanks
As far as the license issue, I am still confused by when you can and cannot
use MSDE and Enterprise Mangler together. The safest thing is to either:
A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
normally runs against MSDE onto a single Standard (soon to be Workgroup)
edition of SQL Server.
B) Use SQL Web Administrator
(http://www.microsoft.com/downloads/d...displaylang=en).
It's free and it's legal.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>I am using Enterprise manager on one server to manage SQL (MSDE) running on
> another server. Am I OK so far?
> When I create a maintenance plan for all databases on the MSDE server, and
> set it for keeping the backup for X days, next the dropdown box which
> should, I think, give options of hours, days, etc. is blank. Also, when I
> put the ext3ension in as, say bak, save t6he plan then go back into it to
> look at its properties, both my schedule and the extension are blank.
> Any ideas ? Or, am I wrong to use EM for MSDE ?
> Thanks
|||I am not as concerned with licensing as I am with the technical feasibilty of
using EM to set up maintenance plans for a machine running MSDE as opposed to
full SQL. It seems like it just doesn't work with MSDE and that may be by
design.
"Geoff N. Hiten" wrote:
> As far as the license issue, I am still confused by when you can and cannot
> use MSDE and Enterprise Mangler together. The safest thing is to either:
> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
> normally runs against MSDE onto a single Standard (soon to be Workgroup)
> edition of SQL Server.
> B) Use SQL Web Administrator
> (http://www.microsoft.com/downloads/d...displaylang=en).
> It's free and it's legal.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Adminstrator
>
> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>
>
|||Technically, you can use Enterprise Manager with MSDE. Even with EM, the
wizards may not work correctly with MSDE. The latest Books On-Line contains
much better content on MSDE than the original release BOL. You can download
it here:
http://www.microsoft.com/sql/techinf...2000/books.asp
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:5B0A3223-1555-4532-B012-9BF782154AA6@.microsoft.com...[vbcol=seagreen]
>I am not as concerned with licensing as I am with the technical feasibilty
>of
> using EM to set up maintenance plans for a machine running MSDE as opposed
> to
> full SQL. It seems like it just doesn't work with MSDE and that may be by
> design.
>
> "Geoff N. Hiten" wrote:
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Friday, March 30, 2012
Maintenance plan issue
I am using Enterprise manager on one server to manage SQL (MSDE) running on
another server. Am I OK so far?
When I create a maintenance plan for all databases on the MSDE server, and
set it for keeping the backup for X days, next the dropdown box which
should, I think, give options of hours, days, etc. is blank. Also, when I
put the ext3ension in as, say bak, save t6he plan then go back into it to
look at its properties, both my schedule and the extension are blank.
Any ideas ? Or, am I wrong to use EM for MSDE '
ThanksAs far as the license issue, I am still confused by when you can and cannot
use MSDE and Enterprise Mangler together. The safest thing is to either:
A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
normally runs against MSDE onto a single Standard (soon to be Workgroup)
edition of SQL Server.
B) Use SQL Web Administrator
(http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
It's free and it's legal.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>I am using Enterprise manager on one server to manage SQL (MSDE) running on
> another server. Am I OK so far?
> When I create a maintenance plan for all databases on the MSDE server, and
> set it for keeping the backup for X days, next the dropdown box which
> should, I think, give options of hours, days, etc. is blank. Also, when I
> put the ext3ension in as, say bak, save t6he plan then go back into it to
> look at its properties, both my schedule and the extension are blank.
> Any ideas ? Or, am I wrong to use EM for MSDE '
> Thanks|||I am not as concerned with licensing as I am with the technical feasibilty of
using EM to set up maintenance plans for a machine running MSDE as opposed to
full SQL. It seems like it just doesn't work with MSDE and that may be by
design.
"Geoff N. Hiten" wrote:
> As far as the license issue, I am still confused by when you can and cannot
> use MSDE and Enterprise Mangler together. The safest thing is to either:
> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
> normally runs against MSDE onto a single Standard (soon to be Workgroup)
> edition of SQL Server.
> B) Use SQL Web Administrator
> (http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
> It's free and it's legal.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Adminstrator
>
> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
> >I am using Enterprise manager on one server to manage SQL (MSDE) running on
> > another server. Am I OK so far?
> >
> > When I create a maintenance plan for all databases on the MSDE server, and
> > set it for keeping the backup for X days, next the dropdown box which
> > should, I think, give options of hours, days, etc. is blank. Also, when I
> > put the ext3ension in as, say bak, save t6he plan then go back into it to
> > look at its properties, both my schedule and the extension are blank.
> > Any ideas ? Or, am I wrong to use EM for MSDE '
> >
> > Thanks
>
>|||Technically, you can use Enterprise Manager with MSDE. Even with EM, the
wizards may not work correctly with MSDE. The latest Books On-Line contains
much better content on MSDE than the original release BOL. You can download
it here:
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:5B0A3223-1555-4532-B012-9BF782154AA6@.microsoft.com...
>I am not as concerned with licensing as I am with the technical feasibilty
>of
> using EM to set up maintenance plans for a machine running MSDE as opposed
> to
> full SQL. It seems like it just doesn't work with MSDE and that may be by
> design.
>
> "Geoff N. Hiten" wrote:
>> As far as the license issue, I am still confused by when you can and
>> cannot
>> use MSDE and Enterprise Mangler together. The safest thing is to either:
>> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff
>> that
>> normally runs against MSDE onto a single Standard (soon to be Workgroup)
>> edition of SQL Server.
>> B) Use SQL Web Administrator
>> (http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
>> It's free and it's legal.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Adminstrator
>>
>> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
>> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>> >I am using Enterprise manager on one server to manage SQL (MSDE) running
>> >on
>> > another server. Am I OK so far?
>> >
>> > When I create a maintenance plan for all databases on the MSDE server,
>> > and
>> > set it for keeping the backup for X days, next the dropdown box which
>> > should, I think, give options of hours, days, etc. is blank. Also,
>> > when I
>> > put the ext3ension in as, say bak, save t6he plan then go back into it
>> > to
>> > look at its properties, both my schedule and the extension are blank.
>> > Any ideas ? Or, am I wrong to use EM for MSDE '
>> >
>> > Thanks
>>
another server. Am I OK so far?
When I create a maintenance plan for all databases on the MSDE server, and
set it for keeping the backup for X days, next the dropdown box which
should, I think, give options of hours, days, etc. is blank. Also, when I
put the ext3ension in as, say bak, save t6he plan then go back into it to
look at its properties, both my schedule and the extension are blank.
Any ideas ? Or, am I wrong to use EM for MSDE '
ThanksAs far as the license issue, I am still confused by when you can and cannot
use MSDE and Enterprise Mangler together. The safest thing is to either:
A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
normally runs against MSDE onto a single Standard (soon to be Workgroup)
edition of SQL Server.
B) Use SQL Web Administrator
(http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
It's free and it's legal.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>I am using Enterprise manager on one server to manage SQL (MSDE) running on
> another server. Am I OK so far?
> When I create a maintenance plan for all databases on the MSDE server, and
> set it for keeping the backup for X days, next the dropdown box which
> should, I think, give options of hours, days, etc. is blank. Also, when I
> put the ext3ension in as, say bak, save t6he plan then go back into it to
> look at its properties, both my schedule and the extension are blank.
> Any ideas ? Or, am I wrong to use EM for MSDE '
> Thanks|||I am not as concerned with licensing as I am with the technical feasibilty of
using EM to set up maintenance plans for a machine running MSDE as opposed to
full SQL. It seems like it just doesn't work with MSDE and that may be by
design.
"Geoff N. Hiten" wrote:
> As far as the license issue, I am still confused by when you can and cannot
> use MSDE and Enterprise Mangler together. The safest thing is to either:
> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
> normally runs against MSDE onto a single Standard (soon to be Workgroup)
> edition of SQL Server.
> B) Use SQL Web Administrator
> (http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
> It's free and it's legal.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Adminstrator
>
> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
> >I am using Enterprise manager on one server to manage SQL (MSDE) running on
> > another server. Am I OK so far?
> >
> > When I create a maintenance plan for all databases on the MSDE server, and
> > set it for keeping the backup for X days, next the dropdown box which
> > should, I think, give options of hours, days, etc. is blank. Also, when I
> > put the ext3ension in as, say bak, save t6he plan then go back into it to
> > look at its properties, both my schedule and the extension are blank.
> > Any ideas ? Or, am I wrong to use EM for MSDE '
> >
> > Thanks
>
>|||Technically, you can use Enterprise Manager with MSDE. Even with EM, the
wizards may not work correctly with MSDE. The latest Books On-Line contains
much better content on MSDE than the original release BOL. You can download
it here:
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:5B0A3223-1555-4532-B012-9BF782154AA6@.microsoft.com...
>I am not as concerned with licensing as I am with the technical feasibilty
>of
> using EM to set up maintenance plans for a machine running MSDE as opposed
> to
> full SQL. It seems like it just doesn't work with MSDE and that may be by
> design.
>
> "Geoff N. Hiten" wrote:
>> As far as the license issue, I am still confused by when you can and
>> cannot
>> use MSDE and Enterprise Mangler together. The safest thing is to either:
>> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff
>> that
>> normally runs against MSDE onto a single Standard (soon to be Workgroup)
>> edition of SQL Server.
>> B) Use SQL Web Administrator
>> (http://www.microsoft.com/downloads/details.aspx?FamilyID=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en).
>> It's free and it's legal.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Adminstrator
>>
>> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
>> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>> >I am using Enterprise manager on one server to manage SQL (MSDE) running
>> >on
>> > another server. Am I OK so far?
>> >
>> > When I create a maintenance plan for all databases on the MSDE server,
>> > and
>> > set it for keeping the backup for X days, next the dropdown box which
>> > should, I think, give options of hours, days, etc. is blank. Also,
>> > when I
>> > put the ext3ension in as, say bak, save t6he plan then go back into it
>> > to
>> > look at its properties, both my schedule and the extension are blank.
>> > Any ideas ? Or, am I wrong to use EM for MSDE '
>> >
>> > Thanks
>>
Maintenance plan issue
I am using Enterprise manager on one server to manage SQL (MSDE) running on
another server. Am I OK so far?
When I create a maintenance plan for all databases on the MSDE server, and
set it for keeping the backup for X days, next the dropdown box which
should, I think, give options of hours, days, etc. is blank. Also, when I
put the ext3ension in as, say bak, save t6he plan then go back into it to
look at its properties, both my schedule and the extension are blank.
Any ideas ? Or, am I wrong to use EM for MSDE '
ThanksAs far as the license issue, I am still confused by when you can and cannot
use MSDE and Enterprise Mangler together. The safest thing is to either:
A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
normally runs against MSDE onto a single Standard (soon to be Workgroup)
edition of SQL Server.
B) Use SQL Web Administrator
(2A332CB7F959&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en).
It's free and it's legal.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>I am using Enterprise manager on one server to manage SQL (MSDE) running on
> another server. Am I OK so far?
> When I create a maintenance plan for all databases on the MSDE server, and
> set it for keeping the backup for X days, next the dropdown box which
> should, I think, give options of hours, days, etc. is blank. Also, when I
> put the ext3ension in as, say bak, save t6he plan then go back into it to
> look at its properties, both my schedule and the extension are blank.
> Any ideas ? Or, am I wrong to use EM for MSDE '
> Thanks|||I am not as concerned with licensing as I am with the technical feasibilty o
f
using EM to set up maintenance plans for a machine running MSDE as opposed t
o
full SQL. It seems like it just doesn't work with MSDE and that may be by
design.
"Geoff N. Hiten" wrote:
> As far as the license issue, I am still confused by when you can and canno
t
> use MSDE and Enterprise Mangler together. The safest thing is to either:
> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
> normally runs against MSDE onto a single Standard (soon to be Workgroup)
> edition of SQL Server.
> B) Use SQL Web Administrator
> (C-2A332CB7F959&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en).
> It's free and it's legal.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Adminstrator
>
> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>
>|||Technically, you can use Enterprise Manager with MSDE. Even with EM, the
wizards may not work correctly with MSDE. The latest Books On-Line contains
much better content on MSDE than the original release BOL. You can download
it here:
http://www.microsoft.com/sql/techin.../2000/books.asp
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:5B0A3223-1555-4532-B012-9BF782154AA6@.microsoft.com...[vbcol=seagreen]
>I am not as concerned with licensing as I am with the technical feasibilty
>of
> using EM to set up maintenance plans for a machine running MSDE as opposed
> to
> full SQL. It seems like it just doesn't work with MSDE and that may be by
> design.
>
> "Geoff N. Hiten" wrote:
>
another server. Am I OK so far?
When I create a maintenance plan for all databases on the MSDE server, and
set it for keeping the backup for X days, next the dropdown box which
should, I think, give options of hours, days, etc. is blank. Also, when I
put the ext3ension in as, say bak, save t6he plan then go back into it to
look at its properties, both my schedule and the extension are blank.
Any ideas ? Or, am I wrong to use EM for MSDE '
ThanksAs far as the license issue, I am still confused by when you can and cannot
use MSDE and Enterprise Mangler together. The safest thing is to either:
A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
normally runs against MSDE onto a single Standard (soon to be Workgroup)
edition of SQL Server.
B) Use SQL Web Administrator
(2A332CB7F959&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en).
It's free and it's legal.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>I am using Enterprise manager on one server to manage SQL (MSDE) running on
> another server. Am I OK so far?
> When I create a maintenance plan for all databases on the MSDE server, and
> set it for keeping the backup for X days, next the dropdown box which
> should, I think, give options of hours, days, etc. is blank. Also, when I
> put the ext3ension in as, say bak, save t6he plan then go back into it to
> look at its properties, both my schedule and the extension are blank.
> Any ideas ? Or, am I wrong to use EM for MSDE '
> Thanks|||I am not as concerned with licensing as I am with the technical feasibilty o
f
using EM to set up maintenance plans for a machine running MSDE as opposed t
o
full SQL. It seems like it just doesn't work with MSDE and that may be by
design.
"Geoff N. Hiten" wrote:
> As far as the license issue, I am still confused by when you can and canno
t
> use MSDE and Enterprise Mangler together. The safest thing is to either:
> A) Do not use MSDE. Personally, I consolidate all back-end SQL stuff that
> normally runs against MSDE onto a single Standard (soon to be Workgroup)
> edition of SQL Server.
> B) Use SQL Web Administrator
> (C-2A332CB7F959&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en).
> It's free and it's legal.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Adminstrator
>
> "Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
> news:4EDBBC5E-C589-47E6-AF8B-54FE78F6C510@.microsoft.com...
>
>|||Technically, you can use Enterprise Manager with MSDE. Even with EM, the
wizards may not work correctly with MSDE. The latest Books On-Line contains
much better content on MSDE than the original release BOL. You can download
it here:
http://www.microsoft.com/sql/techin.../2000/books.asp
"Dave Mc" <DaveMc@.discussions.microsoft.com> wrote in message
news:5B0A3223-1555-4532-B012-9BF782154AA6@.microsoft.com...[vbcol=seagreen]
>I am not as concerned with licensing as I am with the technical feasibilty
>of
> using EM to set up maintenance plans for a machine running MSDE as opposed
> to
> full SQL. It seems like it just doesn't work with MSDE and that may be by
> design.
>
> "Geoff N. Hiten" wrote:
>
maintenance plan in enterprise manager not functioning quite right
hello,
wondering if anyone could give me some insight. i've created two
maintenance plans for each of two sql servers (production and test). the
first of each is supposed to check the master, model, and msdb dbs and then
do a complete backup of them as well as their transaction logs. the second
of each does the same for all my user dbs.
all dbs are set to recovery model full except for the master and msdb dbs.
the plan is basically working, except that it is skipping a few of the user
dbs, and it is also skipping the master and msdb dbs on both servers. that
is, i see no mention of them in the logs, and no backup files are created on
disk.
what am i doing wrong?
appreciated,
matthew
Well it can't issue a log backup on Master and MSDB since they are in simple
mode. My guess is the others are as well.
Andrew J. Kelly SQL MVP
"matthew c. harad" <matthewcharad@.discussions.microsoft.com> wrote in
message news:8EC5F016-98C3-4712-8F4D-F1B84B2A20E5@.microsoft.com...
> hello,
> wondering if anyone could give me some insight. i've created two
> maintenance plans for each of two sql servers (production and test). the
> first of each is supposed to check the master, model, and msdb dbs and
then
> do a complete backup of them as well as their transaction logs. the
second
> of each does the same for all my user dbs.
> all dbs are set to recovery model full except for the master and msdb dbs.
> the plan is basically working, except that it is skipping a few of the
user
> dbs, and it is also skipping the master and msdb dbs on both servers.
that
> is, i see no mention of them in the logs, and no backup files are created
on
> disk.
> what am i doing wrong?
> appreciated,
> matthew
wondering if anyone could give me some insight. i've created two
maintenance plans for each of two sql servers (production and test). the
first of each is supposed to check the master, model, and msdb dbs and then
do a complete backup of them as well as their transaction logs. the second
of each does the same for all my user dbs.
all dbs are set to recovery model full except for the master and msdb dbs.
the plan is basically working, except that it is skipping a few of the user
dbs, and it is also skipping the master and msdb dbs on both servers. that
is, i see no mention of them in the logs, and no backup files are created on
disk.
what am i doing wrong?
appreciated,
matthew
Well it can't issue a log backup on Master and MSDB since they are in simple
mode. My guess is the others are as well.
Andrew J. Kelly SQL MVP
"matthew c. harad" <matthewcharad@.discussions.microsoft.com> wrote in
message news:8EC5F016-98C3-4712-8F4D-F1B84B2A20E5@.microsoft.com...
> hello,
> wondering if anyone could give me some insight. i've created two
> maintenance plans for each of two sql servers (production and test). the
> first of each is supposed to check the master, model, and msdb dbs and
then
> do a complete backup of them as well as their transaction logs. the
second
> of each does the same for all my user dbs.
> all dbs are set to recovery model full except for the master and msdb dbs.
> the plan is basically working, except that it is skipping a few of the
user
> dbs, and it is also skipping the master and msdb dbs on both servers.
that
> is, i see no mention of them in the logs, and no backup files are created
on
> disk.
> what am i doing wrong?
> appreciated,
> matthew
Maintenance Plan folder not shown in Management Folder
Hi,
I have a problem on just one server : The Management folder in
Enterprise Manager does not contain a folder for Maintenance plans. I
have created a plan by right clicking on a db, all tasks > maintenance
plan, but I have no way of editing this as it is not displayed
anywhere. I know I can edit the individual jobs that appear in the
Jobs folder, but I'd like to know why the maintenance plan folder is
not shown. It's not possible to re-install SQL, I would appreciate any
help.
Thanks
Kev.Perhaps just a refresh problem? Have you tried to restart Enterprise Manager?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kev smart" <kev@.earlshilton.com> wrote in message
news:13f1d9b4.0504040344.640c89ad@.posting.google.com...
> Hi,
> I have a problem on just one server : The Management folder in
> Enterprise Manager does not contain a folder for Maintenance plans. I
> have created a plan by right clicking on a db, all tasks > maintenance
> plan, but I have no way of editing this as it is not displayed
> anywhere. I know I can edit the individual jobs that appear in the
> Jobs folder, but I'd like to know why the maintenance plan folder is
> not shown. It's not possible to re-install SQL, I would appreciate any
> help.
> Thanks
> Kev.|||Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
right in thinking that the maintenance plan option should be added when
applying sp3a?
Thanks
Kev|||I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"nsiadmin" <kev@.earlshilton.com> wrote in message
news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> right in thinking that the maintenance plan option should be added when
> applying sp3a?
> Thanks
> Kev
>|||I applied sp3adesk, wrote output to a log file which ends with
(snip)
Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): QFEUpgrade = 1
Property(C): Preselected = 1
Property(C): ACTION = INSTALL
=== Logging stopped: 4/5/2005 7:18:49 ===MSI (c) (C4:CC): Note: 1: 1728
MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
Configuration completed successfully.
MSI (c) (C4:CC): Grabbed execution mutex.
MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
MSI (c) (C4:CC): MainEngineThread is returning 0
=== Verbose logging stopped: 4/5/2005 7:18:49 ===
Which looks like a successful install, but after rebooting the server and
going back into enterprise manager, there is still no Maintenance Plan folder
and the server properties ( and @.@.version ) show the version as sql2000
8.00.194 RTM as though no service pack installed.
Getting desperate....... Kev.
"Tibor Karaszi" wrote:
> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "nsiadmin" <kev@.earlshilton.com> wrote in message
> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> > right in thinking that the maintenance plan option should be added when
> > applying sp3a?
> >
> > Thanks
> >
> > Kev
> >
>
>|||Have you checked whether the maint wiz is included in msde? I'm not sure it is...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevsmart" <kevsmart@.discussions.microsoft.com> wrote in message
news:711B7170-7B9F-4570-B40B-8023EECD1A56@.microsoft.com...
>I applied sp3adesk, wrote output to a log file which ends with
> (snip)
> Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
> Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
> Property(C): UILevel = 3
> Property(C): QFEUpgrade = 1
> Property(C): Preselected = 1
> Property(C): ACTION = INSTALL
> === Logging stopped: 4/5/2005 7:18:49 ===> MSI (c) (C4:CC): Note: 1: 1728
> MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
> Configuration completed successfully.
> MSI (c) (C4:CC): Grabbed execution mutex.
> MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
> MSI (c) (C4:CC): MainEngineThread is returning 0
> === Verbose logging stopped: 4/5/2005 7:18:49 ===>
> Which looks like a successful install, but after rebooting the server and
> going back into enterprise manager, there is still no Maintenance Plan folder
> and the server properties ( and @.@.version ) show the version as sql2000
> 8.00.194 RTM as though no service pack installed.
>
> Getting desperate....... Kev.
>
> "Tibor Karaszi" wrote:
>> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "nsiadmin" <kev@.earlshilton.com> wrote in message
>> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
>> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
>> > right in thinking that the maintenance plan option should be added when
>> > applying sp3a?
>> >
>> > Thanks
>> >
>> > Kev
>> >
>>|||The wizard is there because it is accessible by right clicking the db name,
all tasks, maintenance plan. However although this creates the plan and jobs,
it wont run because there is no sqlmaint.exe in the binn folder. Once this is
copied in (from any other SQL installation ) the next plan to be created will
generate the Maintenance Plan folder under Management. Problem solved!
Thanks
Kev
"Tibor Karaszi" wrote:
> Have you checked whether the maint wiz is included in msde? I'm not sure it is...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "kevsmart" <kevsmart@.discussions.microsoft.com> wrote in message
> news:711B7170-7B9F-4570-B40B-8023EECD1A56@.microsoft.com...
> >I applied sp3adesk, wrote output to a log file which ends with
> >
> > (snip)
> > Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
> > Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
> > Property(C): UILevel = 3
> > Property(C): QFEUpgrade = 1
> > Property(C): Preselected = 1
> > Property(C): ACTION = INSTALL
> > === Logging stopped: 4/5/2005 7:18:49 ===> > MSI (c) (C4:CC): Note: 1: 1728
> > MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
> > Configuration completed successfully.
> >
> > MSI (c) (C4:CC): Grabbed execution mutex.
> > MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
> > MSI (c) (C4:CC): MainEngineThread is returning 0
> > === Verbose logging stopped: 4/5/2005 7:18:49 ===> >
> >
> > Which looks like a successful install, but after rebooting the server and
> > going back into enterprise manager, there is still no Maintenance Plan folder
> > and the server properties ( and @.@.version ) show the version as sql2000
> > 8.00.194 RTM as though no service pack installed.
> >
> >
> > Getting desperate....... Kev.
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "nsiadmin" <kev@.earlshilton.com> wrote in message
> >> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> >> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> >> > right in thinking that the maintenance plan option should be added when
> >> > applying sp3a?
> >> >
> >> > Thanks
> >> >
> >> > Kev
> >> >
> >>
> >>
> >>
>
>sql
I have a problem on just one server : The Management folder in
Enterprise Manager does not contain a folder for Maintenance plans. I
have created a plan by right clicking on a db, all tasks > maintenance
plan, but I have no way of editing this as it is not displayed
anywhere. I know I can edit the individual jobs that appear in the
Jobs folder, but I'd like to know why the maintenance plan folder is
not shown. It's not possible to re-install SQL, I would appreciate any
help.
Thanks
Kev.Perhaps just a refresh problem? Have you tried to restart Enterprise Manager?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kev smart" <kev@.earlshilton.com> wrote in message
news:13f1d9b4.0504040344.640c89ad@.posting.google.com...
> Hi,
> I have a problem on just one server : The Management folder in
> Enterprise Manager does not contain a folder for Maintenance plans. I
> have created a plan by right clicking on a db, all tasks > maintenance
> plan, but I have no way of editing this as it is not displayed
> anywhere. I know I can edit the individual jobs that appear in the
> Jobs folder, but I'd like to know why the maintenance plan folder is
> not shown. It's not possible to re-install SQL, I would appreciate any
> help.
> Thanks
> Kev.|||Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
right in thinking that the maintenance plan option should be added when
applying sp3a?
Thanks
Kev|||I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"nsiadmin" <kev@.earlshilton.com> wrote in message
news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> right in thinking that the maintenance plan option should be added when
> applying sp3a?
> Thanks
> Kev
>|||I applied sp3adesk, wrote output to a log file which ends with
(snip)
Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): QFEUpgrade = 1
Property(C): Preselected = 1
Property(C): ACTION = INSTALL
=== Logging stopped: 4/5/2005 7:18:49 ===MSI (c) (C4:CC): Note: 1: 1728
MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
Configuration completed successfully.
MSI (c) (C4:CC): Grabbed execution mutex.
MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
MSI (c) (C4:CC): MainEngineThread is returning 0
=== Verbose logging stopped: 4/5/2005 7:18:49 ===
Which looks like a successful install, but after rebooting the server and
going back into enterprise manager, there is still no Maintenance Plan folder
and the server properties ( and @.@.version ) show the version as sql2000
8.00.194 RTM as though no service pack installed.
Getting desperate....... Kev.
"Tibor Karaszi" wrote:
> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "nsiadmin" <kev@.earlshilton.com> wrote in message
> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> > right in thinking that the maintenance plan option should be added when
> > applying sp3a?
> >
> > Thanks
> >
> > Kev
> >
>
>|||Have you checked whether the maint wiz is included in msde? I'm not sure it is...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"kevsmart" <kevsmart@.discussions.microsoft.com> wrote in message
news:711B7170-7B9F-4570-B40B-8023EECD1A56@.microsoft.com...
>I applied sp3adesk, wrote output to a log file which ends with
> (snip)
> Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
> Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
> Property(C): UILevel = 3
> Property(C): QFEUpgrade = 1
> Property(C): Preselected = 1
> Property(C): ACTION = INSTALL
> === Logging stopped: 4/5/2005 7:18:49 ===> MSI (c) (C4:CC): Note: 1: 1728
> MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
> Configuration completed successfully.
> MSI (c) (C4:CC): Grabbed execution mutex.
> MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
> MSI (c) (C4:CC): MainEngineThread is returning 0
> === Verbose logging stopped: 4/5/2005 7:18:49 ===>
> Which looks like a successful install, but after rebooting the server and
> going back into enterprise manager, there is still no Maintenance Plan folder
> and the server properties ( and @.@.version ) show the version as sql2000
> 8.00.194 RTM as though no service pack installed.
>
> Getting desperate....... Kev.
>
> "Tibor Karaszi" wrote:
>> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "nsiadmin" <kev@.earlshilton.com> wrote in message
>> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
>> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
>> > right in thinking that the maintenance plan option should be added when
>> > applying sp3a?
>> >
>> > Thanks
>> >
>> > Kev
>> >
>>|||The wizard is there because it is accessible by right clicking the db name,
all tasks, maintenance plan. However although this creates the plan and jobs,
it wont run because there is no sqlmaint.exe in the binn folder. Once this is
copied in (from any other SQL installation ) the next plan to be created will
generate the Maintenance Plan folder under Management. Problem solved!
Thanks
Kev
"Tibor Karaszi" wrote:
> Have you checked whether the maint wiz is included in msde? I'm not sure it is...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "kevsmart" <kevsmart@.discussions.microsoft.com> wrote in message
> news:711B7170-7B9F-4570-B40B-8023EECD1A56@.microsoft.com...
> >I applied sp3adesk, wrote output to a log file which ends with
> >
> > (snip)
> > Property(C): DATABASE = C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\6c801f.msi
> > Property(C): OriginalDatabase = D:\sql2ksp3\MSDE\Setup\SqlRun01.msi
> > Property(C): UILevel = 3
> > Property(C): QFEUpgrade = 1
> > Property(C): Preselected = 1
> > Property(C): ACTION = INSTALL
> > === Logging stopped: 4/5/2005 7:18:49 ===> > MSI (c) (C4:CC): Note: 1: 1728
> > MSI (c) (C4:CC): Product: Microsoft SQL Server Desktop Engine --
> > Configuration completed successfully.
> >
> > MSI (c) (C4:CC): Grabbed execution mutex.
> > MSI (c) (C4:CC): Cleaning up uninstalled install packages, if any exist
> > MSI (c) (C4:CC): MainEngineThread is returning 0
> > === Verbose logging stopped: 4/5/2005 7:18:49 ===> >
> >
> > Which looks like a successful install, but after rebooting the server and
> > going back into enterprise manager, there is still no Maintenance Plan folder
> > and the server properties ( and @.@.version ) show the version as sql2000
> > 8.00.194 RTM as though no service pack installed.
> >
> >
> > Getting desperate....... Kev.
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I'm not sure, I haven't used EM against MSDE. Give it a spin and see...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "nsiadmin" <kev@.earlshilton.com> wrote in message
> >> news:1112621866.677876.74970@.l41g2000cwc.googlegroups.com...
> >> > Yes, restarted em. Now I find out its SQL 2000 msde with no SP, am I
> >> > right in thinking that the maintenance plan option should be added when
> >> > applying sp3a?
> >> >
> >> > Thanks
> >> >
> >> > Kev
> >> >
> >>
> >>
> >>
>
>sql
Wednesday, March 28, 2012
Maintenance Plan Error
Windows 20003 Enterprise server
SQL 2005 Standard with SP2
When I try and create a maintenance plan either via the wizard or just create new, I get the following error. Can anyone help please. thanks
===================================
Cannot show requested dialog.
===================================
Unable to execute requested command.
Program Location:
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
Method not found: 'Void Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'. (Microsoft.SqlServer.Management.MaintenancePlanWizard)
Program Location:
at Microsoft.SqlServer.Management.MaintenancePlanWizard.MaintenancePlanWizardForm..ctor(XmlDocument doc, IServiceProvider serviceProvider)
Hello Theon,
This sounds like your client tools are older than SP2. The SP2 version of the Microsoft.SqlServer.MaintenancePlanTasks.dll assembly removed the function mentioned in the error message, so that's why the function cannot be found.. Can you check what version of Management Studio you're running, and see if its older than SP2? Also are you running Management Studio on the sql server machine, or connecting to it remotely?
James
|||Here is the version
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790
I am connecting on the server
|||Applied sp2 and all is well thanks|||
Glad to help, Theon.
James
Wednesday, March 7, 2012
MAIL on SQL Server 2000 Standard on Windows Server 2003 64-bit
I've read about 2005 Enterprise Edition 64-bit and 2000 Enterprise Edition 64-bit and those mail issues. But, my particular situation is running SQL Server 2000 Standard Edition (32-bit) on Windows 2003 Server (64-bit). I got the mail profile set up ok for the SQL Server Service Account using Outlook 2000 and can send and receive mail using Outlook. But, even after restarting the SQL Server Services, there's no profile to choose in the SQL Mail or Agent Mail drop-down box. I have tried ON the server and remotely. Locally, the drop-down box doesn't even really 'drop down'. Remotely, I get the drop-down but it is empty. I don't need a primer on configuring SQL Mail for SQL 2000. I just need to know if this combination of SQL Server Editions and OS Editions will even support SQL Mail. Maybe adding the appropriate values in the registry will enable me to use this mail profile for SQL Server?
What about that smtp client that's out there. I've not used it on any machine and don't want to make this goofy one the guinea pig if it hasn't been proven to work.
No, we can't go to SQL Server 2005 yet on this server. It hosts a purchased system that isn't supported on SQL Server 2005.
Thanks for your help,
Michelle
I rebooted the server and was able to configure the mail profile and select it from my client/enterprise manager. It seems like things generally require a reboot more often on this server than I've experienced on other servers. I tested agent mail, xp_sendamail, and dts send mail tasks all to success. Now I'm fighting with installation of the SQL Server Health & History Tool.
Just wanted to document that sql mail DOES seem to work with this configuration. Keep trying and I'm sure that you'll get it to work, too :)
What about that smtp client that's out there. I've not used it on any machine and don't want to make this goofy one the guinea pig if it hasn't been proven to work.
No, we can't go to SQL Server 2005 yet on this server. It hosts a purchased system that isn't supported on SQL Server 2005.
Thanks for your help,
Michelle
I rebooted the server and was able to configure the mail profile and select it from my client/enterprise manager. It seems like things generally require a reboot more often on this server than I've experienced on other servers. I tested agent mail, xp_sendamail, and dts send mail tasks all to success. Now I'm fighting with installation of the SQL Server Health & History Tool.
Just wanted to document that sql mail DOES seem to work with this configuration. Keep trying and I'm sure that you'll get it to work, too :)
Subscribe to:
Posts (Atom)