![]() | |
![]() |
| | Thread Tools | Display Modes |
#61
| |||
| |||
|
|
I'm not complaining about the nomenclature. I'm complaining about the strictness of where I'm allows to create branches / leaves of the tree. If we were to follow your reasoning, where would one place server registrations contained in XML files that are not local to the machine? Have you tried to create a folder in in branch other that "Local Server Groups"? "Tibor Karaszi" wrote: Perhaps the groups should have been named "Locally Registered Servers Group" and "Remotely Registered Servers Group". I.e., the question isn't whether the servers in the groups are local or not, the question is whether the registration information resides in an XML file locally on your machine or in msdb possibly remotely on some other machine. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Mark H. Shin" <MarkHShin (AT) discussions (DOT) microsoft.com> wrote in message news:E0CA0C5C-1272-4310-AD12-FAF31AF2B9C9 (AT) microsoft (DOT) com... Yes. That is the same problem I'm having, but as you can deduce, most of my SQL server registered servers are "Remote" and should not be filed under "Local Server Groups"... SSMS 2005 allows allowed creation of folders directly under "Database Engine". "Roy Harvey (SQL Server MVP)" wrote: On Fri, 5 Sep 2008 12:43:01 -0700, Mark H. Shin MarkHShin (AT) discussions (DOT) microsoft.com> wrote: Why does SSMS 2008 force ALL new server registrations under "Local Server Group"? In 2005, I could create folders (almost) arbitrarly in the folder tree... Now I cannot create folders where I want to place them! I had no problem creating groups as long as they were somewhere within Local Server Groups. They nested fine. I haven't found a way to move registrations to different groups, or move groups around. Roy Harvey Beacon Falls, CT |
#62
| |||
| |||
|
|
I'm not complaining about the nomenclature. I'm complaining about the strictness of where I'm allows to create branches / leaves of the tree. If we were to follow your reasoning, where would one place server registrations contained in XML files that are not local to the machine? Have you tried to create a folder in in branch other that "Local Server Groups"? "Tibor Karaszi" wrote: Perhaps the groups should have been named "Locally Registered Servers Group" and "Remotely Registered Servers Group". I.e., the question isn't whether the servers in the groups are local or not, the question is whether the registration information resides in an XML file locally on your machine or in msdb possibly remotely on some other machine. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Mark H. Shin" <MarkHShin (AT) discussions (DOT) microsoft.com> wrote in message news:E0CA0C5C-1272-4310-AD12-FAF31AF2B9C9 (AT) microsoft (DOT) com... Yes. That is the same problem I'm having, but as you can deduce, most of my SQL server registered servers are "Remote" and should not be filed under "Local Server Groups"... SSMS 2005 allows allowed creation of folders directly under "Database Engine". "Roy Harvey (SQL Server MVP)" wrote: On Fri, 5 Sep 2008 12:43:01 -0700, Mark H. Shin MarkHShin (AT) discussions (DOT) microsoft.com> wrote: Why does SSMS 2008 force ALL new server registrations under "Local Server Group"? In 2005, I could create folders (almost) arbitrarly in the folder tree... Now I cannot create folders where I want to place them! I had no problem creating groups as long as they were somewhere within Local Server Groups. They nested fine. I haven't found a way to move registrations to different groups, or move groups around. Roy Harvey Beacon Falls, CT |
#63
| |||
| |||
|
|
I'm not complaining about the nomenclature. I'm complaining about the strictness of where I'm allows to create branches / leaves of the tree. If we were to follow your reasoning, where would one place server registrations contained in XML files that are not local to the machine? Have you tried to create a folder in in branch other that "Local Server Groups"? "Tibor Karaszi" wrote: Perhaps the groups should have been named "Locally Registered Servers Group" and "Remotely Registered Servers Group". I.e., the question isn't whether the servers in the groups are local or not, the question is whether the registration information resides in an XML file locally on your machine or in msdb possibly remotely on some other machine. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Mark H. Shin" <MarkHShin (AT) discussions (DOT) microsoft.com> wrote in message news:E0CA0C5C-1272-4310-AD12-FAF31AF2B9C9 (AT) microsoft (DOT) com... Yes. That is the same problem I'm having, but as you can deduce, most of my SQL server registered servers are "Remote" and should not be filed under "Local Server Groups"... SSMS 2005 allows allowed creation of folders directly under "Database Engine". "Roy Harvey (SQL Server MVP)" wrote: On Fri, 5 Sep 2008 12:43:01 -0700, Mark H. Shin MarkHShin (AT) discussions (DOT) microsoft.com> wrote: Why does SSMS 2008 force ALL new server registrations under "Local Server Group"? In 2005, I could create folders (almost) arbitrarly in the folder tree... Now I cannot create folders where I want to place them! I had no problem creating groups as long as they were somewhere within Local Server Groups. They nested fine. I haven't found a way to move registrations to different groups, or move groups around. Roy Harvey Beacon Falls, CT |
#64
| |||
| |||
|
|
I'm not complaining about the nomenclature. I'm complaining about the strictness of where I'm allows to create branches / leaves of the tree. If we were to follow your reasoning, where would one place server registrations contained in XML files that are not local to the machine? Have you tried to create a folder in in branch other that "Local Server Groups"? "Tibor Karaszi" wrote: Perhaps the groups should have been named "Locally Registered Servers Group" and "Remotely Registered Servers Group". I.e., the question isn't whether the servers in the groups are local or not, the question is whether the registration information resides in an XML file locally on your machine or in msdb possibly remotely on some other machine. -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi "Mark H. Shin" <MarkHShin (AT) discussions (DOT) microsoft.com> wrote in message news:E0CA0C5C-1272-4310-AD12-FAF31AF2B9C9 (AT) microsoft (DOT) com... Yes. That is the same problem I'm having, but as you can deduce, most of my SQL server registered servers are "Remote" and should not be filed under "Local Server Groups"... SSMS 2005 allows allowed creation of folders directly under "Database Engine". "Roy Harvey (SQL Server MVP)" wrote: On Fri, 5 Sep 2008 12:43:01 -0700, Mark H. Shin MarkHShin (AT) discussions (DOT) microsoft.com> wrote: Why does SSMS 2008 force ALL new server registrations under "Local Server Group"? In 2005, I could create folders (almost) arbitrarly in the folder tree... Now I cannot create folders where I want to place them! I had no problem creating groups as long as they were somewhere within Local Server Groups. They nested fine. I haven't found a way to move registrations to different groups, or move groups around. Roy Harvey Beacon Falls, CT |
![]() |
| Thread Tools | |
| Display Modes | |
| |