Last week the SQL Sapphire (or SQL Slammer) virus hit corporate networks throughout the Internet. Although damage has not been estimated yet, it is sure to be in the tens of millions of dollars. So who is to blame when a virus like this manhandles a corporate environment?
This article by Simon Galbraith (from Red-Gate Software, one of our valued advertisers!) in .Net Magazine talks about how to calculate ROI when evaluating software purchases.
How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn't work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control.
Standards are important in the computer business, both the hardware and software side. After looking at Coding Standards in a previous series, Steve Jones looks at the server side of standards beginning with hardware.
Ever tried to open 1 Gig ASCII file with Notepad? WordPad? Do you remember ASCII codes of Tab and Carriage Return? Enter Terminator; huge ASCII file viewer and BCP helper. Terminator reads top 10 (and more if asked) records of ASCII file of any size. It detects record terminators and calculates current cursor position (field offset) and length of selected area (field length). Best of all, it's free!
Can you block a DBA from performing certain actions on a server if he has sysadmin rights? The real answer is no, but this article shows you how to block an unknowledgable DBA from performing certain actions.
On Friday the 24th, a virus that preys on a SQL Server vulnerability began to attack networks, taking down many networks. This brief network describes the virus and how to protect yourself from it.
Moving SQL Server from one computer to another is not a very difficult thing to do, but it often stumps newbie DBAs. Of course, it needs careful planning to ensure that the SQL Server is moved completely and properly to the new machine, and with a minimal downtime and no data loss. This article introduces you to a couple of methods you can employ to move/migrate SQL Server from one computer to another.
This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team.
This application will convert your schema into a standard Word document. Try before you buy, they have two versions - both under $200.
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
Comments posted to this topic are about the item Answering Questions On Dropped Columns
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers