2004-11-09
2,223 reads
2004-11-09
2,223 reads
Another in our series of things you should avoid at all costs. Seems silly at first, not having a detailed recovery plan for your SQL Server. Perhaps it is, but having dealt with any number of problems over the last few years, Steve Jones has some ideas why a detailed plan may not be the best thing to spend your time on.
2004-11-09
8,050 reads
This is the first article by Steve Jones that examines a programming technique for handling operations that may be too large to run in a single query.
2004-11-05 (first published: 2001-05-09)
19,046 reads
2004-11-05
2,382 reads
2004-11-04
2,070 reads
2004-10-28
1,644 reads
2004-10-27
2,271 reads
2004-10-26
2,139 reads
2004-10-22
2,691 reads
2004-10-21
2,258 reads
In the realm of data science, SQL (Structured Query Language) reigns supreme. It's your...
By Brian Kelley
The bottom line here is this: the idea that a CSP takes care of...
In today's data-driven world, SQL (Structured Query Language) is a blazing-hot skill. It's your...
The below code works for backup files only from local drives. When replaced with...
I have been asked to fine-tune the following SQL that was written by a...
In this scenario, I seek assistance in implementing row-level permissions for a table named...
What are the initial config sizes for the tempdb primary data files, secondary data files, and log files in SQL Server 2022?
See possible answers