Another excellent blogger here on SSC, Jeffery Yao, has posted up an interesting idea http://www.sqlservercentral.com/blogs/jeffrey_yao/archive/2009/04/20/database-administration-literature-criticism.aspx .
As a PASS chapter leader...
2009-04-19
456 reads
Often I tell clients better to much memory than too little. This can be applied to any database engine essentially. If your data set is growing over time you will end up using any memory that is not consumed today.
2009-04-15
3,029 reads
I’ve often described SQL Server to people new to databases as a data pump.
Just like a water pump, you...
2009-04-13
1,229 reads
Often I tell clients better to much memory than too little. This can be applied to any database engine essentially....
2009-04-11
1,414 reads
One of the fun facts about SQL Server and the relation model is the
whole concept of three valued logic. Now...
2009-04-09
1,107 reads
Technorati Tags: SQL Server,I/O"Any technology, no matter how primitive, is magic to those who do not understand it."
freefall
Arthur C. Clarke...
2009-04-05
600 reads
I couldn't find a solid script for this so I put this together. It creates the database EXACTLY as it was with growth and proper file groups.
2008-12-18 (first published: 2008-11-14)
1,272 reads
This is based on Clint Herring's work and was better than what I was using ;). It has one user definded variable @path that is where to store the files generated. It will make one file per database and one master file to restore all user permissions into that database. Used mostly for DR and […]
2005-03-30 (first published: 2004-05-25)
1,025 reads
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). Wesley Brown has taken four of these products into his environment and run some comparisons. Read about large databases in part 2 of this series.
2004-12-09
7,294 reads
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). New Author Wesley Brown has taken four of these products into his environment and run some comparisons. Read part one of his review.
2004-12-07
10,777 reads
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
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 *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers