When DBAs Should Consider Using SQL Server to Store Vector Data and If It Makes Sense

  • Comments posted to this topic are about the item When DBAs Should Consider Using SQL Server to Store Vector Data and If It Makes Sense

  • thnak you for great article

  • Nice article.

    In many ways, I feel it is a great shame that the full-text index engine was allowed to stagnate.  If that had had some TLC over the years perhaps full vector DB capability would have been a natural evolution,

  • I happen to be in the middle of a vector project. i downloaded SQL2025, and while i can  use the vector data type, the built in functions related to vectors are not yet available(i was after VECTOR_DISTANCE) the same was true when i created an Azure SQL Database, in case the new features where implemented there.

    I put 2025 away for now because of that, and on my SQL2022 isntnace, i am just storing my vectors in varchar(max) columns along side the field's original values, and am also leveraging full text like David suggested, for better searches.

    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 4 posts - 1 through 4 (of 4 total)

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