Microsoft isn't letting you own a Web Edition of SQL 2012 like they did with 2008. But 2012 Standard edition is way overkill for my needs.
Can I have a database server running 2012 Enterprise (or Standard) and use transactional replication to populate data on a 2008 Web Edition box? This would, of course, be 1-way replication only.
Thanks... trying to save a bunch of money on licensing here.
Yes, replication is possible, as a subscriber only. See the Replication matrix in this article.
Basically, SQL Server 2008 Web Edition supports as subscriber only:
Merge replication.
Transactional replication.
Snapshot replication.
Related
I wanted to ask about Your experience related to set up a Transactional replication between SQL SERVER 2008R2 (publisher) and SQL SERVER 2017 (subscriber).
I know that this is not supported by Microsoft according to "Transactional & Snapshot Replication compatibility matrix", in the docs.
But I set up this kind of transactional replication (2008R2 -> 2017) on a few databases and it works without any errors. So the question is when or in what kind of situation (maybe some special type of configuration, user-defined data types...), this replication could stop to work or generate errors?
Support for SQL Server 2008 R2 has ended, so everything you do is unsupported.
In this configuration (2008 Publisher/Distributor/Push Subscription) all replication activity is driven from the SQL 2008 R2 instance, and with a SQL 2014 subscriber this was a supported configuration.
So the only thing that would break is if SQL 2017 somehow behaved differently than SQL 2014 did. To minimize the likelihood of issues keep the subscriber in 100 or 120 database compatibility level. 130 compatibility level introduced some breaking changes.
I'm not a DBA but I hear that database mirroring is deprecated or about to be, I'm using SQL 2014, in my company they are using database mirroring, which is exactly the new version? it is something we can implement on SQL Server 2014 or we need to have a newer version installed? I want to convince people that database mirroring should be replaced.
AlwaysOn Availability Groups (AGs) are the replacement for Database Mirroring. You can stay on Mirroring on SQL 2014 if it works for you, but when you upgrade you should plan on migrating to AGs. If you're on Standard Edition, you can use Basic Availability Groups which have the same capabilities as Database Mirroring on Standard Edition.
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
Does Microsoft SQL Server 2008 Express support transactions?
According to the page http://msdn.microsoft.com/en-us/library/cc645993(v=sql.100).aspx subscribers only. But what does that mean?
I would like to start an transaction from an C# application.
Yes, it does. SQL Server and SQL Server Express Edition are essentially identical apart from some restrictions in the latter (e.g. maximum size of a database) - all the basic RDBMS features work exactly the same.
Transactional replication has very little to do with the transactions you mean.
That's "transactional replication", not SQL transactions. Transactional replication is a method replicating databases across servers.
Yes, SQL Server Express supports transactions.
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.