Where to start the transaction for a pessimistic concurrency????
My question is : Isn't true when dealing with pessimistic concurrency the transaction has to start in the client?
In other words, for example, you have a C# client window application that retrieves a record for updating from
a SQL Server database. You retrieve the record and you update it on the window screen and send it back to the sql server ---in this process you don't want anyone else grabbing that record for possible updating and so you must start the transaction on the client side and not in say a stored procedure on the sql server database.
Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.
The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed