We create a simple maintenance plan with no error. When we go back to edit the settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (although we can manually enter a number), and the drop-down that should show "hours", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?
Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>
|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>
|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter
Showing posts with label maintenance. Show all posts
Showing posts with label maintenance. Show all posts
Sunday, February 26, 2012
Enterprise Manager Corrupted?
We create a simple maintenance plan with no error. When we go back to edit t
he settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup
files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (althoug
h we can manually enter a number), and the drop-down that should show "hours
", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter|||The SQL Server 2000 instance was originally installed (by another
consultant) last summer. I doubt that any hot fixes were applied before we
came onto the scene in December, since, as you saw, they never got around to
applying SP3.
The master/msdb were installed fresh, I'm sure (the other vendor wasn't
sophisticated enough to know how to do any of that.
Any other thoughts? I'm sort of getting the idea that we probably have no
choice but to rip it out and reinstall?
J
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OHyiE7oGEHA.2052@.TK2MSFTNGP11.phx.gbl...
> What is the database compatibility? What hotfixes have been applied?
Have
> you restored master or msdb from another place or another version?
> I'm just trying to think of things which would make a system-used datatype
> change, and usually these are restricted to service pack/version releases.
> A
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
>
he settings, many have defaulted.
In particular, the backup definition loses the definition of where to backup
files to on the disk is cleared, and the Device option is checked.
Further, in delete files older than, the selector will not populate (althoug
h we can manually enter a number), and the drop-down that should show "hours
", "Days" etc, is completely empty, and we cannot enter anything.
Suggestions?Have your client tools been updated with SP3?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"jnorman" <anonymous@.discussions.microsoft.com> wrote in message
news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
> We create a simple maintenance plan with no error. When we go back to edit
> the settings, many have defaulted.
> In particular, the backup definition loses the definition of where to
> backup files to on the disk is cleared, and the Device option is checked.
> Further, in delete files older than, the selector will not populate
> (although we can manually enter a number), and the drop-down that should
> show "hours", "Days" etc, is completely empty, and we cannot enter
> anything.
> Suggestions?
>|||Good idea. In fact it turns out that, despite assurances
to the contrary, our new client had NOT upgraded to sp3.
So we installed it.
Unfortunately, We still have the same problem. We can
still save an original maintenance plan, although the drop-
down list for the number of time units to delete after is
still blank (it apparently defaults to "weeks," though).
The original save is error-free, but to save any mods
generates this error:
error 8114: error converting data type int to tinyint
We still have no way to simply modify a maintenance plan.
More suggestions?
>--Original Message--
>Have your client tools been updated with SP3?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>"jnorman" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ADE1F886-6641-4741-ABD4-BFED23FD7AED@.microsoft.com...
we go back to edit
definition of where to
option is checked.
not populate
down that should
cannot enter
>
>.
>|||What is the database compatibility? What hotfixes have been applied? Have
you restored master or msdb from another place or another version?
I'm just trying to think of things which would make a system-used datatype
change, and usually these are restricted to service pack/version releases.
A
<anonymous@.discussions.microsoft.com> wrote in message
news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
> Good idea. In fact it turns out that, despite assurances
> to the contrary, our new client had NOT upgraded to sp3.
> So we installed it.
> Unfortunately, We still have the same problem. We can
> still save an original maintenance plan, although the drop-
> down list for the number of time units to delete after is
> still blank (it apparently defaults to "weeks," though).
> The original save is error-free, but to save any mods
> generates this error:
> error 8114: error converting data type int to tinyint
> We still have no way to simply modify a maintenance plan.
> More suggestions?
> message
> we go back to edit
> definition of where to
> option is checked.
> not populate
> down that should
> cannot enter|||The SQL Server 2000 instance was originally installed (by another
consultant) last summer. I doubt that any hot fixes were applied before we
came onto the scene in December, since, as you saw, they never got around to
applying SP3.
The master/msdb were installed fresh, I'm sure (the other vendor wasn't
sophisticated enough to know how to do any of that.
Any other thoughts? I'm sort of getting the idea that we probably have no
choice but to rip it out and reinstall?
J
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OHyiE7oGEHA.2052@.TK2MSFTNGP11.phx.gbl...
> What is the database compatibility? What hotfixes have been applied?
Have
> you restored master or msdb from another place or another version?
> I'm just trying to think of things which would make a system-used datatype
> change, and usually these are restricted to service pack/version releases.
> A
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:153c901c41a8d$122349f0$a601280a@.phx
.gbl...
>
Wednesday, February 15, 2012
Entering maintenance mode through Enterprise Manager?
Is there a way of entering maintenance mode ("-m") through Enterprise
Manager (2000), rather than running sqlservr.exe directly?
Thanks!
You can add it as a start up parameter (right-click your server, startup parameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windows Services applet, and
add the parameter there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
Manager (2000), rather than running sqlservr.exe directly?
Thanks!
You can add it as a start up parameter (right-click your server, startup parameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windows Services applet, and
add the parameter there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
Entering maintenance mode through Enterprise Manager?
Is there a way of entering maintenance mode ("-m") through Enterprise
Manager (2000), rather than running sqlservr.exe directly?
Thanks!You can add it as a start up parameter (right-click your server, startup par
ameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windo
ws Services applet, and
add the parameter there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...[
vbcol=seagreen]
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>[/vbcol]
Manager (2000), rather than running sqlservr.exe directly?
Thanks!You can add it as a start up parameter (right-click your server, startup par
ameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windo
ws Services applet, and
add the parameter there.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...[
vbcol=seagreen]
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>[/vbcol]
Entering maintenance mode through Enterprise Manager?
Is there a way of entering maintenance mode ("-m") through Enterprise
Manager (2000), rather than running sqlservr.exe directly?
Thanks!May be changing the startup parameters from windows "server properties", tab
"General", then stopping and restarting the service.
AMB
"Neil W." wrote:
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
>|||Replied in .server. Please don't multi-post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:u9SHVNk2FHA.1188@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
>
Manager (2000), rather than running sqlservr.exe directly?
Thanks!May be changing the startup parameters from windows "server properties", tab
"General", then stopping and restarting the service.
AMB
"Neil W." wrote:
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
>|||Replied in .server. Please don't multi-post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:u9SHVNk2FHA.1188@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
>
Entering maintenance mode through Enterprise Manager?
Is there a way of entering maintenance mode ("-m") through Enterprise
Manager (2000), rather than running sqlservr.exe directly?
Thanks!You can add it as a start up parameter (right-click your server, startup parameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windows Services applet, and
add the parameter there.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
Manager (2000), rather than running sqlservr.exe directly?
Thanks!You can add it as a start up parameter (right-click your server, startup parameters), these are
stored in the registry. But as this is a one-time, it is easier to use Windows Services applet, and
add the parameter there.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Neil W." <neilw@.netlib.com> wrote in message news:e97bUWk2FHA.1292@.TK2MSFTNGP12.phx.gbl...
> Is there a way of entering maintenance mode ("-m") through Enterprise
> Manager (2000), rather than running sqlservr.exe directly?
> Thanks!
>
Subscribe to:
Posts (Atom)