Can i use preview feature link for SQL MI as DR site (database) for on-prem SQL Server instance?.We don't want to use the SQL MI for reporting purpose. If the answer is yes, if i failover to SQL MI database as primary in case of DR, when original primary onprem SQLDB comes up, can i failback from SQL MI??
https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/managed-instance-link-feature-overview?view=azuresql
Nothing. Looking for an conceptual understanding.
The ability to failback to on-prem is only available in SQL 2022. See The Ultimate Freedom of Movement between SQL Server 2022 and Managed Instance - Microsoft Community Hub
Please let us know if you have further queries.
Related
The client has on-premise SQL Server on his side. We want to replicate his database to our PostgreSQL Azure. The replication we want can have maximum 1min delay. ADF is not the option - copying is too frequent.
What tools can we use? We thought about Azure Sync or SymetricDS. Eventually Would SQL Server -> SQL Server be easier to execute? Any suggestions even beyond Azure are much appreciated.
As #Martin Cairney said on-prem SQL Server -> Azure PostgreSQL doesn't exist in Azure DataSync, so you would need to make use of offical or a 3rd party replication tool. Azure DataSync only support Azure SQL as the Hub Database.
Offical tool, such as Azure data factory. You can set a trigger condition to reduce the frequency of copy activities.
3rd party tool, sunch as skyvia. You said SymmetricDS maybe not support Azure PostgreSQL, according to its official doc.
I believed that I always got the latest version of SQL Server when creating a new Azure database from the Azure Portal. But that is not happening.
I always get sql Server version (12.0.2000.8) which is SQL 2014. I can't find other places to set a new compability level either.
Is there a problem with my subscription (pay as you go)??
Have any of you had the same experience as me, have you been able to solve it?
The reason I want SQL 2017 is that I want to publish SSIS packages to the SSISDB catalog, which is not possible on SQL 2014?
Hope any of you can help me out here
regards GEir
It's possible to use SSIS on DB engine 12 on Azure. Check out official documentation.
Additionally, you may upgrade your already-created azure databases by setting COMPATIBILITY_LEVEL modificator. Look into ALTER_TABLE documentation for examples.
Please note that although SQL Azure's engine share similar "engine api" as SQL Server 2014 (v12), those are not the same. What's more relevant in terms of supported features is maximum supported "Compatibility level".
I'm following a step-by-step guide written by a Microsoft field engineer on below documentation to create BizTalk 2016 AOAG with SQL 2016 enterprise edition in conjunction with Server Management Studio (14.0.17224.0):
https://learn.microsoft.com/en-us/biztalk/core/high-availability-using-sql-server-always-on-availability-groups?redirectedfrom=MSDN
My question on preparing the availability group using Server Management Studio (14.0.17224.0) supports database DTC option is that new functionally added to SQL management studio (14.0.17224.0) and during creation of his lab environment he mention DTC support cannot be applied from the SSMS and must be done in script?
I created AG though SSMS GUI and ran query to find DTC status on DATABASE as below
:
--===Checking where there DTC support is ENABLED or NOT for BIZTALK 2016 SSODB======
SELECT NAME,DTC_SUPPORT FROM sys.availability_groups
HOLD ON!
The first thing you should do is really, double, triple check you really, absolutely 110% need (as in no other option) to use AOAG with BizTalk Server.
While supported, AOAG is in practice a net negative with BizTalk Server over regular failover clustering alone since it adds significant additional complexity to the setup, while providing no incremental benefit to BizTalk Server.
Note, this situation is specific to BizTalk Server. Many apps can and do benefit from AOAG, just not BizTalk Server.
Availability Groups is better H/A solution in my opinion. It comes with database-redundancy and a much faster failover which a BizTalk environmient will benifit from.
From SQL 2016 SP2 and SQL Server 2017 it also supports Cross Database Transaction inside instances in AOAG so you only need one instance (instead of 4 instance in SQL 2016 SP1).
I belive that a Windows Failover Cluster is more complex because you have a lot more shared resources while in Availiability Groups it is only the listner that is a resource in WFC.
Starting with SQL Server 2016 (13.x) Service Pack 2 you can alter an availability group for distributed transactions. For SQL Server 2016 (13.x) versions before Service Pack 2, you need to drop, and recreate the availability group with the DTC_SUPPORT = PER_DB setting.
- For the down voter: This is not a rant in anyway, been using Azure since last 4 years, totally fan -
So far I was using the Manage option of the previous Azure portal, now that the new portal is enabled by default, they does not seems to have transferred the Azure SQL manage option.
SQL Server Management Studio 2016 CTP 3.1 (November 2015) does not offer me any kind of table designer.
Now I know, I could type everything into T-SQL, but still for schema manipulation, the table designer is still the quickest.
Is there not any way to have the old "manage" Silverlight interface or having SSMS handling table design with indexes etc?
In fact, I'm reading everywhere that since SSMS 2014 there has been support to Azure SQL table designer, still I don't have that option on the latest version of SSMS. Is the 2016 have less support for Azure SQL than 2014?
I don't have Visual Studio anymore, and frankly I would rather not want to install this just to have a more comfortable time designing a Azure SQL schema.
Any pointer, how do you handle this?
Table Designer for Azure SQL Database V12 has been enabled from SQL Server Management Studio June 2015 Release.
Source : http://blogs.msdn.com/b/sqlreleaseservices/archive/2015/06/24/sql-server-management-studio-june-2015-release.aspx
You're saying that you're using the last SSMS version (November 2015) but are you using a V12 server on Azure?
Regards,
Has anyone here moved the database underlying a SP 2010 install from one database instance to another (same data, just hosted in another instance)?
For example. we just want to move the database to a diffrerent machine.
In addition, has anyone moved SP 2010 from using SQL Express to a higher version of SQL Server? I would like to run some proof of concept tests with SQL Express, and if all goes well, then move to SQL Standard or Enterprise.
Cheers,
Daniel
Check out the following article:
http://technet.microsoft.com/en-us/library/cc512725.aspx
I don't think you'll run into any problems, just make sure you aren't going backwards in versions between databases. Backing up a database in SQL Server 2008 and restoring in 2005 isn't easy.
I've never done this with SharePoint, but I believe it lets you specify the location of the configuration database. Then you just need to match the user permissions.
The TechNet article "Move All Databases (SharePoint 2010)" is your main guide.
Note that this article contains the following warning:
The new database server must be running the same version of Windows
Server and Microsoft SQL Server as the existing database server.
This in NOT true!
Both from my own experience in migrating SharePoint databases and talks I've had with Microsoft Primary Field Engineering, I can say this method also works when SQL Server versions differ. But only if you upgrade to higher SQL Server versions (i.e. SQL Server 2005 to SQL Server 2008 R2). I was told this scenario is also fully supported by Microsoft.
Also, don't forget to update the database compatibility level for the migrated databases. This should future-proof your databases and enable advanced SQL Server optimization.