SQL Server 2025 Excitement

  • Comments posted to this topic are about the item SQL Server 2025 Excitement

  • We've been stuck on 2016 for a long time and the thing I'm looking forward to most is not specific to 2025. It's the change to the "string or binary data would be truncated" error so that you actually get a clue as to what caused the problem.

  • I've been doing some stuff with the new [vector] data type as a result of some efforts related to AI projects. in both 2025 and Azure, the data type exists, but the  built in functions don't work at this time. I hope they fix that before the official release; i've been pushed to other database systems just to test that functionality to find near vectors

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

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

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