Last post Jan 22, 2020 01:03 PM by PatriceSc
Jan 22, 2020 08:07 AM|jimmy69|LINK
We have an application web who is installed on a server application and this web site call another server who sql serveur is installed.
all works since several years.
For some reason of performance, we need to migrate this application to a cluster sql.
For me, but i'm not a specialist about cluster -> I thought to backup the database in our last sql serveur and installed to the new cluster sql server ...
but i don't know if it's work ?
My first question is -> it possible to backUp all (data and structure of database) and install in the new sql cluster OR we need to start from scratch ?
second question -> sorry question can be stupid but is there something to do when an application web call a cluster sql ?
In fact, is something must be made in the web app for to work in cluster ?
thanks for sharing your knowledge
Jan 22, 2020 10:49 AM|Khuram.Shahzad|LINK
As far as i know, there is active and passive nodes in cluster and if you want to connect to a node then you can access it by its IP or Virtual Server Name, Cluster have its own IP and Node have its own, one node can have an instance and you can connect
with that particular instance as well by specifying in connection string.
"The connection string is written in the usual way; but in clustering you have 3 (or more) addresses: one for each node which constitues the cluster and one for the cluster. E.g.: we have two node with addresses 192.168.0.10 and 192.168.0.20: if you
write down one of this numbers as the DataSource in the connection string, you'll gain access to that physical instance. But if you want to access the cluster (virtual) Sql Server instance, you'll have to use the cluster's address (e.g.: 192.168.0.230) as
the DataSource. Of course, you can also use the machines' names instead of the IP addresses, provided you are in the same domain as the cluster."
I like the mirror feature as well which is supported by ADo.Net:
Jan 22, 2020 01:03 PM|PatriceSc|LINK
My understanding is that you are planning something such as is https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server?view=sql-server-ver15#Benefits which
is AFAIK intended for availability, NOT for performance.
The cluster should be seen as a single SQL Server instance directing the query to the active "node". The benefit is that it can switch to another node as needed without any reconfiguration.