2004-11-01
1,458 reads
2004-11-01
1,458 reads
2004-10-25
1,555 reads
2004-10-18
1,532 reads
If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.
2004-10-15 (first published: 2001-05-04)
9,678 reads
2004-10-11
1,471 reads
Andy has some examples of not very high tech solutions that involve some technology behind the scenes, but the binding factor was that someone had to see the problem first. Not about SQL, but we think it is on topic.
2004-10-08
4,461 reads
2004-10-07
1,425 reads
2004-10-06
1,436 reads
2004-10-04
1,534 reads
2004-10-01
1,654 reads
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...
By Vinay Thakur
Continuing from Day 5 where we covered notebooks, HuggingFace and fine tuning AI now...
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