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.
Related
Is it possible to set up a replication between an SQL Server Express Database that we can't touch, with an SQL Server Standard database?
We only have read-only access on the SQL Server Express database, so we are oblige to use only SQL requests.
We thought of using a python script and doing the replication ourselves, but is there a framework that can do that ?
We don't need realtime replication, a time span of minutes is enough.
I need to know if cross-database transactions are supported or not in Microsoft SQL Server 2016 Enterprise.
The wording on the following article is contradictory:
https://technet.microsoft.com/en-us/library/ms366279.aspx
Cross-database transactions within the same SQL Server instance are
not supported for Always On Availability Groups. This means that no
two databases in a cross-database transaction may be hosted by the
same SQL Server instance. This is true even if those databases are
part of the same Availability Group.
This is then followed by the following statement:
Cross-database transactions are not supported for database mirroring
or for Always On Availability Groups in any version of SQL Server
prior to SQL Server 2016.
Can someone please tell me which it is?
Supported or NOT supported?
My requirement is to maintain two database in SQL Server 2014 Management Studio (one for transaction and another for reporting) for single application developed in EF 7 and MVC 6.
My question is
what are the technologies I can implement for my requirement?
How to Implement and maintain two database?
I did some R&D regarding the requirement here but I cannot find the actual solution. Solution I find from R&D is Mirroring, synchronisation and CDT. I am not been able to figure out which technology to use for data replication.
I want to feed data in reporting db at the time of transaction in transaction db and I may be allowed for updating the reporting db.
Basically SQL Server 2014 is the first in-memory database on SQL Server data platform.
This means, the transactional (OLTP) and reporting (OLAP) capabilities are merged and covered by SQL Server 2014. You can check how to create in-memory database on SQL Server 2014.
Actually I'm not sure how successful is this approach but SAP HANA is being marketed with this saying.
The column-store indexing and compression ratios with decreasing prizes of memory brought in-memory databases enhancements with Sybase, SQL Server, Hana and now Oracle
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.
Is it recommended to use two versions of SQL Server (2005 and 2008) for storing data of an application. We have a situation where we have an existing web application consuming SQL server 2005 as a database. Some enhancements in the application required us to solution a FILESTREAM data store. Now we have our data in SQL Server 2005 and associated FILESTREAM data in SQL Server 2008. Being very new to SQL Server I would like to ascertain how bad is this in terms of performance? How can we achieve atomicity across both the database versions, is it via using a linked server or some other mechanism? Any alternative solutions would be fine except that we just cannot migrate the existing application to SQL Server 2008.
To keep your transactions ACID, you can use distributed transactions at a stored procedure level, or from a code level using DTC (e.g. via a .net TransactionScope). DTC would need to be present on both SQL Servers, and on your App Server as well if you do the ACID from there. There is some overhead with DTC
Edit : You will also need to link the servers with sp_addlinkedserver and provide credentials with sp_addlinkedsrvlogin