Because data can not be replicated directly from SQL Server 2008 R2 to Azure SQL Database I wonder if it is possible to replicate using replication from SQL Server 2008 R2 this way: SQL Server 2008 R2 replicates data to SQL Server 2012 or 2014 and then from there I replicate data to Azure SQL database.
What is the best fallback plan? Let's say we went to live and after 1 or 2 days we realized that we need go back. What is the best way to go back to old datacenter to SQL Server 2008 R2?
The database is approximately 20Gb. It is preferred to do migration in 1 step.
I doubt that SQL Server 2012 or 2014 database could be a subscriber at the same time and the publisher.
At this point of time, replication between on-premise SQL 2008 R2 Database and Azure SQL is not supported.
If you are asking about data migration, I suggest using Azure SQL Migration tool. You can download it from codeplex, choose appropriate version 2008 R2
take a look into this article. To summarize: you can do a direct SQL 2008 DB move to Azure if the DB adheres to the v12 DB schema.
Related
Can I create a snapshot from SQL Server 2012 on a SQL Server 2008 R2 Server?
The goal is to build reporting and queries without locking the live database.
I need only a DB copy (Getdate()-1)
No, the SQL Server 2012 snapshot has specific SQL Server 2012 features in it that are not compatible with SQL Server 2008 R2. These are incompatibilities that you will not see. They are deep in the SQL Server engine. You cannot do this.
It's a similar concept to trying to restore a SQL Server 2012 database backup to a SQL Server 2008 R2 instance. The higher database version cannot backstep to a lower version.
You need to use a SQL Server of the same level or higher (I believe or higher) for your snapshot server.
I don't know if the title is correct but well what I'd like to ask: is it possible to import my database from SQL Server 2005 to 2008 or is the database in SQL Server 2005 compatible with 2008? I'm still a newbie.
Thanks
You can restore an SQL Server 2005 database on SQL Server 2008.
You can not restore an SQL Server 2008 database on SQL Server 2005.
Generally speaking, at the time of writing,
you can restore any database starting from SQL Server 2005 on a newer version of SQL Server (up to 2016), and
you can not restore any database on an earlier version.
You might want to increase the compatibility level of your DB after restoring it on a newer SQL Server version.
Yes. They are compatible. You can use a backup to transfer all the data.
Can I use a SQL Server Express database backup file to restore that database on a full fledged version of SQL Server. I am particularly looking at SQL Server 2008 Express to SQL Server 2012 Enterprise. And if so how?
Lets be clear about one thing first, SQL Server Express , Standard and Enterprise are the Editions.
SQL Server 2005 , 2008, 2008 R2 and 2012 are SQL Server versions.
Now coming to your question whether you can restore a database from 2008 Express to 2012 Enterprise?
The Simple Answer would be YES you can.
A couple of things to keep in mind.
SQL Server Editions has no limitation you can backup and restore databases from one Edition to another without any restrictions (Except SQL Server Express which can only accommodate databases upto 10 GB). Other than this size limitation in SQL Server express, all is good.
Whereas SQL Server Versions has a very strict limitation, You can go up 3 versions but cannot go down at all.
For example if you had taken a backup on SQL Server 2008 (regardless of Edition) you can restore this backup onto a SQL Server 2008, 2008 R2 , 2012 and I think also on 2014. But you cannot restore this onto a SQL Server 2005.
I hope the explanation clears some confusions.
We are considering to upgrade our Database from SQL Server 2008 R2 to SQL Server 2014. However, The new licensing with Core based seem to be very expensive.
We have one primary database and one secondary database. If we have SQL Server 2014 Enterprise Edition for the Primary database and SQL Server 2014 Standard Edition for the Secondary Database.
Question 1)
Is it possible to run transaction log shipping in different edition as above?
Question 2)
Could it be possible to run it from SQL Server 2014 to SQL Server 2008 R2?
Is it possible to run transaction log shipping in different edition as above?
Going for possibility yes it is possible to configure log shipping between SQL Server 2012 Enterprise and standard edition. But Just think of scenario where you are using enterprise features in Enterprise edition and failover happens now SQL server is on standrad edition and enterprise features will not work and you might face issue with application, some functionality crashing. I dont think you want this.
Plus again if you are using enterprise features and to configure loghshipping you take backup of enterprise edition and try to restore it on standard it would fail saying the backup has enterprise features and DB cannot be brought online because current database does not supports it
Could it be possible to run it from SQL Server 2014 to SQL Server 2008 R2?
No because you cannot restore database backup taken on SQL Server 2014 on SQL Server 2008 R2. If you like to make SQL Server 2008 R2 as primary and 2014 as secondary then you may succeed in configuring logshipping using T-SQL scripts( you cannot do it using GUI) but consider scenario where failover occurs and 2014 is new primary you cannot fail it back to 2008 r2 as Higher to lower version is not allowed.
Hope this is clear
I use SQL Server 2008 R2 as the database engine. With my MSDN subscription, I can get SQL Server 2012 for development use. Since I noticed some cool things in 2012 SSMS, my question is that if I only use 2012 SSMS and keep 2008 R2 as the database engine, will there be any difference in scripts' generation or any other effects?
Thanks.
UPDATE 1:
Oh yes, I saw this page: SQL Server Database Engine Backward Compatibility, but it is not exactly what I am looking for.
No, there should be no ill effects.
SSMS 2012 should generate scripts that are compatible with the database version that is being actively used.