SQL Always on

Hello ,
i have sql server 2008 and hosting 3 databases
i have to upgrade to sql 2012 with always on .
i am not DB guy so how can i migrate the database from sql 2008 to 2012 is it kind of export or backup & restore
need any reference please regarding this process .
Regards
MCP MCSA MCSE MCT MCTS CCNA

A database migration can be a very complex procedure as usually it's not only the databases that need to migrated. As far as only the databases are concerned, backup/restore would be the preferred method as it leaves your original environment untouched.
Please also think of other aspects such as logins, linked servers, jobs,... all server objects and all of your application's needs need to be migrated to the new server. This list can be endless depending on your specific environment.
Once you have moved your databases to the new server which has been prepared for AlwaysOn with failover partners you can create availability groups and such to establish high availability for them.
You may want to read this as a starting point:
Migration Guide
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Similar Messages

SharePoint 2013 and SQL Always On

How do I setup SharePoint with SQL Always On.
I have two servers SQL1 and SQL2. I created Windows 2012 cluster and called it MyCluster.
I installed SQL Server 2012 SP1 on both servers. I created AlwaysOn group called MyAlwaysOn and added test database to sync between those two servers.
Now I have to install SharePoint 2013. How do I specify the SQL server? Do I say that name is SQL1? Or MyCluster? Or MyAlwaysOn?
MyAlwaysOn does not have IP address or DNS record, so I do not think I can do it. So, is it SQL1 or MyCluster?
If it is SQL1, do I manualy add SharePoint databases to MyAlwaysOn group? How does it work? How will SharePoint know to switch to SQL2?
Anyone knows how to do it right?
Thank you.
Thank you. Eric.

Please see))
http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx
Create SharePoint Databases
Prepare SQL Alias
We need to fool SharePoint into thinking the SQL server where we'll create the configuration database is called something else. That’s because when you create a farm, whatever destination server you use during the “create new farm” stage isn’t forgotten (to
simplify), so first thing’s first let’s create fake alias for our SQL “server” – “SP15” as it’s SharePoint 2013 that’ll use it (version 15). As far as SharePoint needs to know everything is going into a SQL box called 'SP15'.
Now assuming you don’t have SQL Server tools installed (which you shouldn’t if it’s on production!) you’ll need to use a tool called “cliconfg.exe” to create a SQL alias. Run it; click the “Alias” tab, and the Add button.
Add a name – SP15 for the alias name, but it can be anything - instead of referencing a server-name we’ll reference the name of the alias which will transparently redirect traffic to the alias destination instead.
And if you know Russian languages
http://blog.it-kb.ru/2014/04/15/install-two-tier-farm-sharepoint-server-2013-sp1-on-windows-server-2012-r2-part-1-prepare-ha-clustered-sql-server-2012-sp1-cumulative-update-9-instance/
http://blog.it-kb.ru/2014/04/15/install-two-tier-farm-sharepoint-server-2013-sp1-on-windows-server-2012-r2-part-2-create-a-new-server-farm-with-kerberos-and-language-pack/
Так как БД SharePoint в нашем случае будут расположены на удалённом экземпляре SQL Server 2012 SP1(CU9), перед началом установки SharePoint
можно установить пакет Microsoft SQL Server Native Client. Его можно загрузить например со страницы Microsoft
SQL Server 2012 SP1 Feature Pack (файлENU\x64\sqlncli.msi), а ещё лучше взять дистрибутив клиента обновлённой версии из состава CU9 (файл\SQLServer2012_SP1_CU9\1033_enu_lp\x64\setup\x64\sqlncli.msi)
Хотя в дальнейшем фактически утилита подготовки к установке Sharepoint всё равно загрузит у установитSQL Server 2008 R2 SP1 Native Client.
После установки SQL-клиента создадим на нашем сервере SQL-Alias, который будем в дальнейшем использовать для подключения служб SharePoint к серверу SQL Server. Этого конечно можно
и не делать, но это может оказаться полезным (даст нам дополнительную гибкость) в случае необходимости переноса БД на другой SQL-сервер или экземпляр. Запустим встроенную в ОС утилиту SQL Server Client Network Utility (%windir%\system32\cliconfg.exe)
и добавим два новых алиаса – с коротким именем SQL-сервера и его FQDN, указав при этом имя экземпляра и статический TCP порт (в нашем случае SHAREPOINT и 1435соответственно).
Имя самого алиаса в нашем случае будет KOM-AD01-SQLSP

SQL Always On - Group Listener with a Private IP ?

Hi,
I read the tutorial on how to configure SQL Always On in Azure.
I saw that we need to configure the group listener with an Public IP.
I also saw that SQL servers must reside in a different Cloud Service.
A reason why is because Azure does not support direct server return.
What is DSR ?
To help me understanding, is someone able to explain me this situation :
What would happen if I configure group listener with a private IP and I put all my servers in the same cloud service.

Actually, I know what is DSR.
During the initial connexion, the client talks with the group listener and then redirect you to the active server. Afterward, you have a direct connection with the Active Server.
Why is it not supported ?
Why having a public IP instead of a private IP resolve the issue ?
This quote from Microsoft :
The client application must reside on a different cloud service than the one that contains your availability group VMs. Azure does not support direct server return with client and server in
the same cloud service.
Does it apply only with a public IP address ?

Are there benefits to adding crossover cable between two servers for DFS replication and SQL Always On?

I have two identical servers with 4 network interfaces each. The primary usage for two servers is hosting SQL Server instance with Always On high availability and dfs replication. Two network interfaces from each server will be used to connect to main network,
while for the other two (on each) I was thinking about using crossover cable to possibly provide shorter path for two servers to communicate.
Will there be any benefits to doing so, moreover, would teaming two crossover cable help more?
Edit: Below is the link to the article where I got the idea of moving DFS Replication traffic to crossover. I wasn't able to find any info whether same thing is applied to SQL Always On high availability.
http://blogs.technet.com/b/filecab/archive/2006/08/24/449013.aspx

Hi,
According to your description, my understanding is that you want to connect 2 servers by crossed cable(2 NICs).
Just as the blog suggested, directly connect the servers by crossed cable and configure corresponding route entries will improve efficiency.
If both servers have 2 NICs to connect, I recommend you to team the 2 NICs for bandwidth aggregation. NIC teaming is supported by Windows Server 2012/2012 R2, detailed information you may reference:
NIC Teaming Overview
https://technet.microsoft.com/en-us/library/hh831648.aspx
besides, for file servers, SMB Multichannel (a feature included with Windows Server 2012/2012 R2 and part of the SMB 3.0 protocol) will helpful for increasing the network performance and availability. Detailed information reference:
The basics of SMB Multichannel, a feature of Windows Server 2012 and SMB 3.0
http://blogs.technet.com/b/josebda/archive/2012/05/13/the-basics-of-smb-multichannel-a-feature-of-windows-server-2012-and-smb-3-0.aspx
For SQL server, suggestions in SQL Server Best Practices would be helpful for you:
https://technet.microsoft.com/en-us/sqlserver/bb671430.aspx
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SQL Always On for FIM

I wasn't able to find any information regarding the support of SQL Always On
Does FIM support SQL Always On? If not what should I use? Cluster? Mirroring?
The data above this text is pseudorandom, brace yourselves.

https://social.technet.microsoft.com/Forums/en-US/27dde96a-5305-446c-a3e8-edc2e617c55c/sql-2012-always-on-availability-groups?forum=ilm2
As Peter says: clustering is supported, mirroring is not, always on database availability groups are not, log shipping is not. Automatic failover with mirroring or database availability groups will not work. Mirroring itself works, just not the failover.
Albeit you have a big performance hit even in asynchronous mode. Ditto for Availability groups. Log Shipping works, but you do have to pay attention to the management of the log. Again, Mirroring, Availability Groups and Log Shipping are not supported by Microsoft
FIM Product group but they will work to the extent described and with the caveats described. So think carefully on what you want to do, being in an unsupported position isn't fun. Clustering can accomplish the goal of high availability. If I had to pick one
for providing DR in case of site failure I would pick log shipping. But again not supported and you must pay attention to your log management or you could suffer performance hits.
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

SQL Always On: not accessible for queries

Hi forum!
I'm monitoring SQL 2012 Always On Groups with the latest SQL MP. A couple of the database replicas are configured to not allow access. This is to avoid additional license costs for those minor important databases.
However, I get the following events in the SQL log:
Error 976, Severity 14
The target database, '%.*ls', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended
or the availability replica is not enabled for read access. To allow read-only access to this and other ...
Of course, as soon as I configure read-only for those databases the events disappear.
Is there any other solution?
Has anyone identified already (all) the accessing workflows?
Thanks in advance,
Patrick
http://www.syliance.com | http://www.systemcenterrocks.com

Hi All, I am also experiencing this issue. Having a look at the statements SCOM is issuing, it's actually checking whether the AG secondary allows connections but it ignores the value and tries to connect anyway. I believe this is a minor bug.
See below for these queries.
You can vote to correct it through Microsoft Connect on: https://connect.microsoft.com/WindowsServer/feedback/details/1121330
--SCOM/MP: is this database a replica and does it allow connections?
SELECT d.name, d.database_id, CASE WHEN d.replica_id IS NULL THEN 0 ELSE 1 END AS is_replica, ar.secondary_role_allow_connections
FROM sys.databases d JOIN sys.availability_replicas ar on d.replica_id = ar.replica_id JOIN sys.servers s ON s.name = ar.replica_server_name AND s.server_id = 0 /*local server*/
WHERE d.database_id = x --current db id in sys.databases loop
--SCOM/MP: let's look into that db (regardless of whether it allows connections)
--EXCEPTION: The target database, 'x', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.

Sql always on full sync when creating availability group

hi,
i am creating AOAG in SQL 2012 and i am a little confused as to how the sync is created. when you setup the avail group the options you have are full, join and something else. We are doing the full.
i have a database that's 700gb in size so i did a backup to meet the pre reqs of creating the aoag. i then started the process and it shows a list of tasks its performing. once of the tasks is backing up the db before it syncs.
if i look at the backup it shows a size of 217GB. why do i have a difference in the size. does it do something different while creating the AOAG?
Thanks
phill

Hi phillbl,
According to your description, the backup operation copies the data in the database to the backup file. The backup contains only the actual data in the database and not any unused space. Therefore, the backup is usually smaller than the database itself.
Usually, in SQL Server AlwaysOn Availabity Group Wizards, you can use
Select Initial Data Synchronization page to specify a network share in order to create and access backups, then synchronize full initial data with secondary database.
If you are unable to use the wizard to perform full initial data synchronization ,you need to manually prepare a Secondary database for an Availability Group , as other post, you should manually restore a recent database backup of the primary
database using RESTORE WITH NORECOVERY, and then restore each subsequent log backup using RESTORE WITH NORECOVERY.
For more information, see:
http://msdn.microsoft.com/en-us/library/hh403415.aspx
Back Up and Restore of SQL Server Databases:
http://msdn.microsoft.com/en-us/library/ms187048.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Always on listener not discovered.

I have a problem with discovery of the SQL AlwaysOn. I followed the MS article for implementing SQL monitoring. I can see the
vip with the green circle. However, it's not monitored. Is there special configurations that I'm missing?

Verify the following:
enable proxy on physical sql server on SCOM
Run AS Account in SQL Discovery rule.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Which Edition of Windows is required for using SQL 2012 Always On Availability Groups

I want to use the new feature of having 2 secondary mirror replicas. the first secondary replica will be sync the second one will be async.
Currently I have SQL Enterprise license and Windows 2008 R2 Standard license.
Will I be required to upgrade to Windows Enterprise license to use Always On? (since this feature depends on Windows clustering?)
Can you please confirm if SQL Always On feature can be used on Windows 2008 R2 standard or not?
MSDNStudent Knows not much!

Always On is available with Standard Edition but it supports only 2 nodes.
AlwaysOn is a bigger umbrella which covers two features. AlwaysOn Availability Groups (AG) and AlwaysOn Failover Cluster Instance (FCI).
FCI for 2 node is supported. You can't use AG feature in SQL Server Standard Edition
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Distribution status different in SQL than WMI

Hi, we have an issue where when we look into the CAS db to see the replication status messages for all package réplications in
v_DistributionStatus, we get a different result than in the console and WMI by looking into the SMS_DistributionDPStatus class
SQL gives us ID 2372 which means waiting for content with last status from 07/07/2014 and the console and WMI gives us ID 2384 which means Content hash has been sucessfully verified and last status is from today.
This is not happening on all packages and all DPs. We can have a package that doesn't show the right info for just one DP and all the other DPs are reporting the right info.
Why isn't sql always giving us the same info?
Thks in advance and don't hesitate if you have any questions.
joeblow

I am usually using SMS_PackageStatusDistPointsSummarizer
http://msdn.microsoft.com/en-us/library/cc143014.aspx
Torsten Meringer | http://www.mssccmfaq.de

Lync Monitoring Database, Named Instance, Always On

I have a SQL Server 2012 named instance (LYNC_MONITOR) on a specified port which is Always On enabled for deploying LYNC 2012 Monitoring and Reporting. I had moved the databases from another DB server into a Always On AG, which works fine, and set
up Listener on the defined port. My issue comes in when changing the topology. In the topology builder, the requested information is server name and instance (default or named). Well an AG Listener on a specified port is neither of those. If the instance was
actually default, then it would be no problem (but the default instance is SharePoint). So I need to be able to provide the Listener/port combo as the server name without specifying the instance. Currently it's just pointed to the primary node (server/instance).
Does anybody know of a way to get around this? Thanks much.
Tim Hacker

Currently SQL Always On is not supported for Lync 2013. That being said have you looked at setting up a SQL Alias (cliconfg.exe) on the Front Ends? I've used this when the SQL port is not the standard one: http://blogs.technet.com/b/nexthop/archive/2011/04/12/using-lync-server-2010-with-a-custom-sql-server-network-configuration.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Always On Availability Groups

Hello everyone!
I am currently planning to implement SQL Always On Availability Groups.
Mainly i have one sql server so apparently i need to setup a new sql server.
In the wizard there is a page where I need to select Initial data synchronization full or join.
What’s the difference?? Is choosing the full option requires me to provide a Third server to temporarily store my database so my 2 main SQL server can sync for the first time? And if yes can I remove this shared location (Third server) after the database
are synced??
Thank You.

Join option only if the new
secondary databases already exist on each server instance that hosts a secondary replica for the availability group. That is you have manually restore a recent database backup of the primary database using RESTORE WITH NORECOVERY, and then restore each
subsequent log backup using RESTORE WITH NORECOVERY.
Full option
creates a full and log backup of the primary database, create the corresponding secondary databases by restoring these backups on every server instance that is hosting a secondary replica, and join each secondary database to availability group.
When you use full you have to
specify a network share folder in order for the wizard to create backups and secondary replica will access backups to perform restores from this stage. Yes you can remove the share once the all databases are in sync.

How do I handle my Final SELECT based on a @ReportType Run Parameter

So I have multiple CTEs in my SQL...
WITH CTE_1 AS
(SELECT...)
CTE_2 AS
(SELECT...)
CTE_3 AS
(SELECT...)
My Final SELECT then will be based on my CTE drill-downs and the filtering will be based on the @ReportType that will be chosen within SSRS and Report Manager. How can I handle the varying portions of my FINAL SELECT based on @ReportType? Do I have to do
this via dynamic SQL? I know that dynamic SQL is frowned upon. So this is what I'm talking about...
SELECT ...
CASE WHEN @ReportType = 'Renewal People'
THEN INNER JOIN...
WHEN @ReportType = 'New People'
THEN NOT IN (SELECT...)
END
CASE WHEN @ReportType = 'Renewal People'
THEN WHERE...
WHEN @ReportType = 'New People'
THEN WHERE...
END

> I know that dynamic SQL is frowned upon.
That depends. I love (*) dynamic SQL for one thing:
http://www.sqlusa.com/bestpractices/dynamicsql/
Second, there are many things you cannot in static SQL:
http://www.sqlusa.com/bestpractices2008/rebuild-all-indexes/
* First choice is static SQL always.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Lack of support for FIM database mirroring

The official line is that database mirroring is not a supported architecture for the FIM deployment. I am not proposing using this, however I'd like to understand 1) What the issues really would be with a mirrored database deployment, 2) Will support
ever be added for this, and will it come in the form of SQL AlwaysOn?
Really appreciate help and input.
Rgds,
David

Database mirroring comes has two modes regarding transactions: synchronous or asynchronous.
Synchronous requires that the data be committed in both places before releasing the transaction. This has a big performance impact on the FIM Service database and to a lesser extent on the FIM Sync Database.
Asynchronous means that data isn't committed in both places at the same time, the mirror can fall behind and then in failover you could be behind. In order to have automatic failover with Mirroring you have to be able to modify the connection string to include
the failover partner or the client has to support getting that data at first logon. While you can modify the FIM database connection strings, it is not understood if FIM is using database clients that support mirroring. I believe it is. Even with asynchronous
you still have performance hit for copying every transaction to the mirror.
SQL Always On combines the best of mirroring and clustering to allow you to group databases together into an availability set, and then automatic failover the whole group to another server. It should be noted that Always On makes use of a similar underlying
mechanisms as mirroring to copy the data -- this is evident when you read that Always on also has an asynchronous and synchronous mode. You will most likely run into the same performance quandary.
Will the product group add support for it? My guess is that it depends on if they find a good way to address the performance issues.
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

Error when create listener - thespecified IP Address 'IP' is not valid in the cluster-allowed IP range.

Hi...
I'm able to configure AlwaysOn and all things are great.
I have a problem only when create a listener , I have two node in same data center (SQLP1,SQLP2) and one in DR data center (SQLD1)
SQLP1 + SQLP2 > Sync
SQLD1 > Async
The error I face is
The specified IP Address 'IP' is not valid in the cluster-allowed IP range.
Check with the network administrator to select values that are appropriate for the cluster-allowed IP range.
(.Net SqlClient Data Provider)
I went through some suggestion and found a permission required (create computer objects) and I give it but still error show up.
I follow the same as here
http://blogs.msdn.com/b/psssql/archive/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance.aspx

Hi
Thanks for your follow up. I hope the below information is enough
Creating Listener through visual studio wizard “Add listener”
Hostname
IP Address
Description
SQLP1
Public
10.190.255.90/
Subnet 10.190.255.0/24
Private
10.192.255.90
subnet 10.192.255.0/24
MS SQL AlwaysOn Availability Test Lab Server 1 – Main DC
SQLP2
Public
10.190.255.91
Subnet 10.190.255.0/24
Private
10.192.255.91
subnet 10.192.255.0/24
MS SQL AlwaysOn Availability Test Lab Server 2 – Main DC
SQLDR1
10.193.255.90/
subnet 10.193.255.0/24
Private
10.194.255.90
subnet 10.194.255.0/24
MS SQL AlwaysOn Availability Test Lab Server 1 – DR DC
10.190.255.93
SQL Always on listener

SQL Always on

Similar Messages

Maybe you are looking for