Viewing 15 posts - 2,986 through 3,000 (of 9,253 total)
Scorz (9/4/2014)
September 5, 2014 at 3:23 am
changing the computer name will essentially change the sql instance name, this is likely the issue you are having. Supply the new servername or the IP address and retry the...
September 4, 2014 at 7:26 am
sounds like the log is not large enough to cope with the longest active transaction 😉
September 4, 2014 at 7:21 am
do you want the AlwaysOn solution to reatin a failover cluster instance as a replica? There are restrictions by doing this 😉
September 4, 2014 at 7:08 am
an upgrade is perfectly viable as long as it's between supported editions. What is the state of each node for cluster membership? Is the current instance a Failover Cluster Iinstance...
September 4, 2014 at 5:41 am
do you plan to use separate NICs or one NIC?
September 4, 2014 at 5:32 am
bpowers (9/3/2014)
September 4, 2014 at 5:29 am
if running under local system you shouldnt need to do anything
September 4, 2014 at 5:26 am
Whats your environment like?
For example, If it takes 2 days just to rack the servers and connect the storage this would need to be factored in.
September 3, 2014 at 11:03 am
Yes you can add extra IP addresses for SQL server to listen on, you either stack them on the same NIC or have separate NICs
September 3, 2014 at 10:57 am
You'll need to create a new SPN if you change the computername and the svc account does not have permission to do it automatically.
September 3, 2014 at 10:50 am
Chowdary's (9/3/2014)
thank you for reply,Can you pls tell me the TUF file path,where it will be created when we configure the log shipping.....
Regards
Chowdary...
To be honest i can't remember, you could...
September 3, 2014 at 9:06 am
cstrati (9/2/2014)
The SQLServer and SQLAgent login are both under login "local system"
This violates all Windows and SQL server security Best Practice.
cstrati (9/2/2014)
September 2, 2014 at 11:58 pm
that's not surprising
September 2, 2014 at 10:31 am
Viewing 15 posts - 2,986 through 3,000 (of 9,253 total)