Enterprise manager settings migration?

Anyone knows if it is at all possible to Copy or Move the Server Registered under EM to another machine ?
ThanksOriginally posted by aashu
Anyone knows if it is at all possible to Copy or Move the Server Registered under EM to another machine ?

Thanks

but if have the registered server on ur EM then u can just use that to register the same servers on another instance of EM... or you could get the information for the server from the Client Network Utility: ipaddresses, servername etc.|||I am aware of that . Doing for 50 Servers will be a nightmare .. So , back to the question again , is there some ini file or EM setup file I could move over?

Thanks|||I know the information about registered servers is in the registry:
HKEY_CURRENT_USER\software\microsoft\microsoft sql server\80\tools\sqlew\registeredservers x

You should be able to export this key with regedt32. If you use regedit, you may only get the directory structure, and none of the data. Hope this helps.|||Thats what I was looking for !|||The same information is in HKEY_USERS\... But you have to guess at what your NT SID is. This is probably the more definitive place to get and store the information, as I think HKEY_CURRENT_USER is cleared when you log out.

As always, modifying your registry can have dire consequences, yadda, yadda, yadda.

enterprise manager settings

hate to sound stupid, but i could not find a place where i could change ansi_nulls, ansi_warnings, quoted_identifiers, etc. for enterprise manager.

a "developer" approached me with this question because he "wants" to be able to create tables and views without having to use query analyzer, but also wants to use specific (not default) settings through enterprise manager.

anyone knows?

thanks in advance.Howdy,

I was sitting here musing over this problem and it occurred to me that if you could set those options in EM, it logically would have to override these settings for every single server registered in EM.

This would cause everything to go nuts as apps failed on some servers and all generally goes to custard ......

Your developer sounds like he needs to read some devlopment books...

Cheers,

SG|||you can cahnge some of those for the default connection properties in the server properties for each server and one or two of them in the properties pages for each database... probably be best off setting them via the system stored procedures, I'm pretty sure you can set some or most of those options on individual databases|||Tell your developer he needs to use QA

EM can get funky...|||yeah, i would have, only if they were not considered "our customers". untill then (or until i get hired by a company that gives due respect to dba's), - i'll have to go to his desk and play tech support level 2... :(|||Judging from all the funky stuff that Enterprise Mangler does, I suspect you could not change these settings, unless you coded your own EM. I have had users create tables called "dbo.table", when they try to specify dbo as the owner of the table. Maybe it is just my programmers, but I agree with the majortiy opnion here. Query Analyzer is the way to go. EM can help with diagrams, but it is not an all inclusive tool.|||Howdy,

For what its worth - at some stage they will eventually have to hear the word "No!!" ...customer or no customer....some things cant be bent... unless of course they want to pay handsomely for it.... ;-)

Stay cool,

Cheers,

SG.

Enterprise Manager Corrupted?

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

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...
>