We have 2 SQL 2012 servers. Our application has 2 databases. We are creating an AlwaysOn cluster. Is it good to create 2 AlwaysOn clusters to have 1 database primary on one of the servers and the other database primary on the other server?
I have been asked if it is possible to have one database running on one server and the other database on the other server. Is this possible without creating 2 separate AlwaysOn clusters? Is it a good idea to do this?
If there is any interplay between the two databases I would STRONGLY encourage you to keep them on the same server and in a single AG. Linked servers SUCK in SO many ways.
Outside of that if you want them to be split then you need 2 AGs. I have done this for clients and there is no issues (that aren't already in play with AGs).
Don't forget that there are a WIDE array of things you need to do when you have AGs, like SID-coherent logins, SQL Agent Jobs, how to (re)point various constructs if/when a failover occurs, etc.
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service