We are in parallel with one of our apps going from SQL2005 to 2012. Another small app will be upgraded to 2012 in March. The last one is...

Perry Whittle (2/9/2016)

---

:Whistling: I posted the link to that at the beginning of this topic on my very first post :w00t:

At no point...

I found the official Microsoft preferred method:

Oracle, SQL Server and DB2 are by far the marketshare leaders. However, they are all quite expensive which leads to the MySQL, NoSQL and others to take a small...

I have been pushing app folks for 3 years to get into their budgets upgrades OR replacement products for things running on Windows 2003/SQL 2005. We only have three...

jcarranza 23978 (2/5/2016)

---

Normally when you do the FailOver on the AlwaysON High Availability Group the Primary Node A will change the ROLE over to Node B.

If you don't do it...

jcarranza 23978 (2/4/2016)

---

1. Open your Windows FailOver Cluster Manager .

2. Check which node owns the Role (A or B).

3. Pause the Secondary node (so that the Primary knows is down)

4....

Man. Thanks for posting...

I am very new to this as well. We just brought up our very first Always on system this week. I believe the listener will allow you...

In place upgrade is really not something you want to do. If the upgrade fails then you have a unstable system (possibly one that is dead) and no backout...

That is the first release of SQL 2012.

This is how you can figure that out:

[/url]

Yes, it is set to failover mode Automatic.

I found the issue and fixed it.

Upon failover I changed it to the recommended setting in this link. Basically it means it...

It is set to Synchronous commit. There aren't any data changes as we only have a test database with a few test tables with less than 20 rows in...

On...

This same thing happened to me as well. I had a clean output file but the job said failed. I manually ran the integrity check and it was...