|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 5:06 PM
Points: 39,
Visits: 129
|
|
Thanks everyone for the replys, I am looking at all these options!
In regards to recreating logins and resetting SIDs:
All the logins and service accounts are using domain accounts. I have setup the test/dev server with all the required logins and service accounts. Do I still need to look at restting SIDs? I dont have login accounts that will access any other servers or resources outside of their SQL server. (I do know the credentials created for a few jobs will need to be recreated)
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: 2 days ago @ 12:37 PM
Points: 228,
Visits: 725
|
|
wb.spiekerdoyle (9/11/2012) Thanks everyone for the replys, I am looking at all these options!
In regards to recreating logins and resetting SIDs:
All the logins and service accounts are using domain accounts. I have setup the test/dev server with all the required logins and service accounts. Do I still need to look at restting SIDs? I dont have login accounts that will access any other servers or resources outside of their SQL server. (I do know the credentials created for a few jobs will need to be recreated)
You don't have to worry about SID if you're using domain accounts and they're on the same domain.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Wednesday, January 02, 2013 5:06 PM
Points: 39,
Visits: 129
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: 2 days ago @ 12:37 PM
Points: 228,
Visits: 725
|
|
MysteryJimbo (9/11/2012) Mirroring has an processing overhead on the principle server which can, and does, have a performance impact on high TPS servers. I've seen it and discounted this technology for this reason.
I have never seen this on my production boxes. What I've seen, and on SQL 2005, was some latency issues.
But as a temporary solution to migrate big databases with minimum downtime, I think Mirroring is really good.
|
|
|
|