It's been some time and he apologizes. This next part of this series from Steve Jones looks at selective auditing changes to data on the server using a combination of methods presented in previous articles in the series. Read on if you have problems tracking changes to data on some tables, but don't want to implement a solution that tracks every change.
2004-04-28
12,821 reads
2004-04-22
1,985 reads
Good enough for your bookshelf? This one meets that requirement for Brian, click the link to find out why.
2004-04-13
8,906 reads
2004-04-09
1,856 reads
2004-04-08
1,908 reads
2004-04-05
1,681 reads
2004-04-01
1,970 reads
2004-03-31
1,531 reads
If your database is marked suspect, this will show you a step-by-step guide in how to fix the problem.
2007-09-22 (first published: 2004-03-31)
59,244 reads
Do you have the need for more speed on your servers? How do you go about squeezing more speed out of the database when faced with an upgrade? Steve Jones walks through some of his thought process when looking at ugprade for one of his servers.
2004-03-30
6,477 reads
By Vinay Thakur
Continuing from Day 5 where we covered notebooks, HuggingFace and fine tuning AI now...
By Steve Jones
This is kind of a funny page to look at. The next page has...
A while ago I blogged about a use case where a pipeline fails during...
Comments posted to this topic are about the item Why End-User Testing Is Even...
I have a table I didn't design that has tons of repeating groups in...
Comments posted to this topic are about the item Writing as an Art and...
What is the range for the result from the EDIT_DISTANCE_SIMILARITY() function in SQL Server 2025?
See possible answers