February 3, 2010 at 7:43 am
We are upgrading our PeopleSoft systems, moving from 32 bit to 64 bit applications/servers. As a part of this, we are also moving from SQL Server 2005 to SQL Server 2008. Another major part of this move is building load balancing (web and application servers) and failover (web, application, database servers) into the architecture.
For the database side, we are planning on using database mirroring. Well I ran into my first issue, and that was actually getting a test database to mirror between two servers.
Resolution: I had to add a login in SQL Server 2008 on the servers involved for the domain account used by SQL Server 2008, then grant CONNECT permissions to the database mirroring endpoints.
My question, what is the minimum server level permissions required by this login to allow database mirroring to work. In this case I went to the extreme and assigned the login sys admin rights. I would like to reduce this if it is possible.
February 3, 2010 at 3:05 pm
Just an FYI Lynn, I am looking into this but it is taking me longer than expected. I am thinking you could get away with ddladmin but that isn't much better than sa.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 3, 2010 at 3:10 pm
CirquedeSQLeil (2/3/2010)
Just an FYI Lynn, I am looking into this but it is taking me longer than expected. I am thinking you could get away with ddladmin but that isn't much better than sa.
I appreciate you looking into this. I would at the moment, but I am on my next critical part. What to do when the pricipal fails to mirror. Scheduled jobs need to activate on the new principal and if the server with the old pricipal is still up (or after it comes up), the scheduled jobs there need to be disabled.
I have the event notification piece working. Now I have to process those notifications and figure out what needs to be done when. Fun.
February 3, 2010 at 3:30 pm
Lynn Pettis (2/3/2010)
CirquedeSQLeil (2/3/2010)
Just an FYI Lynn, I am looking into this but it is taking me longer than expected. I am thinking you could get away with ddladmin but that isn't much better than sa.I appreciate you looking into this. I would at the moment, but I am on my next critical part. What to do when the pricipal fails to mirror. Scheduled jobs need to activate on the new principal and if the server with the old pricipal is still up (or after it comes up), the scheduled jobs there need to be disabled.
I have the event notification piece working. Now I have to process those notifications and figure out what needs to be done when. Fun.
It is the kind of fun that I would enjoy doing. Of course, I would make sure that every single step is documented too - massive project like what you are doing needs that. I'm not saying you're not doing that - just adding that in.
With the docs in hand, I could then break it and rebuild it to test over and over again to make sure it is all good. (I know preaching to the choir here.)
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
February 3, 2010 at 3:38 pm
CirquedeSQLeil (2/3/2010)
Lynn Pettis (2/3/2010)
CirquedeSQLeil (2/3/2010)
Just an FYI Lynn, I am looking into this but it is taking me longer than expected. I am thinking you could get away with ddladmin but that isn't much better than sa.I appreciate you looking into this. I would at the moment, but I am on my next critical part. What to do when the pricipal fails to mirror. Scheduled jobs need to activate on the new principal and if the server with the old pricipal is still up (or after it comes up), the scheduled jobs there need to be disabled.
I have the event notification piece working. Now I have to process those notifications and figure out what needs to be done when. Fun.
It is the kind of fun that I would enjoy doing. Of course, I would make sure that every single step is documented too - massive project like what you are doing needs that. I'm not saying you're not doing that - just adding that in.
With the docs in hand, I could then break it and rebuild it to test over and over again to make sure it is all good. (I know preaching to the choir here.)
Considering everything I am doing on this pair of servers needs to be duplicated on another pair of servers, trust me, I am documenting what I am doing.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply