Are BUILTIN\Administrators (local admins on the server) the only persons
allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
Services (SSRS)? Can others who may have the Content Manager Role on a
folder or that have the System Administrator Role use SSMS? So far my
experience is only BUILTIN\Admins can use SSMS. Anyting special that must be
done to open up the SSMS to Reporting Services for non BUILTIN\Admins?Why do you want someone, who is not DB admin, to use SSMS to "manage"
reporting services' meta database? Even a db manager has few need to manage
reporting services' database directly. Reporting Services is a web
application and it is managed through a web interfaccce (report manager -
http://serverName/reports).
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> Are BUILTIN\Administrators (local admins on the server) the only persons
> allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> Services (SSRS)? Can others who may have the Content Manager Role on a
> folder or that have the System Administrator Role use SSMS? So far my
> experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> be
> done to open up the SSMS to Reporting Services for non BUILTIN\Admins?|||I have taken 2 Microsoft Reporting Services (webcast) courses, which have
shown all the administration of SSRS taking place in SQL Server Management
Studio. I use SSMS to conduct other database and A.S. work and consider it
convenient to use SSMS to work SSRS issues, as well. At our location, DBAs
are not allowed to be local admins (except for temporary circumstances) as a
Sarbanes-Oxley design result. I think it is interesting that no one answers
my question, but are very willing to question the circumstances.
"Norman Yuan" wrote:
> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> reporting services' meta database? Even a db manager has few need to manage
> reporting services' database directly. Reporting Services is a web
> application and it is managed through a web interfaccce (report manager -
> http://serverName/reports).
>
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> > Are BUILTIN\Administrators (local admins on the server) the only persons
> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> > Services (SSRS)? Can others who may have the Content Manager Role on a
> > folder or that have the System Administrator Role use SSMS? So far my
> > experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> > be
> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>
>|||>>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
>> shown all the administration of SSRS taking place in SQL Server
>> Management
>> Studio. [..]
>>I think it is interesting that no one answers my question, but are very
>>willing to question the circumstances.
It *is* interesting, but it's also interesting that this is how the courses
recommended that you work, IMHO, since it may not be a viable strategy,
long-term.
Please read below, from Brian Welcker's Weblog
(http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
feedback.
Which parts of administering RS were you particularly interested in doing
via SSMS versus Report Manager (just curious)?
(snip) ---
Watusi (SSRS Management Tools Changes for Katmai)
For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.
Why the change?
Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.
This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.
If you have feedback about these changes, please feel free to comment.
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> shown all the administration of SSRS taking place in SQL Server Management
> Studio. I use SSMS to conduct other database and A.S. work and consider
> it
> convenient to use SSMS to work SSRS issues, as well. At our location,
> DBAs
> are not allowed to be local admins (except for temporary circumstances) as
> a
> Sarbanes-Oxley design result. I think it is interesting that no one
> answers
> my question, but are very willing to question the circumstances.
> "Norman Yuan" wrote:
>> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> reporting services' meta database? Even a db manager has few need to
>> manage
>> reporting services' database directly. Reporting Services is a web
>> application and it is managed through a web interfaccce (report manager -
>> http://serverName/reports).
>>
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> > Are BUILTIN\Administrators (local admins on the server) the only
>> > persons
>> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> > Reporting
>> > Services (SSRS)? Can others who may have the Content Manager Role on a
>> > folder or that have the System Administrator Role use SSMS? So far my
>> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
>> > must
>> > be
>> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>>|||Appreciate your feedback and the insight into Katmai. Looks like it is best
to focus on the Report Manager tool. I am responsible for creating new
folders and assigning new accounts / roles. Most other work is done by the
report developers / folder content managers. I am a previous DBA whose work
has been outsourced. I, currently, provide a role of 'moving' the corp. into
new (DBMS, etc. ) software, then working out the details of handing the
support over to the service provider. I am not yet to the point of moving
the support of SSRS to the service providers, due to budgets, and other
administrative hurdles, so I am the current administrator, beyond the
installation of the product.
"Lisa Slater Nicholls" wrote:
> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> >> shown all the administration of SSRS taking place in SQL Server
> >> Management
> >> Studio. [..]
> >>I think it is interesting that no one answers my question, but are very
> >>willing to question the circumstances.
> It *is* interesting, but it's also interesting that this is how the courses
> recommended that you work, IMHO, since it may not be a viable strategy,
> long-term.
> Please read below, from Brian Welcker's Weblog
> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
> feedback.
> Which parts of administering RS were you particularly interested in doing
> via SSMS versus Report Manager (just curious)?
> (snip) ---
> Watusi (SSRS Management Tools Changes for Katmai)
> For Katmai we are considering the removal of namespace management (folders,
> reports, data sources, models) from the Reporting Services Add-in for SQL
> Server Management Studio (SSMS). In other words, we are considering removing
> the 'Home' folder under the Reporting Server node in SSMS.
> Why the change?
> Customer feedback and usage data indicates that Report Manager and/or
> SharePoint are the tools of choice for managing the Report Server namespace,
> rather than the SSMS add-in. The design constraints of SSMS mean that any
> new namespace functionality is significantly expensive to implement,
> specifically adding support for the namespace in SharePoint integrated mode.
> For Katmai we want to invest in SharePoint and Report Manager for namespace
> management and focus on SSMS as a server-level management tool.
> This means that the namespace management functions that are not available in
> Report Manager (Model ClickThrough and Model Item Security) will be added to
> Report Manager (they are already in SharePoint). Job Management, configuring
> System properties, and administering Roles will be moved to SSMS. In
> addition, SSMS will be updated to work in SharePoint mode.
> If you have feedback about these changes, please feel free to comment.
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
> >I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> > shown all the administration of SSRS taking place in SQL Server Management
> > Studio. I use SSMS to conduct other database and A.S. work and consider
> > it
> > convenient to use SSMS to work SSRS issues, as well. At our location,
> > DBAs
> > are not allowed to be local admins (except for temporary circumstances) as
> > a
> > Sarbanes-Oxley design result. I think it is interesting that no one
> > answers
> > my question, but are very willing to question the circumstances.
> >
> > "Norman Yuan" wrote:
> >
> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> >> reporting services' meta database? Even a db manager has few need to
> >> manage
> >> reporting services' database directly. Reporting Services is a web
> >> application and it is managed through a web interfaccce (report manager -
> >> http://serverName/reports).
> >>
> >>
> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> >> > Are BUILTIN\Administrators (local admins on the server) the only
> >> > persons
> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
> >> > Reporting
> >> > Services (SSRS)? Can others who may have the Content Manager Role on a
> >> > folder or that have the System Administrator Role use SSMS? So far my
> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
> >> > must
> >> > be
> >> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
> >>
> >>
> >>
>|||>>Looks like it is best to focus on the Report Manager tool.
I didn't actually mean to say that! I meant to say: if you have cogent
reasons why the work you need to do is better done in Management Studio
rather than Report Manager... then MS deserves to hear your reasons <s>.
OTOH... reading that post closely, it seemed clear to me that the RS team
found the required heirarchical arrangement of functionality in Studio
limiting and not really suited to their purposes. They were probably tired
of shoe-horning features into it. In the Report Manager, they have a much
free-er hand and it was probably not necessary for them to split their
effort between implementation of upcoming features in both UIs.
Going forward, I guess we should be happy if they can focus their energy on
one management UI and we get more new features as a result <s>.
Cheers,
>L<
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:D6726064-25F3-45C6-A9DB-C54CD3778868@.microsoft.com...
> Appreciate your feedback and the insight into Katmai. Looks like it is
> best
> to focus on the Report Manager tool. I am responsible for creating new
> folders and assigning new accounts / roles. Most other work is done by
> the
> report developers / folder content managers. I am a previous DBA whose
> work
> has been outsourced. I, currently, provide a role of 'moving' the corp.
> into
> new (DBMS, etc. ) software, then working out the details of handing the
> support over to the service provider. I am not yet to the point of moving
> the support of SSRS to the service providers, due to budgets, and other
> administrative hurdles, so I am the current administrator, beyond the
> installation of the product.
> "Lisa Slater Nicholls" wrote:
>> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >>have
>> >> shown all the administration of SSRS taking place in SQL Server
>> >> Management
>> >> Studio. [..]
>> >>I think it is interesting that no one answers my question, but are
>> >>very
>> >>willing to question the circumstances.
>> It *is* interesting, but it's also interesting that this is how the
>> courses
>> recommended that you work, IMHO, since it may not be a viable strategy,
>> long-term.
>> Please read below, from Brian Welcker's Weblog
>> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
>> feedback.
>> Which parts of administering RS were you particularly interested in doing
>> via SSMS versus Report Manager (just curious)?
>> (snip) ---
>> Watusi (SSRS Management Tools Changes for Katmai)
>> For Katmai we are considering the removal of namespace management
>> (folders,
>> reports, data sources, models) from the Reporting Services Add-in for SQL
>> Server Management Studio (SSMS). In other words, we are considering
>> removing
>> the 'Home' folder under the Reporting Server node in SSMS.
>> Why the change?
>> Customer feedback and usage data indicates that Report Manager and/or
>> SharePoint are the tools of choice for managing the Report Server
>> namespace,
>> rather than the SSMS add-in. The design constraints of SSMS mean that any
>> new namespace functionality is significantly expensive to implement,
>> specifically adding support for the namespace in SharePoint integrated
>> mode.
>> For Katmai we want to invest in SharePoint and Report Manager for
>> namespace
>> management and focus on SSMS as a server-level management tool.
>> This means that the namespace management functions that are not available
>> in
>> Report Manager (Model ClickThrough and Model Item Security) will be added
>> to
>> Report Manager (they are already in SharePoint). Job Management,
>> configuring
>> System properties, and administering Roles will be moved to SSMS. In
>> addition, SSMS will be updated to work in SharePoint mode.
>> If you have feedback about these changes, please feel free to comment.
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>> >I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >have
>> > shown all the administration of SSRS taking place in SQL Server
>> > Management
>> > Studio. I use SSMS to conduct other database and A.S. work and
>> > consider
>> > it
>> > convenient to use SSMS to work SSRS issues, as well. At our location,
>> > DBAs
>> > are not allowed to be local admins (except for temporary circumstances)
>> > as
>> > a
>> > Sarbanes-Oxley design result. I think it is interesting that no one
>> > answers
>> > my question, but are very willing to question the circumstances.
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> >> reporting services' meta database? Even a db manager has few need to
>> >> manage
>> >> reporting services' database directly. Reporting Services is a web
>> >> application and it is managed through a web interfaccce (report
>> >> manager -
>> >> http://serverName/reports).
>> >>
>> >>
>> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> >> > Are BUILTIN\Administrators (local admins on the server) the only
>> >> > persons
>> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> >> > Reporting
>> >> > Services (SSRS)? Can others who may have the Content Manager Role
>> >> > on a
>> >> > folder or that have the System Administrator Role use SSMS? So far
>> >> > my
>> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special
>> >> > that
>> >> > must
>> >> > be
>> >> > done to open up the SSMS to Reporting Services for non
>> >> > BUILTIN\Admins?
>> >>
>> >>
>> >>
>>
Showing posts with label administering. Show all posts
Showing posts with label administering. Show all posts
Sunday, February 12, 2012
Administering SQl 2000 from SQL 2005
I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
> >I have some old SQL servers that I cannot upgrade becuase of the
> >application
> > that uses them. Can I manage these servers from SQL 2005? IF so, are there
> > any known gotchas? Thanks in advance.
> > --
> > Bettie
>
>
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
> >I have some old SQL servers that I cannot upgrade becuase of the
> >application
> > that uses them. Can I manage these servers from SQL 2005? IF so, are there
> > any known gotchas? Thanks in advance.
> > --
> > Bettie
>
>
Administering SQl 2000 from SQL 2005
I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
Bettie
You can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||Thanks -- I'll try the upgrade in the lab.
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
Bettie
You can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||Thanks -- I'll try the upgrade in the lab.
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>
Thursday, February 9, 2012
Administering SQl 2000 from SQL 2005
I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in messag
e
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in messag
e
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>
Administering SQL
In SQL Server 2005 to administer all aspects of SQL is there any way a non local administrator can do this? We are trying to remove the DBAs from being local administrators over the SQL server machines in SQL 2005, we were able to do this in SQL 2000 but SQL 2005 is not working correctly.
We want to make the DBAs a member of local power users and assign the specific rights for it. Can this be done, if so how? is there a document I can reference somewhere.
Hi,
yes sure. Local administrators are automatically in the sysadmin group. YOu can sure remove them from the group if you don′t want them to have access to the server. On the other side, you can grant any role to a individual role, also the serverrole sysadmin. So put the "SQL Administrators" in a special Windows group and add this group to the serveradmin role. That should be fine for you.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Administering Replication
Hello,
I do have the following question:
SQLServer 2000 Push Replication
What SPs are responsible if clicking right on the Repl. Topic and clicking "start syncronization"?
Reason: I will give Administrators (no dbo) the possibility to start the sync again if failed (e.g too many timeouts) over a Frontend.
Thanks in advance
PeterRun SQL-Profiler and check what SPs are executed.
Regards.
I do have the following question:
SQLServer 2000 Push Replication
What SPs are responsible if clicking right on the Repl. Topic and clicking "start syncronization"?
Reason: I will give Administrators (no dbo) the possibility to start the sync again if failed (e.g too many timeouts) over a Frontend.
Thanks in advance
PeterRun SQL-Profiler and check what SPs are executed.
Regards.
Administering MSDE with Enterprise Manager
Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
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.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
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.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
Administering MSDE with Enterprise Manager
Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
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.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
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.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> 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.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
Administering msde
Hi all,
I am totaly new to all this sql server think. I have installed MSDE on Win2K
Server.
How do you administer this think? Is there een interface? I have tried SQL
webadmin.
When I try to open the site with IE I see source code of the file
default.aspx.
Why is this?
Any help would be great.
tnx. in advance
Admir
hi admir,
admir wrote:
> Hi all,
> I am totaly new to all this sql server think. I have installed MSDE
> on Win2K Server.
> How do you administer this think? Is there een interface? I have
> tried SQL webadmin.
> When I try to open the site with IE I see source code of the file
> default.aspx.
> Why is this?
>
personally I do not like WDA very much... but you perhaps can find some
hints at http://www.sqljunkies.com/forums/ ..
if you need a Web based admin you'd probably better invest in myLittleTools
(http://www.mylittletools.net/mla_sql) ... other free and commercial tools
for administering MSDE are listed at
http://www.microsoft.com/sql/msde/partners/default.asp ,
http://www.aspfaq.com/show.asp?id=2442
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
I am totaly new to all this sql server think. I have installed MSDE on Win2K
Server.
How do you administer this think? Is there een interface? I have tried SQL
webadmin.
When I try to open the site with IE I see source code of the file
default.aspx.
Why is this?
Any help would be great.
tnx. in advance
Admir
hi admir,
admir wrote:
> Hi all,
> I am totaly new to all this sql server think. I have installed MSDE
> on Win2K Server.
> How do you administer this think? Is there een interface? I have
> tried SQL webadmin.
> When I try to open the site with IE I see source code of the file
> default.aspx.
> Why is this?
>
personally I do not like WDA very much... but you perhaps can find some
hints at http://www.sqljunkies.com/forums/ ..
if you need a Web based admin you'd probably better invest in myLittleTools
(http://www.mylittletools.net/mla_sql) ... other free and commercial tools
for administering MSDE are listed at
http://www.microsoft.com/sql/msde/partners/default.asp ,
http://www.aspfaq.com/show.asp?id=2442
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
Administering many SQL Servers
We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> > We have 25+ SQL Servers our DBA group administers. Each is installed under
> > a
> > domain account, call it Domain1\SQLAdmin. When we change the password to
> > Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> > Agent
> > password properties on each box to be the new password. Is there any way
> > to
> > automate this process?
>
>
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> > We have 25+ SQL Servers our DBA group administers. Each is installed under
> > a
> > domain account, call it Domain1\SQLAdmin. When we change the password to
> > Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> > Agent
> > password properties on each box to be the new password. Is there any way
> > to
> > automate this process?
>
>
Administering many SQL Servers
We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?
Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?
|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?
Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?
|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>
Administering many SQL Servers
We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>
administering jobs and targetserversrole
Hi all,
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.
>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.
>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
administering jobs and targetserversrole
Hi all,
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
--
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
--
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
administering jobs and targetserversrole
Hi all,
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
--
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Hoping that someone else has tried to allow non sa people the ability to
administer jobs on a server. My situation is this:
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.>
> Hi all,
> Hoping that someone else has tried to allow non sa people the ability to
> administer jobs on a server. My situation is this:
> My goal is to allow my developers to create and modify jobs on our
> development server. To this end, I have put the developers (who are dbo
in
> their respective db), in an nt group and put them in the targetserversrole
> in msdb on the server. In addition, by changing the role and granting
> execute to the add,delete,and update job stored procedure groups and the
job
> start and stop stored procedures I am able to allow the group to add and
> modify jobs, except for one item in the job and that is to set up job
> notifications. I have tried granting the add,update and delete
notification
> group but that doesn't do it as the check boxes are still disabled for the
> developers when they look at that part of the job. Does anyone know what
I
> am missing in this plan? Thanks in advance for any help solving this.
>
--
With SQL Server 2000, you need to be a sysadmin to be able to FULLY
ADMINISTER SQL Agent jobs.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
administering jobs and targetserversrole
My goal is to allow my developers to create and modify jobs on our
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.One of the problems with this approach is that it's not
documented or supported. The role really isn't meant to be
used outside of SQL Server using it for MSX. If you use this
role, you will find that things change if/when you apply SP3
and who knows what other service packs or fixes may change
the functionality of the role.
-Sue
On Tue, 4 May 2004 09:12:53 -0400, "MarkR"
<mrussell@.dasny.org.dontspamme.net> wrote:
>My goal is to allow my developers to create and modify jobs on our
>development server. To this end, I have put the developers (who are dbo in
>their respective db), in an nt group and put them in the targetserversrole
>in msdb on the server. In addition, by changing the role and granting
>execute to the add,delete,and update job stored procedure groups and the jo
b
>start and stop stored procedures I am able to allow the group to add and
>modify jobs, except for one item in the job and that is to set up job
>notifications. I have tried granting the add,update and delete notificatio
n
>group but that doesn't do it as the check boxes are still disabled for the
>developers when they look at that part of the job. Does anyone know what I
>am missing in this plan? Thanks in advance for any help solving this.
>
>
development server. To this end, I have put the developers (who are dbo in
their respective db), in an nt group and put them in the targetserversrole
in msdb on the server. In addition, by changing the role and granting
execute to the add,delete,and update job stored procedure groups and the job
start and stop stored procedures I am able to allow the group to add and
modify jobs, except for one item in the job and that is to set up job
notifications. I have tried granting the add,update and delete notification
group but that doesn't do it as the check boxes are still disabled for the
developers when they look at that part of the job. Does anyone know what I
am missing in this plan? Thanks in advance for any help solving this.One of the problems with this approach is that it's not
documented or supported. The role really isn't meant to be
used outside of SQL Server using it for MSX. If you use this
role, you will find that things change if/when you apply SP3
and who knows what other service packs or fixes may change
the functionality of the role.
-Sue
On Tue, 4 May 2004 09:12:53 -0400, "MarkR"
<mrussell@.dasny.org.dontspamme.net> wrote:
>My goal is to allow my developers to create and modify jobs on our
>development server. To this end, I have put the developers (who are dbo in
>their respective db), in an nt group and put them in the targetserversrole
>in msdb on the server. In addition, by changing the role and granting
>execute to the add,delete,and update job stored procedure groups and the jo
b
>start and stop stored procedures I am able to allow the group to add and
>modify jobs, except for one item in the job and that is to set up job
>notifications. I have tried granting the add,update and delete notificatio
n
>group but that doesn't do it as the check boxes are still disabled for the
>developers when they look at that part of the job. Does anyone know what I
>am missing in this plan? Thanks in advance for any help solving this.
>
>
Subscribe to:
Posts (Atom)