A Case FOR Cursors...
We've all heard that definitive statement: "Avoid using cursors." But, in my opinion, what really should be conveyed is: "Avoid using row-by-row operations when possible."
2016-09-09 (first published: 2015-06-01)
13,573 reads
We've all heard that definitive statement: "Avoid using cursors." But, in my opinion, what really should be conveyed is: "Avoid using row-by-row operations when possible."
2016-09-09 (first published: 2015-06-01)
13,573 reads
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
By Vinay Thakur
Continuing from Day 6 we learned Embeddings, Semantic Search and Checks, on Day 7...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
Comments posted to this topic are about the item Restoring On Top I
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers