Post reply

SQL Server RTM - June 1

  • May 14, 2016 at 11:51 am

    #327073

    Comments posted to this topic are about the item SQL Server RTM - June 1

  • May 14, 2016 at 1:02 pm

    #1879102

    re: "and more", PolyBase and R analytics integration are very exciting features to me personally that will expand the data platform and its reach within enterprise environments.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • May 16, 2016 at 10:45 am

    #1879319

    I would count this as a very important release - the In-Memory/Hekaton tables can finally have foreign keys (even if they must reference a primary key), which takes them from party tricks into the realm of the reasonable for databases that enforce data integrity... if you're on Enterprise Edition.

    The new COMPRESS and DECOMPRESS functions (GZip) are also tremendously interesting, and moreso in those (rare?) cases where they can be combined with a view and an INSTEAD OF trigger on ancient, awful databases.

    Also, for the first time in many years, CREATE CERTIFICATE generates a key that meets both sane minimums and current regulatory guidance (2048 bit certs instead of the pathetic 1024 bit certs we had to work with even on SQL 2014).

  • May 16, 2016 at 11:57 am

    #1879337

    Nadrek (5/16/2016)

    I would count this as a very important release - the In-Memory/Hekaton tables can finally have foreign keys (even if they must reference a primary key), which takes them from party tricks into the realm of the reasonable for databases that enforce data integrity... if you're on Enterprise Edition.

    The new COMPRESS and DECOMPRESS functions (GZip) are also tremendously interesting, and moreso in those (rare?) cases where they can be combined with a view and an INSTEAD OF trigger on ancient, awful databases.

    Also, for the first time in many years, CREATE CERTIFICATE generates a key that meets both sane minimums and current regulatory guidance (2048 bit certs instead of the pathetic 1024 bit certs we had to work with even on SQL 2014).

    Agree. It's been better to import certs in SQL 2014-- since you could go 4096 there.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply