Skip to main content

Upcoming SQL Server 2018 Features.


The new upcoming SQL server 2018 features list as below.
  • Edible Result Sets
  • Self-destructing transactions
  • New SSMS color schemes by Karl Lagerfeld
  • Deep South Parent/Child Referential Integrity (I didn’t wanna ask for details there)
  • Eventual consistency
  • Scented error messages
  • Duraflame Transaction Log
  • Access storage engine
  • MAIM command – like KILL, but lets you keep up to half of the result sets that have already been delivered
  • Renaming SQL Server Agent to Cortana
  • Twitch integration for a video replay of cool transactions
  • Azure Power Enterprise Server – I’m not quite sure what this is because the description changed three times while we were talking, and the name changed four
  • Opinion-based triggers
  • TSA-grade security
Labels:
Location: Australia

Comments

Post a Comment

Popular posts from this blog

Generating serial numbers and keys in Asp.net(C#).

here we are using GUID for generate serial numbers and GUID is always unique. Example format: XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX. Guid SerialKeyGuid = Guid.NewGuid(); string AccessKey = SerialKeyGuid.ToString("N"); string AccessKeyLength = AccessKey.Substring(0, 28).ToUpper(); char[] serialArray = AccessKeyLength.ToCharArray(); string SerialNumber = ""; int P = 0; for (int B = 0; B < 28; B++) {                 for (P = B; P < 4 + B; P++)                 {                     SerialNumber += serialArray[P];                 }                 if (P == 28)                 {                     break;                 }         ...
Post a Comment
Read more

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more