May 1, 2002 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/rmarda/multiserveradministration.asp
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
May 6, 2002 at 5:17 am
How about authentication issue?
I had tried Multiserver adm. in mixed mode authentication, it was worked, but in win authentication it wasn't work and i saw my security authentication change from win mode to mixed mode.
After I restart SQl Service, it was work.
Any Comment?
TIA
May 6, 2002 at 5:50 am
It never occured to me to test for Windows only authentication. I've always used mixed authentication mode with the SQL Servers I've managed. I'll have to look into this the first chance I get. Unless someone else has experience with multi server administration and Windows authentication only.
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
May 6, 2002 at 7:59 am
Mixed mode is required. The operator created for MultiServer Administration (MSXOperator) is a SQL Server login and thus the change.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
May 6, 2002 at 8:54 am
Thanks Brian!
Robert Marda
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
December 7, 2007 at 4:17 pm
Hi All
What's the stability on the multi server setup, I'm think of making one of my cluster instances as a master and letting all other 2005 servers being slaves. For now that's 6 slaves, but in the future that will probably grow to 15-25.
Has anyone got experience with a setup of such size and even bigger ones? What's the performance impact for the master server, CPU, msdb and network wise?
Any best practice guidelines out there for setting this up?
Thanks in advance for any hints.
//SUN
March 17, 2009 at 2:56 pm
Hi,
I'm having some difficulty with a multi-server maintenance plan. I was able to get multi-server admin configured and the resultant job propogated to the other servers, but when I Execute the plan, it only runs locally. I tried starting the multi-server Job for the plan and it looks like it attempted to run the target server jobs, but they failed with:
Could not load package "Maintenance Plans\Nightly Index Maintenance" because of error 0xC001000A. Description: The specified package could not be loaded from the SQL Server database.
What's going on?
Konrad Willmert
Indiana Wesleyan University
May 6, 2009 at 6:44 am
Hi,
I am experiencing the same problem right now. I configured multiserver environment and all worked out. The job was propagated and available both on master and target server. However, when I run the job it runs only locally. When I run it from the target server, I am getting the same problem you are getting.
I was really wondering if you could share your experience if you solved the problem.
I appreciate your comments.
Regards
Niyala
May 7, 2009 at 6:49 am
Sorry, no. We gave up on it. Regular multi-server jobs using T-SQL propagate just fine, so we'll probably be using those to perform maintenance.
March 30, 2010 at 1:51 pm
Multi-Server Administration sure takes on a whole new meaning in SQL server 2008.
I appreciate the article I tried to implemnt this in 2000 and found the jobs a pain to work with especially when the master went out the door with the previous DBA. If I remember right I was hacking system tables in MSDB to get the jobs working again, ahh memories. Anyway R@ is around the corner and Application and Multi-Server Management look to be a big part of the release. Currently working with MDW which worked great! Only issue I found was IIS on XP I guess you can't use port 80 for reporting services. Other then that worked smoothly.
Again thanks for the article Robert i'll be looking for your next one 🙂
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply